Hola,

¡Gracias por contactarnos!

Por favor explique el problema en detalle. Estaremos encantados de ayudarte.

También puede enviarnos sus problemas a support@theironnetwork.org

¡Gracias y que tenga un buen día!

Hi,

Thanks for reaching out!

Regarding your query, Please follow the below steps to fix this:

Step 1. Go to src/sagas/ and open Auth.js and find signInUserWithEmailPassword function and Replace the whole function to following: function* signInUserWithEmailPassword({ payload }) { const { email, password } = payload.user; const { history } = payload; try { const signInUser = yield call(signInUserWithEmailPasswordRequest, email, password); console.log(‘user_id’, signInUser) // check data is store in signInUser or not. if (signInUser.message) { yield put(signinUserFailure(signInUser.message)); } else { console.log(‘11 local’, signInUser.user.uid) // check uid in console window localStorage.setItem(‘user_id’, JSON.stringify(signInUser.user.uid));

var getData = JSON.parse(localStorage.getItem(‘user_id’)) yield put(signinUserSuccess(getData)); history.push(’/’); NotificationManager.success(‘User Logged In’); } } catch (error) { yield put(signinUserFailure(error)); } }

Step 2. Now, import notification manager component:- import { NotificationManager } from ‘react-notifications’;

Step 3. Now Go to src/reducers/AuthUserReducer.js and update the below cases:- case LOGIN_USER_SUCCESS: return { ...state, loading: false, user: action.payload };

case LOGOUT_USER_SUCCESS: NotificationManager.success(‘User Logged Out’); return { ...state, user: null };

Let us know if you have other queries at support@theironnetwork.org

Thanks and have a nice day!

Thank you, it works! Another question connected to notifications. Is it possible to localize notifications with the same locale files: src/lang/locales?

Hi, I have another question connected to notifications. Is it possible to localize notifications with the same technique (files located in src/lang/locales)?

tried but no luck.. Sent a mail to support email id with sample code… please check and let us know asap

Replied to your email. Thanks!

thanks

Hi,

Thanks for your kind words! We appreciate it!

We were updating some server files. So that is why demo of our themes not accessible at that time, but now we successfully updated all the files. Now you able to see the demo without any issue. Please Clear your browser cache First before checking the demo.

Let us know if you are having still issue with our demo.

Thanks and have a nice day!

Hi,

Thanks for reaching out!

Sorry for the delayed response.

Regarding your query, we did not tested as such with reactify but there are several steps that you have to add some integration methods for login with redux-thunk.

Step1. First, you have to update the AuthUserReducer (src/reducers/AuthUserReducer.js) case and its initial state and some switch case.

Step2. Then go to src/actions/AuthActions.js and create actions for login by using API with JWT token.

Step3. Go to src/routes/session/login/index.js and define the state and some functions and connect to store.

Let us know if you have any queries at support@theironnetwork.org

Thanks and have a nice day!

React compile Error occurred :

Failed to compile ./src/routes/session/lock-screen/index.js Module not found: Can’t resolve ‘Constants/AppConfig’ in ‘E:\Apache24\htdocs\react-saga\src\routes\session\lock-screen’

Please correct way to linking file folder and sub folder from any file location.

or have any trick to bypass this issue please tell me

Example : in the followiing case i have manually changes into the file

// rct page loader import RctPageLoader from ’../../components/RctPageLoader/RctPageLoader’;

// Session Lock Screen const AsyncSessionLockScreenComponent = Loadable({ loader: () => import(”../../routes/session/lock-screen”), loading: () => <RctPageLoader />, });

// app config import AppConfig from ’../../../constants/AppConfig’;

<Link to="/">
       
</Link>

Hi,

Thanks for reaching out!

We have checked this issue at our end, According to your manual changes to the files. There is one file path that you have to update is mentioned below Because the path you mentioned is not correct:-

// app config import AppConfig from ’../constants/AppConfig’;

After these changes run the template, which is working fine.

Let us know if you have any other queries at support @theironnetwork.org

Thanks and have a nice day!

Hi,

Thanks for reaching out!

We have fixed the issues and updated the package at themeforest. Please download the latest package and check once.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Hi,

Whenever we run “npm run dev” or “npm run watch-poll” commands, they compile the changes we have made in our react files by the help of laravel.mix and they automatically generate that chunks.

Regarding Languages Translation, If you are showing multiple languages on your template then yes you have to define that key-value pair in all your language JSON file. If you are adding a key-value pair only in English file if you select suppose Arabic then you will have errors in the console.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Thanks for your reply, i tried “npm run watch-poll” and it seems to be working sometimes and some other times not, for example, i run it in the background and i keep doing changes, and then i go to the browser to check my changes sometimes it’s working and sometimes it’s not working and i keep wondering why? and where was the problems? but when i run “nom run dev” it work and everything goes on the right way.

i just was wondering if there’s a way to work directly on the “Original files” without generating the chunks? just for quick development, because this way is slowing me down.

Thanks

Hi,

Yes, this happens sometimes, please follow given a link for better solution:

But make sure, whenever you make any big changes in your file try to run “npm run dev” to be fully sure that your changes will compile

The chunks will be generated every time when we compile the code so there is no way around to not to generate the chunks whenever we compile the code.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Please Correct All Warnings in the folder reactify-laravel\reactify-redux-saga

“C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” install—scripts-prepend-node-path=auto npm WARN deprecated extract-text-webpack-plugin@3.0.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin npm WARN deprecated superagent@3.8.3: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once i t is released. npm WARN deprecated intl-relativeformat@2.2.0: This package has been deprecated, please see migration guide at ‘https://github.com/formatjs/formatjs/tree/master/packages/intl-relativeformat#migration-guide' npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.

> grpc@1.23.3 install E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\grpc > node-pre-gyp install—fallback-to-build—library=static_library

node-pre-gyp WARN Using request for node-pre-gyp https download [grpc] Success: “E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown\grpc_node.node” is installed via remote

> node-sass@4.13.0 install E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\node-sass > node scripts/install.js

Cached binary found at C:\Users\xxgho\AppData\Roaming\npm-cache\node-sass\4.13.0\win32-x64-72_binding.node

> core-js@3.2.1 postinstall E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\@firebase\polyfill\node_modules\core-js > node scripts/postinstall || echo “ignore”

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

> core-js@2.6.10 postinstall E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\core-js > node postinstall || echo “ignore”

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

> protobufjs@6.8.8 postinstall E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\protobufjs > node scripts/postinstall

> uglifyjs-webpack-plugin@0.4.6 postinstall E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\webpack\node_modules\uglifyjs-webpack-plugin > node lib/post_install.js

> node-sass@4.13.0 postinstall E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\node-sass > node scripts/build.js

Binary found at E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\node-sass\vendor\win32-x64-72\binding.node Testing binary Binary is fine npm WARN rollback Rolling back readable-stream@2.3.6 failed (this is probably harmless): EPERM: operation not permitted, scandir ‘E:\Apache24\htdocs\reactify-laravel\reactify-redux-saga\node_modules\fsevents\node_modules’ npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN mui-datatables@2.12.4 requires a peer of material-ui/core^{3.2.0 but none is installed. You must install peer dependencies yourself. npm WARN mui-datatables@2.12.4 requires a peer of material-ui/icons}3.0.1 but none is installed. You must install peer dependencies yourself. npm WARN babel-core@7.0.0-bridge.0 requires a peer of babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN react-draft-wysiwyg@1.13.2 requires a peer of draft-js@}0.10.x but none is installed. You must install peer dependencies yourself. npm WARN canvg@2.0.0 requires a peer of canvas@^{2.1.0 but none is installed. You must install peer dependencies yourself. npm WARN canvg@2.0.0 requires a peer of jsdom@}13.0.0 but none is installed. You must install peer dependencies yourself. npm WARN canvg@2.0.0 requires a peer of xmldom@^{0.1.27 but none is installed. You must install peer dependencies yourself. npm WARN draftjs-utils@0.9.4 requires a peer of draft-js@}0.10.x but none is installed. You must install peer dependencies yourself. npm WARN html-to-draftjs@1.4.0 requires a peer of draft-js@^{0.10.x but none is installed. You must install peer dependencies yourself. npm WARN react-instantsearch-native@5.7.0 requires a peer of react-native@>= 0.32.0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#36> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN mini-css-extract-plugin@0.4.5 requires a peer of webpack@^{4.4.0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#38> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#39> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#40> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#41> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#42> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#43> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#44> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#45> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#46> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#47> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#48> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#49> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#50> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#51> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#52> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#53> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#54> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#55> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#56> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#57> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#58> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#59> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#60> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#61> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#62> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#63> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#64> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#65> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#66> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#67> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#68> requires a peer of @babel/core}7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#69> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#70> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#71> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#72> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#73> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#74> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#75> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#76> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#77> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#78> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#79> requires a peer of @babel/core^{7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#80> requires a peer of @babel/core}7.0.0-0 but none is installed. You must install peer dependencies yourself. npm WARN babel/<redpre#81> requires a peer of @babel/core^{7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN img-loader@3.0.1 requires a peer of imagemin@}5.0.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN The package axios is included as both a dev and production dependency. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {os“} (current: {os“})

added 1888 packages from 1162 contributors and audited 21847 packages in 300.104s found 10 vulnerabilities (5 moderate, 5 high) run `npm audit fix` to fix them, or `npm audit` for details

Process finished with exit code 0

Please Release Fresh Version with no warnings and Correct All Warnings and Remove old versions in the folder reactify-laravel\reactify-redux-saga

Hi,

Thanks for reaching out!

We are aware of these warnings. Our developer team already working on it and almost at the final stages of release. We will update the theme soon.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Hi,

Thanks for reaching out!

It seems that you are asking for seed (Skeleton project). Yes, We do have a seed project please check out the seed folder in downloaded files. We are providing seed project in the redux-saga and redux-thunk.

But regarding another part of your question, we do not have session pages for reactify in seed project and don’t have Firebase connectivity with it because most of the user wants to update there own custom code for login and signup as per the project requirement. So we keep it simple.

There is two way to use login page authentication with firebase or without firebase (API).

1. First, you have to create an API. We already use REST API in our full-stack version you can check there. Then copy session pages from full-stack reactify version to the seed project and then do the changes as per requirement.

2. Second You can use the Firebase method which is also defined in our full-stack version. After Creating API/firebase for login you need to import login files in app.js (src/container/App.js ) and create methods for login and logout functionality.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Im building a admin dashboard from scratch, i need use admin/ routes

this is my App.js file at root folder

const MainApp = () => ( <Provider store={configureStore()}> <MuiPickersUtilsProvider utils={MomentUtils}> <Router> <Switch> <Route path=”/admin” component={App} /> </Switch> </Router> </MuiPickersUtilsProvider> </Provider> );

i had change this file path to ‘admin’ because you had set as ’/’ and i need start app with admin route else this start with app/ routes

this is my container/App.js file

class App extends Component { render() { const { location, match, user } = this.props; }

//Test redirection not authentication
   if (location.pathname === '/admin') {
     if (true) {
       return <Redirect to={'/admin/dashboard'} />;
     }
     return <Redirect to={'/admin/login'} />;
   }
   return (
      <RctThemeProvider>
         <NotificationContainer />
         <InitialPath
            path={`${match.url}app`}
            authUser={user}
            component={RctDefaultLayout}
         />
         <Route path="/admin" component={CRMLayout} />
      </RctThemeProvider>
   );
}

this is my routes/dashboard/index.js file

import { AsyncAdminDashboardComponent, AsyncArtistComponent, AsyncArtistUpdateComponent, AsyncArtistAlbumComponent, AsyncAlbumComponent, AsyncSongComponent, AsyncCityComponent, AsyncUserComponent, AsyncPlaylistComponent } from ‘Components/AsyncComponent/AsyncComponent’;

const Dashboard = ({ match }) => ( <Switch> <Route path={`${match.url}/artists/albums/:id`} component={AsyncArtistAlbumComponent} /> <Route path={`${match.url}/artists/:id`} component={AsyncArtistUpdateComponent} /> <Route path={`${match.url}/artists`} component={AsyncArtistComponent} /> <Route path={`${match.url}/dashboard`} component={AsyncAdminDashboardComponent} /> <Route path={`${match.url}/albums`} component={AsyncAlbumComponent} /> <Route path={`${match.url}/songs`} component={AsyncSongComponent} /> <Route path={`${match.url}/cities`} component={AsyncCityComponent} /> <Route path={`${match.url}/users`} component={AsyncUserComponent} /> <Route path={`${match.url}/playlists`} component={AsyncPlaylistComponent} /> </Switch> );

this is my async component file

const AsyncAdminDashboardComponent = Loadable({ loader: () => import(“Routes/dashboard/index”), loading: () => <RctPageLoader />, });

const AsyncArtistComponent = Loadable({ loader: () => import(“Routes/dashboard/artist”), loading: () => <RctPageLoader />, });

const AsyncArtistUpdateComponent = Loadable({ loader: () => import(“Routes/dashboard/artist-update”), loading: () => <RctPageLoader />, });

const AsyncArtistAlbumComponent = Loadable({ loader: () => import(“Routes/dashboard/albums”), loading: () => <RctPageLoader />, });

const AsyncAlbumComponent = Loadable({ loader: () => import(“Routes/dashboard/album”), loading: () => <RctPageLoader />, });

const AsyncSongComponent = Loadable({ loader: () => import(“Routes/dashboard/song”), loading: () => <RctPageLoader />, });

const AsyncCityComponent = Loadable({ loader: () => import(“Routes/dashboard/city”), loading: () => <RctPageLoader />, });

const AsyncUserComponent = Loadable({ loader: () => import(“Routes/dashboard/user”), loading: () => <RctPageLoader />, });

const AsyncPlaylistComponent = Loadable({ loader: () => import(“Routes/dashboard/playlist”), loading: () => <RctPageLoader />, });

export { AsyncAdminDashboardComponent, AsyncArtistComponent, AsyncArtistUpdateComponent, AsyncArtistAlbumComponent, AsyncAlbumComponent, AsyncSongComponent, AsyncCityComponent, AsyncUserComponent, AsyncPlaylistComponent };

i only want add admin/dashboard route but doesnt works, the page dont load!

class App extends Component { render() { const { location, match, user } = this.props; }

//Test redirection not authentication if (location.pathname === ’/admin’) { if (true) { return <Redirect to={’/admin/dashboard’} />; } return <Redirect to={’/admin/login’} />; } return ( <RctThemeProvider> <NotificationContainer /> <InitialPath path={`${match.url}admin`} authUser={user} component={RctDefaultLayout} /> <Route path=”/” component={CRMLayout} /> </RctThemeProvider> ); }

i have make this change and change app to admin and route path to ’/’ but doesnt works, how i can disable joyride tooltip?

Hi,

We had tested the code that mention in the comment and found some issues in your code which leads to error. We made changes and fixed issues. Please follow the step below:-

1. First, you need to remove admin keyword from app.js file because we are setting here routing for theme, you can find the file “src/App.js” like below:- const MainApp = () => ( <Provider store={configureStore()}> <MuiPickersUtilsProvider utils={MomentUtils}> <Router> <Switch> <Route path=”/” component={App} /> //remove admin keyword </Switch> </Router> </MuiPickersUtilsProvider> </Provider> );

2. Second, you need to update in given file ”/src/container/App.js”

As per as your requirement that you need to change the app keyword with admin so here are we are doing the same.

class App extends Component {
    render() {
        const { location, match, user } = this.props;
        if (location.pathname === '/') { //remove admin keyword
            if (true) {
                return <Redirect to={'/admin/dashboard'} />;
            }
            return <Redirect to={'/admin/login'} />;
        }
        return (
            <RctThemeProvider>
                <NotificationContainer />
                <InitialPath
                    path={`${match.url}admin`} //update app keyword to admin
                    authUser={user}
                    component={RctDefaultLayout}
                />
                <Route path="/horizontal" component={HorizontalLayout} />
                <Route path="/agency" component={AgencyLayout} />
                <Route path="/boxed" component={RctBoxedLayout} />
                <Route path="/admin" component={CRMLayout} />
            </RctThemeProvider>
        );
    }
}

If you give us your email id then we will send you the working example as well.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

It’s been resolved. Thanks

Hi,

Unfortunately we are not very familiar with redhat OS, having said that we have faced similar issue a long time back with mac OS, we were able to resolve it via resetting the directory permissions properly.

Ok. You have changed _header.scss under assets\scss\custom.

Hi,

Thanks for reaching out!

You have to do some changes in SCSS file to fix the issue. Now Go to src/assets/scss/custom and open “_header.scss” file, And find the below code snippet :-

.app-header {
      .rct-header {
            z-index: 99 !important; // 1. Update z-index value.
            position: relative; // 2. Add position relative property.
            ...
      }
}

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Hi,

Thanks for reaching out!

We have given typescript guidelines in our documentation. Please check https://iron-network.gitbook.io/reactify/faqs#how-to-use-typescript-ts-code-in-reactify

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Hi,

Thank you for your interest.

Reactify is a basic react js template, You should consider reactify as a both starter app for react js developers and a learning source for new comers. You can link your database by using rest APIs.

We are also using firebase for some sections and JSON files for others.

Let us know if you need anything else at support@theironnetwork.org

Thanks and have a nice day!

Hi,

Thanks for reaching out!

Please make sure that you are using latest version of reactify. The error that you are mentioning seems that you may have old version of reactify.

We tested it at our end everything is working fine.

So, Please download the latest files from the themeforest and let us know if you have any problem at support@theironnetwork.org

Thanks and have a nice day!