Hi. Yes, Gogo version is 1.0.2. I downgraded my node version to 8.9.0 and I’m getting the same error. I think this is a babel problem, but I’m getting this error only starting Gogo.

Hi,

You are the first one getting this error or maybe someone had the error but found the solution. We are not able to recreate it so we will not be able to provide a solid solution. You may have a refund if you like.

Regards.

Hi,

One of our users had this exact problem and he managed to find the source of it.

In his case, it is about files which start with a dot being hidden by his os and failing to copy them.

In project directory there should be a ”.babelrc” and ”.eslintrc” files and the problem occurs when ”.babelrc” file is missing. Maybe you should also check it when you have time.

Regards.

Hi Shai,

Thanks for your purchase.

As for the question, here is where the authentication check is made and how to remove it.

src/containers/App.js

This file checks authentication and makes redirection accordingly.

You should change following block with next one.

const InitialPath = ({ component: Component, ...rest, authUser }) =>
    <Route
        {...rest}
        render={props =>
            authUser
                ? <Component {...props} />
                : <Redirect
                    to={{
                        pathname: '/login',
                        state: { from: props.location }
                    }}
                /> }
    />;

const InitialPath = ({ component: Component, ...rest, authUser }) =>
    <Route
        {...rest}
        render={props => <Component {...props} />}
    />;

Regards.

Hi Aidan,

We gladly accept refunds if the problem is with our item or description but we stopped accepting refunds for buyer faults since we felt it was being abused.

If you have not donwloaded the item, we are obligated to accept your request.

We expect you to understand us as a fellow author.

Regards.

Hello,

You have done the most of the job. Here is what we think is missing.

src > redux > settings  > reducer.js

const INIT_STATE = {
    locale: {
        languageId: 'english',
        locale: 'en',
        name: 'English',
        icon: 'en'
    }
};

On your switch you should use redux to update this.

locale: {
        languageId: 'german',
        locale: 'de',
        name: 'German',
        icon: 'de-icon' //burası şu an kullanılmıyor. ileriye dönük raw language switcher için tutuluyor.
}

We will add this feature in next update and we think it will be available start of the next week.

Regards.

Hi,

Regards.

Hello,

We must admit that we are not really experts on this particular area, we can offer a solution but be warned that it may cause problems. Please test some builds with making changes to the source.

- Create a variable just under cleanOptison

let cleanOptionsDev = {
    root: __dirname,
    verbose: false, // Write logs to console.
    dry: true
}

-Change the following line with conditioned one.

new CleanWebpackPlugin(pathsToClean, cleanOptions),

new CleanWebpackPlugin(pathsToClean, process.env.NODE_ENV === 'production' ? cleanOptions : cleanOptionsDev),

Idea here is to send CleanWebpackPlugin different settings base on the build type. If you have any problems, let us know

Regards.

Hi,

Sorry to hear that. Is Theme Forest available or is it also requires a vpn? I am asking out of curiosity.

As for the questions, we provided Firebase as an easy starting point. It does not require any server side knowledge and provides backend connection via Rest Api. It is called serverless development. Maybe you have an alternative in your country.

Going back to the topic, as i explained earlier we are using it in src>redux>auth>saga.js file with an import { auth } from ’../../firebase’

These are the methods make Firebase api calls. auth.signInWithEmailAndPassword(), auth.createUserWithEmailAndPassword(), auth.signOut()

We also provided a project called “Gogo-React-Start” which does not include Firebase at all. It is also an empty project that contains only necessary dependencies. You may start from this project and implement your own backend solution from scratch.

Regards.

Hello, I am thinking of some ideas, whether you can add a friend through chat tools or emails to get in touch with you. Some are inconvenient to disclose content.

Hello,

Regards.

Hello,

Thanks for your patience. We have come up with a solution. Here is what needs to be done.

1. Default menu type should be changed. It is causing a bug and we think that it is not good ux when any of the main menu items don’t have a submenu. On file src > constants > defaultValues.js you should change defaultMenuType variable.

export const defaultMenuType = 'menu-sub-hidden'; 

<NavItem  className={classnames({    active: this.state.selectedParentMenu == "main-menu-single1"})}>
  <NavLink to="/app/main-menu-single1" data-flag="main-menu-single1">
    <i classname="icon-main-menu-single1" /><IntlMessages id="menu.main-menu-single1" />
  </NavLink>
</NavItem>

setSelectedLiActive() {
    const oldli = document.querySelector(".sub-menu  li.active");
    if (oldli != null) {
      oldli.classList.remove("active");
    }

    /* set selected parent menu */
    const selectedlink = document.querySelector(".sub-menu  a.active");
    if (selectedlink != null) {
      selectedlink.parentElement.classList.add("active");
      this.setState({
        selectedParentMenu: selectedlink.parentElement.parentElement.getAttribute(
          "data-parent" 
        )
      });
    }else{
      var selectedParentNoSubItem = document.querySelector(".main-menu  li a.active");
      if(selectedParentNoSubItem!=null){
        this.setState({
          selectedParentMenu: selectedParentNoSubItem.getAttribute(
            "data-flag" 
          )
        });
      }else if (this.state.selectedParentMenu == "") {
        this.setState({
          selectedParentMenu: "dashboards" 
        });
      }

    } 
}

After applying these fixes problem should be solved. If you have any problem with implementation or it does not work as expected, please let us know.

Perfect! Exactly what I was looking for. Thank you. Hope you update the documentation and add this for the next release. Keep up the good work

Note: There is a typo in the documentation for the routes section -

If your page does not need to be under a here is what needs to be done at src/containers/Sidebar/index.js file

Hi,

That is great!

We are currently working on some new features and codebase is a little bit complicated so it may take some time for this to be released. But thanks to you we know the fix if anyone experiences it.

Also thanks for the typo warning, i will fix that swiftly.

Happy coding

You already got the sources? Did you mean the landing page? This one: http://gogo-react-web.crealeaf.com/

i purchased it some weeks ago, and i really like it.

and once again i should have read the documentation more carefully…I started with the “Gogo-React-Start-With-Auth” and I thought it is the full package with some addons (may because it has the longest name

Now i realized the difference and had a look at “Gogo-React”...Problem solved.

Glad that you have sorted it out. Happy coding:)

Hello,

Thank you for the contribution. Taking your time to share this is really meaningful.

Some of the users have experienced this issue and we also managed to replicate it on a Mac. We provided the solution via comments but will correct this on the next update.

Regards.

Hello,

Thanks for the nice comment.

Our priority is developing this further with updates and then a Vue version. This will take a while and after that we will think about Angular.

Regards.

Hello,

4) We will are planning to use it as front end with firebaseUI sign up and pretty much open to the world to register and login. Do we need extra license for that?

Hello,

Thanks for your nice comment and interest.

Here are the answers.

1. There is only Firebase login which we added as a basic starting point.

2. We have not implemented any server side code. Our priority was to provide frontend as good as we could. So there is not a search function.

3. We have not used any external data source. Some components get their data from a static local json file with a basic import.

4. I am not an expert but i think it depends on what your users will do with it. If you sell concert tickets with it, that is a regular license but if you sell it as an accounting application that might need an extended license since it is a saas(software as a service) Please check the license pages for more information. https://themeforest.net/licenses/terms/regular

Regards.

Hi, I just bought the correct one! Can you proceed with the refund of the React version, please? Thank you so much for understading and sorry for the inconvenience.

Hi Mikera,

We answered your request.

Regards.

Hi,

We are planning to include a landing page after next update. Next one is currently on development and after that we will be working for the landing page. It should be available approximately in 2 weeks.

There is not a horizontal menu implementation and we are not planning to add one.

Regards.

Hi,

Landing page is available if you are still interested.

You may check it under Landing Page menu item: http://gogo-react.crealeaf.com/

Regards.

Hello,

It seems like the problem is about webpack-cli package. We have not experienced it on Windows. Googling the error quickly pointed us to the solution. For more information you may check here: https://github.com/webpack/webpack/issues/8082

1- To get it working uninstall webpack-cli with following command.
npm uninstall webpack-cli

2- After uninstalling complete install it again with following command. This should install webpack-cli 3.1.2
npm install webpack-cli --save-dev

3- After this, you should be able to use npm start and npm run build.

Regards.

Hi Onur,

Your project does not require an extended license, standard will do.

Regards.

Hello,

We have contacted support about your problem and wating for their response.

I must add that saying “they are the same” is not quite fair. We worked really hard on both items and they have really different structures, lifecycles and implementations. They even have different paradigms since one is imperative and other one is declarative.

In fact, it was even harder for us to make them this similar. They have different open source components. For example Dore has Select 2, Data Tables, Full Calendar, Dropzone etc. In response to this Gogo have React Select, React Tables, Big Calendar, Fine Uploader etc. Theming these different libraries with different styles and usage was not an easy task that we could take some code from one and add it to other.

Regards.

Hi,

We have got a response from support and as the refund policy states that we don’t have to accept refunds on items which user bought by mistake or user changed mind.

Sorry about that.

Regards.

Hi,

Another user experienced the issue and we were able to replicate it on a Macbook. Asking for a future update, are you also on a Mac?

Problem is about webpack-cli package, solution is uninstalling and installing again this package via npm.

—-—-—-—-—-—-—-—
To get it working uninstall webpack-cli with following command.
npm uninstall webpack-cli

After uninstalling complete install it again with following command. This should install webpack-cli 3.1.2
npm install webpack-cli --save-dev

After this, you should be able to use npm start and npm run build.
Please let us know if that solves the problem.

Regards.

Hi Timo,

We can not provide a trial or a light version. It’s an Envato rule.

If your developer has no experience with using and building React code, npm, Nodejs and Redux then we suggest that Gogo is not a good choice for you. Node.js is responsible for loading packages and running the project but React has a very different syntax and lifecycle than regular html/jquery projects.

Regards.

And you should also check and be sure that port 3000 is not in use, you have administration authorization on command line. You might also want to check your log as the error suggests. /Users/krishnakumar/.npm/_logs/2018-09-29T07_57_30_567Z-debug.log

I think some problem with the theme I have done npm install and then npm start. My other applications with react is working absolutely fine. but I am getting error with your template and screenshot is here. Check the circled error related to template. https://ibb.co/fGsMZK

Give me a solution asap.

Hello,

It seems like the problem occurs on some Mac computers and it is about webpack-cli package. We have not experienced it on Windows. Googling the error quickly pointed us to the solution. For more information you may check here: https://github.com/webpack/webpack/issues/8082

After this, you should be able to use npm start and npm run build.

Regards.