Hello,

Boxed layout is a great feature, we will add it as a setting in our next release.

We are planning to release new version 1.9 in a day, so we will let you know when ready.

Hello,

As a demo we are using this.props.appStore.userIsAuthenticated property in order to hide or show the login container page, check Line 194 of containers/App/index.js

You can use browserHistory to navigate programatically:

import { browserHistory } from ‘react-router’;

browserHistory.push(’/somepath’);

Check the documentation:

https://github.com/reactjs/react-router-tutorial/tree/master/lessons/12-navigating

Thank you for your response. I tried with browserHistory.push and I received an error:

uncaught at SignInRequest Invariant Violation: Objects are not valid as a React child (found: TypeError: Cannot read property ‘import’ of undefined). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. at invariant (webpack:///./_{/fbjs/lib/invariant.js?:44:15) at traverseAllChildrenImpl (webpack:///./}/react-dom/lib/traverseAllChildren.js?:144:44) at traverseAllChildren (webpack:///./_{/react-dom/lib/traverseAllChildren.js?:172:10) at flattenChildren (webpack:///./}/react-dom/lib/flattenChildren.js?:66:5) at ReactDOMComponent._reconcilerUpdateChildren (webpack:///./_{/react-dom/lib/ReactMultiChild.js?:204:28) at ReactDOMComponent._updateChildren (webpack:///./}/react-dom/lib/ReactMultiChild.js?:312:31) at ReactDOMComponent.updateChildren (webpack:///./_{/react-dom/lib/ReactMultiChild.js?:299:12) at ReactDOMComponent._updateDOMChildren (webpack:///./}/react-dom/lib/ReactDOMComponent.js?:930:12) at ReactDOMComponent.updateComponent (webpack:///./_{/react-dom/lib/ReactDOMComponent.js?:748:10) at ReactDOMComponent.receiveComponent (webpack:///./}/react-dom/lib/ReactDOMComponent.js?:710:10)

We tested from a container, from where are you executing browserHistory?

You can also try with requiring react-router:

const router = require(‘react-router’);

router.browserHistory.push(‘somePath’);

I call from a reducer.js file. I know about appStore.isUserAuthentificated but the app don’t have a recover as a reset password page. I build a new component called Auth that include all 3 parts that is needed for a complete Auth module.

I have same issue with car router = ...

Var**

We tried to place browserHistory into a reducer, but it is not a good practice.

Uncaught Error: Reducers may not dispatch actions.

Reducer should be used to change states only.

You can use a Saga instead.

We did a test in the ComponentDemos/ApidemoPage/sagas.js

import { browserHistory } from ‘react-router’; ...

export function* updatePost(action) { ... yield put(updatedPost(result)); browserHistory.push(’/’); ...

So after we update a post we navigate to dashboard.

I use fortress 1.7 .. I put in the my saga and i have same issue. I saw in Components / LeftDrawer browser history it works without any issue .. I don’t have any explanation why i have this issue. Do you think in 1.8 you update something that correct this issue ?

I figure out what is the issue . Webpack serve wrong files or chrome catch the old files. Even the cod is functional the result was wrong due to the issue above. I figure out when I run fortress theme and the chrome browser serve my app and the mozilla serve fortress app… Very, very strange I think the issue is in the webpack .. Did you see similar issue?

Look at the picture below.. Same app , same link open with chrome and chrome incognito mode.. What is wrong? I think the webpack don’t generate unique files sometimes and for this reason the files are not updated. https://ibb.co/mqMR0v

We haven’t seen that behavior for a while to be honest. Sometimes generated files remains in cache. Using incognito window is a good option during development also you can use empty cache and hard reload in chrome.

Just press and hold the refresh icon with dev tools open:

http://www.code-pal.com/wp-content/uploads/2013/03/clear-cache-and-reload.png

In version 1.8 we updated webpack to version 2.5.1

Hello

I think you don’t have to change anything in the LeftDrawer component.

The reducer in the containers/App/reducer.js is the one that adds the elements to the this.props.appStore.menus array

There is an API that loads data.js json menu called app/api/mockMenuApi.js

Just change the getMenu() method content to get the data from an API. Check the ApidemoPage.

Hello

Thanks for the quick response!

I’ve located an action called LOAD_MENU in the app / containers / App / actions.js file

However I did not find any reducer for LOAD_MENU only LOAD_MENU_SUCCESS in the app / containers / App / reducer.js file

It is in this reducer (LOAD-MENU_SUCCESS) that the values ​​for the menu are assigned, based on values ​​that the action sent.

Actually the LOAD_MENU_ACCESS action sends a variable with the menu values ​​for your reducer.

But here I am confused, its I called the action LOAD_MENU I hope to execute the code of reducer LOAD_MENU.

So at some point that was executed LOAD_MENU and that had success should be called the LOAD_MENU_SUCCESS however I did not find this place.

There is still an app / containers / App / saga.js file that listens to calls to the LOAD_MENU action and automatically calls a function, which by what I understand calls the LOAD_MENU_SUCCESS action passing the menu items.

So if I understood, in this case the LOAD_MENU action will not have a reduer to produce a response. It exists and only serves to be called and using the Saga, trigger another action (LOAD_MENU_SUCCESS), but before the call retrieves the menu items.

So I should change the menu items here in this Saga file, before the LOAD_MENU_SUCCESS action call, passing the treated menu, or should I handle the menu items in the LOAD_MENU_SUCCESS reducer?

I think the right answer is to reduce, correct?

It was exactly the first place I tried to treat the menu, the difference being that I made the treatment in the SIGN_IN action.

Well doing the treatment in SIGN_IN even worked, the problem is that when I did SIGN_OUT and then did SIGN_IN, without closing the browser or without refreshing the page, it would not work because it would apply the menu treatment in the previously discussed menu because This is how the last state of the application was.

I had a way to recover the initial state of the menu but without success. I tried to save the initial value of the menu in an auxiliary variable because later I could use to restart the default menu items but I could not since whenever I changed the menu items in one variable the other was affected (I tried Object.assign. ..origens)), I tried to let menu2 = {... menu1} more did not work).

I feel like I’m pretty close to fully understanding how the menu is initialized, but I still do not understand which menu launch point to set up and what the whole flow is until the menu is set up.

Can you help me finalize the understanding of the menu assembly?

Thank you.

Hello,

Sagas and Reducers are mapped to the store, this means that when you dispatch an action both are listening the type of the action. In the case of LOAD_MENU, in containers/App/sagas.js you will find a function call appSaga that watches LOAD_MENU.

Once fetchMenu is executed LOAD_MENU_SUCCESS is dispatched and containers/App/reducer.js watches for that action.

You will find the initial menu dispatch in app.js line 85, it can be changed to be called in the containers/App/index.js in the componentWillMount function for example.

Hello,

Only the store.dispatch (loadMenu ()) call starts menu loading, or is it necessary to also load the sagas?

Hello,

We will help you to get the template working in your environment.

Can you describe us what you are trying to do? Is it npm install or npm start where you get the error?

I ran npm install wiht no problems. Then npm start and received the ERROR The DLL manifest is missing. Please run `npm run build:dll`. I did that as suggested in the error and nothing happens. I checked the react-boilerplate docs and ran npm run setup and it didn’t fix it. I checked the [path]/webpack.dev.babel.js and it is searching for dllPath in ‘node_modules/react-boilerplate-dlls’ and the manifestPath in reactBoilerplateDeps.json. Neither files are present in the root. Nor can I run “npm i react-boilerplate-dlls -S` because react-boilerplate-dlls is not an npm package so it doesn’t make sense that it would be found there.

const dllPath = path.resolve(process.cwd(), dllPlugin.path || ‘node_modules/react-boilerplate-dlls’);

if (!dllPlugin.dlls) {
    const manifestPath = path.resolve(dllPath, 'reactBoilerplateDeps.json');

if (!fs.existsSync(manifestPath)) {
    logger.error('The DLL manifest is missing. Please run `npm run build:dll`');
    process.exit(0);
  }
}

return [
  new webpack.DllReferencePlugin({
    context: process.cwd(),
    manifest: require(manifestPath), // eslint-disable-line global-require
  }),
];

const dllManifests = Object.keys(dllPlugin.dlls).map((name) => path.join(dllPath, `/${name}.json`));

return dllManifests.map((manifestPath) => {
  if (!fs.existsSync(path)) {
    if (!fs.existsSync(manifestPath)) {
      logger.error(`The following Webpack DLL manifest is missing: ${path.basename(manifestPath)}`);
      logger.error(`Expected to find it in ${dllPath}`);
      logger.error('Please run: npm run build:dll');
});

process.exit(0);
  }
}

return new webpack.DllReferencePlugin({
  context: process.cwd(),
  manifest: require(manifestPath), // eslint-disable-line global-require
});

Thanks,

What version of node and npm are you using?

We will try to reproduce this error.

C:\Users\lotus\Desktop\fortress-react-admin> node -v

v7.9.0

C:\Users\lotus\Desktop\fortress-react-admin> npm -v

4.2.0

Hello,

Check the below link to see if is related with your issue:

https://github.com/react-boilerplate/react-boilerplate/issues/774

We installed node 7.9, but we are not able to reproduce the error yet.

I didn’t rename any DLL. All I did was exactly the steps I mentioned above

May I request a refund. I can’t run it and I’ve been at it for a week

Hello,

Sure no problem.

Review your global packages, looks like there is some kind of conflict when you start the server. We believe is something in your environment since we have tested this template in different computers (macs, windows).

We do our best to give support to our clients and we will continue improving this template to make it the best.

Thanks!

Trust me, I want it to work. I checked the global packages. Nothing wrong. I’m already running other apps in a similar system (react/materialUI/webpack, etc) and they run fine.

Ok,

We are going to release a new version today, in case you want to give a last try.

Basically and update for webpack library to 2.5.1 And also we added a new library called recompose 0.23.4 to fix a material-ui issue.

Sounds good. How do I download the update?

The new version It is not in envato yet. We will let you know when ready later today.

Great! I will wait. I hope it works. To be honest, I am only insterested on one aspect of your template which I am hoping to gut out and use it in my actual app. If your template ends up not working, as long as I can get the part I need I will be fine and won’t need a refund. I noticed you are saving the pages visited as bookmarks and keeping them as a history of pages visited. I want to implement something similar and I think I can use this as a foundation to build my own.

Hello,

You can download version 1.8 of this template.

I’ll give it a try. Thanks. I imagine the setup didn’t change? npm install and npm start? right?

Hello, thanks for your message.

Yeah, we were able to reproduce the error with the versions you are using for node, npm, react and webpack.

The error is cause by the webpack version you are using, you should use the version that comes in the template to avoid this error.

I went back to use webpack 2.2.0 and then got this error when running npm run build:

ERROR in ./app/img/logo_small.png Module build failed: TypeError: pPipe(...) is not a function at Function.module.exports.buffer (/Users/fraggi/Downloads/themeforest-19568479-fortress-react-admin-template/fortress-react-admin-clean/node_modules/imagemin/index.js:64:60) at Object.module.exports (/Users/fraggi/Downloads/themeforest-19568479-fortress-react-admin-template/fortress-react-admin-clean/node_modules/image-webpack-loader/index.js:37:8) @ ./app/containers/LoginPage/index.js 31:11-46 @ ./app/containers/App/index.js @ ./app/app.js @ multi ./app/app.js

After a quick google search, I found the issue was with the imagemin package. I found this link with a fix: https://github.com/imagemin/imagemin/issues/244.

The fix just goes back to an older version of imagemin:

npm install imagemin@5.2.2—save-dev

That fixed the pPipe is not a function error and can run npm run build without erros.

Unfortunately, I’m back to the previous error. When I run npm run start:prod:

I get this error in the browser:

11:04:31.838 main.85d8834….js:74626 uncaught at fetchMenu Invariant Violation: Minified React error #136; visit http://facebook.github.io/react/docs/error-decoder.html?invariant=136&args[]=NavigationMenu for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at reactProdInvariant (http://localhost:3000/main.85d8834d8967b5c3717c.js:60454:15) at ReactCompositeComponentWrapper.updateComponent (http://localhost:3000/main.85d8834d8967b5c3717c.js:50646:188) at ReactCompositeComponentWrapper.receiveComponent (http://localhost:3000/main.85d8834d8967b5c3717c.js:50609:10) at Object.receiveComponent (http://localhost:3000/main.85d8834d8967b5c3717c.js:56184:22) at Object.updateChildren (http://localhost:3000/main.85d8834d8967b5c3717c.js:49922:25) at ReactDOMComponent._reconcilerUpdateChildren (http://localhost:3000/main.85d8834d8967b5c3717c.js:55463:28) at ReactDOMComponent._updateChildren (http://localhost:3000/main.85d8834d8967b5c3717c.js:55562:31) at ReactDOMComponent.updateChildren (http://localhost:3000/main.85d8834d8967b5c3717c.js:55549:12) at ReactDOMComponent._updateDOMChildren (http://localhost:3000/main.85d8834d8967b5c3717c.js:52017:12) at ReactDOMComponent.updateComponent (http://localhost:3000/main.85d8834d8967b5c3717c.js:51835:10)

I confirmed my webpack version is 2.2.0

Hello,

Thanks for your comment.

I wasn’t able to reproduce the error you mention.

I’m using node 7.9.0 and npm 3.10.6

After running npm run build npm run start:prod

I can see the app working.

Can you describe a little bit more about your error?

Hello Friend!

The error is really this one I passed and yes it does not say much …

Although your environment is different from mine, this is not the problem. Because I downloaded the theme, and everything worked here.

So I was putting step by step the insights that I made here and discovered what it is generating.

On the login screen and fuz a request for a REST service and stored the error result (this when api returns error) in an attribute of my state and then displayed the error.

But at the time of viewing I used ReactHtmlParser to display my error message that already came with html tags (a br, or p, or

tag, in my case the variable looks like this:

user required

Password required

).

So I used this ReactHtmlParser to leave the message formatted correctly on the screen (the message is displayed inside a Dialog). When running the application everything works and receives no error in the console or shell.

But when I run the build, I get that error …..

Do you have any suggestions for substituting ReactHtmlParser?

Thank you!

Hello,

I did a test and now I was able to reproduce the same error. That ReactHtmlParser library has issues when building to production.

Use this syntax instead:

dangerouslySetInnerHTML={{ __html: ‘your html’ }}

I tested and it works ok when running npm run build.

Check this url: http://stackoverflow.com/a/19277723

Ignore my last past. I will look on your API example. Very nice update.

Hello, thanks for your comment. We just included a seed version of the template, please download the latest version.

Thank you very much.

Another question. I started from seed and i wanted to remove “Opens view”. I almost succeed but I have a little issue. The routes are not opened when i click on a menu item. It is an option or an easy way to run the theme without having open views ?( In Left drawer and Header component)