52 comments found.
Hi , I just bought it but I have a question, I would like to use this template on my project but do you have a guide how to implements or what do we need to import to my recent project?
Regards
Hello, thanks for buying our product.
The simplest way to work with this theme is to create your new routes using the file system provided by Nuxt, as you can see at https://ignity.co/demo2/admin/doc/basic/getting-started. If you want you can also directly import components into your project, copying a file from the component you want to use, and taking care of possible imports.
Best Regards
Hi there ,
Could you help me to import all the components and keep it each ready to use? I would pay for this
Hello,
What type of component do you want to import? Could you give us an example?
Thanks
Hi, I would like a simple NuxtJS project with the style (Demo 1) as a main layout ready to use any component
Hello,
To keep one theme in the project, to prevent the others from being loaded, just locate the theme/client/layouts/_admin.vue file and remove the SCSS import from the themes you will not use. To start using the components, just create a .vue file inside the theme/client/pages/ folder, importing the components you will use, using the Nuxt default.
Hey there,
It’s great product, and I had liked your coding standards as well, but I have some requirements, I mean I have one project on NuxtJS, and I want to use your theme as a component, so do you have any guide that I can use only of your components & assets, this can help me a lot.
Thank you.
Few more things, I had tried to copy only components and layouts but then I fall into this error, https://prnt.sc/ubp7xb https://prnt.sc/ubp8ha. Maybe you can help me to find solution for this?
Thank you.
Hey, you can ignore this. I just figured everything! Really great work man! Thank you!
Thank you very much for the feedback.
Let us know if you need anything.
HI
I found this line yarn serve in readme not work. It should be yarn dev to run selfhost.
Best Regard
Hello,
Our theme was initially approved for version 10.00 of Node, but we have already performed some preliminary tests here in the last stable version of Node (14, the same one you are currently using), and it is fully compatible, in this case just update the package.json file by changing the line: “node”: “^10.0.0”, to “node”: ”>= 10.0.0”,
Use the “yarn dev” command to upload the project under development.
We will update the session in the documentation that deals with the subject, thanks for contacting us.
Sincerely,
Hi I am new for nuxtjs.. I download and follow readme, when I user yran install console shows error IGNITY@1.1.0: The engine “node” is incompatible with this module. Expected version “^10.0.0”. Got “14.4.0”
so, yarn have to use nodejs 10.0.0 ?
Best so, yarn have to use nodejs 10.0.0 ?
Best Regard
Hello,
Our theme was initially approved for version 10.00 of Node, but we have already performed some preliminary tests here in the last stable version of Node (14, the same one you are currently using), and it is fully compatible, in this case just update the package.json file by changing the line: “node”: “^10.0.0”, to “node”: ”>= 10.0.0”,
Use the “yarn dev” command to upload the project under development.
We will update the session in the documentation that deals with the subject, thanks for contacting us.
Sincerely,
Hello, can you let us know How to remove featherjs ?? We have already designed backend system to work with.
Hello, how are you?
To remove Feathersjs completely just ignore all content in the src folder, with the exception of /src/middleware/nuxt.js and /src/middleware/index.js files, it’s responsible for the route inclusions in Express.js (assuming your backend is compatible or based on this one)
I hope I helped you.
Sincerely,
Hi,
I have just spend about 5 hours today trying to get the authentication to work correctly and i have been going in cirlces without it getting to work.
What I have done: - Applied a middleware to the routes in nuxt config to make any non authenticated user redirect to the login screen - Login works. But when you refresh the page the client app doesnt authenticate the user. I have been trying lots of methods to get this to work and none seem to work.
I have followed this: https://vuex.feathersjs.com/common-patterns.html#full-nuxt-example
But I get the issue that makeAuthPlugin is not a function.. which is because ‘feathers-vuex’ is a crazy old version.
https://github.com/feathersjs-ecosystem/feathers-vuex/blob/a33feaa428877031cc3ee53a99cc7fe62730a6e1/docs/2.0-major-release.mdFeathers-vuex really needs updating. I can’t believe this theme is advertised as ‘enterprise’ production ready and its running 2 major versions behind on its core code.
The whole theme fails the npm audit and reports 47 vulnerability from old packages. It cant be right to use a theme with vulnerabilities.
Feathers is a major version behind with 4 now available and it running version 3. Cookie store is version 3 when 6 is available. NeDB 4 when 5 is available.
Please can you update the theme so that it can be used to modern standards and examples?
I feel like just fixing the auth to work is not a fair approach. Because once I finish developing the app and release it, it will be more outdated. And it will need re-developing eventually.
If the theme can be updated it will be a great theme and I am really looking forward to using it.
Regards
Hello,
We’re sorry you’re having trouble using the theme and its versions, I’ll try to help you with the minor issues right away, but in about 4 weeks we’ll release a major update on the theme already with the new versions.
About the vunerabilities you can run the npm audit fix npm audit fix—force
that the packages will be updated in their minority versions with the proper fixes without any break in the project.
About authentication not occurring on the client side, if you are talking about the automatic authentication that occurs naturally on the pages, you can check if the layout file you are using (directory /client/layout), contains the call:
this.$store.dispatch(‘auth/authenticate’)
this call is responsible for the magic of automated authentication.
We are at your disposal for any questions.
Thanks for the advice on the authentication side. I just tried it thought and still wasnt able to get it to work 
I tried a few places in layout + on authinit .then() and no luck. Tried these also: https://github.com/feathersjs-ecosystem/feathers-vuex/issues/78
And even more thanks for the quick update and positive news on a theme updated with the relevant package updated 
I am really excited about this 
If the update and include a fully working end-to-end client / server authentication setup that would be awesome. Its been a real difficult thing to get right for me.
Also I seem to be struggling to get all the font awesome icons to load. It seems some of them dont work, not sure why. It seems simple. I am setting icon to things like “money”, “wallet”, “coin” and they are not displaying. Any idea why?
The icons it seems to be missing icons from the dual-tone icons folder is causing the issue
Hello,
The dual-tone icons are based on SVG files, and you must define them according to the file name in the client/static/img/icon/dual-tone/ folder. If you need to add some new icon just add a new SVG file following the color pattern of the others so that the system makes the change according to the chosen theme.
Thanks, any idea where i need to insert the auth code in the layout?
Hello,
You can add the call in the mounted function of the layout, as below:
mounted () { this.$store.dispatch(‘auth/authenticate’).catch(error => { if (!error.message.includes(‘Could not find stored JWT’)) { console.log(error) } }) }
This way every time any page is rendered, it will try to send the login data previously saved in the browser.
If you are interested, send me a private message through themeforest with your contact details, I can send you the version that will be published in the next days.
I sent you a message about the newer version. I tried that code as well and it didnt seem to work. I added some console logs and the page was loading before any of that fires. I’ll just wait for the update to fix it I think, I feel defeated on this one haha!
Hello,
I’ve already forwarded to your mailbox the link to the new version, the same one I’ll update next on themeforest.
Anything just let us know.
Hi I love the dashboard i just had a few questions is it possible to have just the base nuxt installation then with it set up one admin dashboard without all the other stuff ?
Hi, thanks for the feedback.
If I understood your question, to have only the base of the panel just delete all the files from /client/pages (responsible for the routes) and start your development by creating new routes.
I hope you’ve answered your question.
Hi, I have a question, I want to use that “ContextSideBar” from mail pages, the one with the text “Buddy online”. I have tried to import this component on my home vue component but it doesn’t show the proper style. Copying all the style properties on that mail/index components isn’t working. I just want to use that “side panel”. Thanks in advance.
Hello,
You don’t need to import the component that is in Client/Base/Menu/ContextSideBar it is already included by the main layout. To use it on your page on the page you are trying to render, set the ‘layout’ property to ‘admin’ as in the example on the email page, and edit the ContextSideBar component by importing the new context component into it and changing the mapModuleBySideBar variable with URL mapping made to the context component, it will appear on your page already with the base styles applied.
I hope it helped.
Hi, I want to add a new item on the TopMenu items object. When I add a new one it replaces another that currently exists, which is the best way to add new items here?
Hello,
The top menu component uses the same array of menu items as the side menu, due to size limitation it displays 4 items at the top (the rest are included in the “More” menu item) If you want to change the menu items just edit the file: /client/util/menu/items.js If you are going to use items other than sidebar, then I advise you to change the menu object that is searched in /client/layout/_admin.vue
I hope you’ve cleared your doubts.
Sincerely,
Thanks!, Another question, how can I get rid of feathers? I don’t want server logic frameworks like that inside this app. I would like to have some easy steps to remove the entire feathers thing without causing problems on the app.
Hello,
You can remove the feathers by changing the key: “dev”: “cross-env DEBUG=nuxt:* nodemon—max-old-space-size=8192 src/”, to: “dev”: “nuxt—max_old_space_size=8192—optimize_for_size”, in package.json
And commenting or removing the key: serverMiddleware in the file: nuxt.config.js
Remembering that some components search for data using actions created by feathers, these components need to be changed if you are going to use them.
Thank you so much!
Hi, I can´t install because I get this: npm WARN tar ENOENT: no such file or directory, open ‘C:\plantilla\theme\node_modules\.staging\cliui-4bc790be\package.json’ npm WARN tar ENOENT: no such file or directory, open ‘C:\plantilla\theme\node_modules\.staging\cliui-4bc790be\CHANGELOG.md’ npm WARN tar ENOENT: no such file or directory, open ‘C:\plantilla\theme\node_modules\.staging\cliui-4bc790be\index.js’ npm WARN tar ENOENT: no such file or directory, open ‘C:\plantilla\theme\node_modules\.staging\cliui-4bc790be\LICENSE.txt’
and more lines like this At the end I get this:
npm ERR! code ENOENT npm ERR! syscall spawn git npm ERR! path git npm ERR! errno -4058 npm ERR! enoent Error while executing: npm ERR! enoent undefined ls-remote -h -t ssh://git@github.com/anthonypaparella/aos.git npm ERR! enoent npm ERR! enoent npm ERR! enoent spawn git ENOENT npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent ------------------------------------------ Please could you help me?
Hello,
Make sure you have the GIT installed on your device and accessible globally. Try to type git -v in the CMD. If it returned that the command is not recognized and GIT already installed, then you need to add it to the PATH environment variable and make sure to try the command using a new CMD session.
After that try again to perform the installation.
Hi, I need help. I want to know how to easily avoid the nav-sidebar on a particular component. for e.g. the login. Where and what should I change?
Also, how can I avoid using nuxt or whatever the thing that is rendering all the routes?
Hello,
To create pages without the menu structure create a file called blank.vue in the folder /client/layouts/ with content from this link: https://pastebin.com/99xJpdwB and in the root file of the page (/client/pages/frontend/user/login.vue), change the property layout to: layout: ‘blank’. We will release this layout without menu in the next version.
The nuxt in default mode, is used only as a helper to create routes automatically (based on the files contained in the directory in client/pages) and assists in the file structure, it does not pre-render routes, unless you put it in SSR mode. All components are made in pure vue, it would be possible to use them in another project, but as Nuxt creates a layout structure for each page it would be necessary to manually code something to suit you in this case.
Thanks for the response! another quick question, which is the best way to use Vuex store here? I mean, If I want to save a variable on the store (In a specific Vue component) and get it in another Vue component like replicating the localStorage behavior.
For example, I want to commit an action to store the current theme skin but I don’t know the right way to do that without getting the error “converting circular structure to JSON”.
nvm, figured out. vuex persisted module problem
Okay, if you have any new questions, we’re at your disposal.
hello good afternoon
please i get this error when i run ‘yarn run dev’
ServerMiddleware should expose a handle: /Users/chun/projects/nuxt-dash/src
i dont know what is wrong.. kindly help me
Hi, thanks for getting in touch, check if the package.json file contains this value on line 63: “nuxt”: “~2.10.0”
If not you can change to this or download the latest version on themeforest
Okay works now.. after downloading the new version on themeforest.. thanks!
Hi,
the live demo link has not been working for some days, is there any other way to see the demo,
thnx, 4/13/20
nvm, I removed the envato frame and toke me to : http://ignity.co/frontend/
Hello, thanks for warning, in which browser are you trying to access the demo?
chrome
Hello, you can try clearing your browser cache and perform a new test, we tested with the latest version of Chrome and it was possible to open the view normally.
thank you, please don’t worry about me, i checked the demo on your website already, and its great by the way, just telling you, because of the new possible customers. a quick question, is there any chance that I can change the transitions of the left side menu, i would love to have a more smooth transition.
Hello, anyway thanks for getting in touch.
About the menu animations, yes it is possible to easily change these animations, Vue natively offers special components to animate transitions (https://vuejs.org/v2/guide/transitions.html) and the components used to create the menu make use of this component. In this way you can create the CSS with the desired animation and change a parameter in the transition components of the menu.
i have an error
ServerMiddleware should expose a handle: ignity-admin\src
when i run npm run dev and i got a url localhost:3031 but on my browser NuxtServerError ServerMiddleware should expose a handle: D:\ignity-admin\src
Hello,
Thanks for contacting us, current project is broken due to an update in a project used in the theme, an update was released on Nuxt that broke the build. We have already sent an update to ThemeForest fixing the error and are waiting for its approval.
Meanwhile you can manually adjust your project:
To fix it manually just locate the line 62 in the package.json file, and change it to: “nuxt”: “~2.10.0”,
Then just run the “npm install” command again. You may need to delete the node_modules folder within the project before running the mentioned command, so that no cache is kept.
look like the table is also broken, there are curly braces in the fullname column and items in action column wont show
i had to use v-slot:cell(name)="row" to properly display items
Thank you very much for informing us. We have made an update on the mentioned page with the new syntax for slots.
Hello,
out of the box this does not work on run dev:
› Creating webpack middleware… 12:51:12 error: Unhandled Rejection at: Promise {key“}
Hello,
Sorry for the problem presenting, in fact the error message you informed has no relation with current problem in the project (it refers to the fact that the test data are already registered) but the current project is broken due to an update in a project used in the theme, an update was released on Nuxt that broke the build.
To fix it manually just locate the line 62 in the package.json file, and change it to: “nuxt”: “~2.10.0”,
Then just run the “npm install” command again. You may need to delete the node_modules folder within the project before running the mentioned command, so that no cache is kept.
We will also send a new version to ThemeForest fixing the problem, in a few days the final project will be updated .
we encounter a problem when we are in mobile mode as buttons and inputs such as radio checkbox etc. are not clickable. Also how can we set a different default thema?
Hi, thanks for letting us know about the problem involving the mobile version and the action buttons.
We have already sent a new version to Themeforest and soon the update will be sent to all customers.
To fix it locally just change it in the file: /client/components/Base/Page/PageWrapper.vue on line 4
from: class=”d-flex” to: :class=”{‘d-flex’: isCenteredContent}”
Full version of the file after correction: https://pastebin.com/rd5T9pGS
To change the default theme, locate the file /config/layouts.json Just configure the “default” key, changing the skin property to the desired skin, and the other parameters according to your needs.
I hope it helped you.
would you happen know how to incorporate this into typescript?
You can easily use typescript in this project using the official nuxt modules.
Follow the link with installation and configuration guide:
https://typescript.nuxtjs.org/guide/setup.html#installationIf you have any other questions, let me know.
i did follow that guide, but i was not able to get feathresjs to use the middleware for nuxt
Hello,
We are testing the scenario you need and will soon give you more details.
Hello,
It was possible to integrate TypeScript to Nuxt following the site guide, some changes were necessary in the Midleware server to make nuxt compile normally.
I sent you the modified project in the private, while we thought about a way to officially release it to everyone, basically the following files were changed:
As in the official guide: nuxt.config.js package.json tsconfig.json
In middleware:
/src/middleware/index.js /src/middleware/nuxt.js /src/app.js
I also created an example page / route using TypeScript: /client/pages/admin/basic/typescript-example.vue /client/types/index.ts
I hope this helps you with your project. Let me know if you need anything else.
silly question, but where did you send it?
i found, it i see your using commonjs. have you tried ES6?
Hi, I didn’t try ES6 in the middleware yet.
do you know if its possible to use feathers-vuex ^3.6.1? I get an error in the store/index.js over the service function used in the plugin export.
Hello,
The version you want to run of feathers-vuex has had updates that break the previous compatibility, so the error message you mentioned. In this case you need to rewrite the services source files to the new format supported by feathers-vuex.
If you have questions about the new way to declare services, I suggest you use feathers-cli to generate the new services according to your needs (after updating the project package).
Further adaptations to the code may be necessary for full operation.
ya, i ended giving up on using the latest version =)
Hey your preview is broken.
Hi, thank you for contacting me, could you tell me more details how to simulate the problem?
If you can try the most up-to-date version of your browser, clearing your cache, you may be successful. Around here we are getting access normally in the preview.
is there a stripped down version to create new project without any of the sample and demo pages? i’m not 100% sure where to hunt down the demo and sample page references to remove them from the project i’m testing with.
Hello,
This project uses nuxt to dynamically manage routes/pages, so it reads all the .vue files in the client/pages folder at the root of your project, and generates the routes to the demo pages. This way to remove the demo pages (and all routes), just delete all content from that folder. The same goes for creating new pages, just create a .vue file inside it.
I hope you have solved your doubt/need otherwise let me know.
Cheers
in the nuxt.config.js, is it safe to remove the extendRoutes block? I don’t understand what its doing with the demo layouts here.
Hello,
Yes, it’s safe to remove this setting, it only allows you to access the various skins/demos via the demoX URL (X equal to the skin number). You will only lose the skins selection feature via the icon fixed on the right side of the demo.
I hope you’ve cleared up your doubts. Cheers
