95 comments found.
Hi, I have purchased this theme yesterday as we liked the layout a lot. Now the challenging part starts of getting it to run on my machine. I am facing issue with installing node 15 as well as fibers. Both fail for various reasons. Can you please suggest a clean way to this?
Npm version is 8.19.4, Node version is 16.20.2.
In Windows, I had to manually extract the zip file of Node 15.14.0 in the nvm folder. And npm 7.7.6 was picked properly. After this, there was issue of fibers which only works with Node 14. So commented the line from webpack.config.js to not require fibers. And then uninstall fibers with command “npm uninstall fibers”. After this, node_modules was donwloaded properly though many libs deprecated. But it ran the project successfully.
Hey, I didnt realise this is quite outdated. Are you able to issue a refund please? or do you have an updated version that is secure?
Hey there,
We would surely able to approve refund if you have no downloaded the item.
Regarding update, we have not planned yet but sure thing there will update in future once Vuetify public latest version with Vue 3.
Hoping for the best!
Best Regards, Jack
What vuejs version it is?
Hey there,
Thanks for reaching us. Vue Js version is 2.6.11.
- Best Regards, Jack
Hello, Does the file provide static HTML files of all pages? theme: VueJs CLI Material Admin
Hey there,
Thanks for writing to us. This is Vue JS specific theme, thus we don’t have static HTML files for all the pages.
Feel free to write us in case of any other questions.
Best regards, Mia
يواجهني خطاء في تشغيل القالب ارجو التواصل علي رقم 01110357707
Hello there,
Thanks for writing to us.
You may get almost all question answered with our documentation. https://vuse-documention.hexesis.com/introductionUnfortunately, we don’t provide telephone support, Hence kind request to share exact issue that you are facing in English for better understanding.
Looking forward to hearing from you.
— Best regards, Mia
Hello i worked with this admin panel and I really like it. I want to get new licence for my new project ,but i have recognized that it did not updated to work with new node and npm version , Do you have any plans to update it ? Thank you
Hello there,
Thanks a bunch for writing to us and appreciation. To be honest, yes we will have update for sure but don’t have defined date for it.
— Best regards, Mia
Hi I am Missing Binary error while installing. can you please help.
Hello Rahul,
Thanks for writing to us. Kindly ask you to try with node v15.14.0 (npm v7.7.6). It should work.
— Best Regards, Mia
Hello,
using the template with the demo to add pages in the sidebar I used navigation-items.js with the same format as in the demo site, however the names are displayed with the prefix “Vuse.AppDrawer.”, I do not know how to have only the labels without the prefix, would you have an idea of how to correct this?
Thank you.
Hello,
Our sincere apology for such a late response. Could you please clarify, are facing any issue with demo or skeleton project with more details ?
You must have navigation-items.js and _navigation-items.js.
/demo/src/layouts/App/ReadMe.md
This readme file would help you to solve your question. Nevertheless, feel free to write us if you need any further help on this.
— Best regards, Jack
Or have the project compile this error
error in ./src/main.js Module build failed (from ./node_modules/thread-loader/dist/cjs.js): Thread Loader (Worker 0) Module.createRequire is not a function at PoolWorker.fromErrorObj (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/thread-loader/dist/WorkerPool.js:262:12) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2359:26) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/eslint/lib/cli-engine/cli-engine.js:33:5) at Module._compile (internal/modules/cjs/loader.js:778:30)
@ multi ./src/main.js ERROR Build failed with errors.
Hello Scantec,
Sorry for late response! We are trying to reproduce this issue with our machine.
Could you please provide below details ? 1. npm and node version 2. Step to reproduce this
Looking forward to hearing from you.
— Best Regards, Mia
Or have the project compile this error Module build failed (from ./node_modules/thread-loader/dist/cjs.js): Thread Loader (Worker 0) Module.createRequire is not a function at PoolWorker.fromErrorObj (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/thread-loader/dist/WorkerPool.js:262:12) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2359:26) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/eslint/lib/cli-engine/cli-engine.js:33:5) at Module._compile (internal/modules/cjs/loader.js:778:30)
Building for production…
ERROR Failed to compile with 1 errors 11:31:39 PM
error in ./src/main.js
Module build failed (from ./node_modules/thread-loader/dist/cjs.js): Thread Loader (Worker 0) Module.createRequire is not a function at PoolWorker.fromErrorObj (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/thread-loader/dist/WorkerPool.js:262:12) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2359:26) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/jpinto/Desktop/themeforest-Hb9y5mHF-vuse-vuejs-cli-material-admin/demo/node_modules/eslint/lib/cli-engine/cli-engine.js:33:5) at Module._compile (internal/modules/cjs/loader.js:778:30)
@ multi ./src/main.js
ERROR Build failed with errors.
I ran “npm install” and got this result,
npm WARN EBADENGINE package: ‘morris.js@0.5.0’, npm WARN EBADENGINE required: { node: ’>=0.8 <0.11’ }, npm WARN EBADENGINE current: { node: ‘v14.15.5’, npm: ‘7.17.0’ }
Could you advise on the issue.
Thanks.
Hello there,
Thanks for writing to us.
We have just try to regenerate this issue for npm install with fresh setup. Unfortunately we are not able to re-generate this issue at our end.
Could you please share step to reproduce it ?
Screenshot: https://www.dropbox.com/s/oypn9ye7ncgo1i8/Screenshot%202021-08-16%20at%2012.33.12%20AM.png?dl=0
Below is our Node | Npm version. We would request you to check you node setup.
➜ demo npm -v 6.14.13 ➜ demo node -v v14.17.0
Feel free to write us with steps.
— Best Regards, Mia
hi team you need to solve this fibers problem.
node v14.17.4
npm 6.14.14
and i cant install
it gives error “Failed at the fibers@4.0.3 install script”
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment—
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
i’m almost end my project and need to compile again some other machines.Urgent ! help needed
Hello there,
Thanks for writing to us.
We have just try to regenerate this issue for npm install with fresh setup. Unfortunately we are not able to re-generate this issue at our end.
Could you please share step to reproduce it ?
Screenshot: https://www.dropbox.com/s/oypn9ye7ncgo1i8/Screenshot%202021-08-16%20at%2012.33.12%20AM.png?dl=0
Below is our Node | Npm version. We would request you to check you node setup.
➜ demo npm -v 6.14.13 ➜ demo node -v v14.17.0
Feel free to write us with steps.
— Best Regards, Mia
I can’t get the latest version running. Any suggestion where to open an issue, I can provide some screenshots and details.
Coming back to this, it doesn’t work with npm V7, with npm6* and nodejs14 it works.
d:\Training\themeforest\demo>npm -v 7.16.0
d:\Training\themeforest\demo>node -v v16.3.0
Hello Klodoma,
Thanks for writing to us and regret for a bit late response.
It’s working fine with Node (LTS): Npm: n6.14.13 Node: v14.17.0
If you are facing issue use below command to fix it.
npm i fibers <pre> -- Best Regards, Mia</pre>
Yes, it works with nodejs 14 npm 6. It doesn’t work with nodejs 16 npm 7
tnx for reply. i did it according to your instructions. I’m putting my solutions here for further usage who may need. i add new toolbar named “webtoolbar” and make it active denpendig to “navs” variable. may be you can add proper documentation for different layout usage..
const WebToolbar = () =>
import (
/* webpackChunkName: "WebLayout", webpackPreload: true */
"@/layouts/Web/Toolbar"
)
const AllRoutes = [...VuseRoutes]
const routes = AllRoutes.map((route) => {
const { params, defaultComponentPath, navs } = route
const componentObj = navs ? {
components: {
default: LazyLoad(defaultComponentPath),
sidebar: AppSidebar,
header: AppToolbar,
footer: AppFooter
}
} : {
components: {
default: LazyLoad(defaultComponentPath),
header: WebToolbar,
footer: AppFooter
}
}
return {
...params,
...componentObj
}
})
hi, i want to create different layout for website and admin panel but i cant figure it out. how can i set different layout for different routes,i cant find how did you forward chat and contact app to inner layout. thank you for your help
Hello Drascom,
Thank you for writing to us.
You can refer the router/routes.js where you can see from line No.21 to 32. It’s rendering the navigations conditionally. Now, you can open any route from routes folder – I am referring here Chat route from applications.js. You can also play with enable disabled navs attribute true/false. Hence, how you configure your route, it will behave accordingly.
For your question regarding Admin v/s website routing, router/routes.js would be your best friend. You can configure the layout and routes the way you want.
We are using named router-view for all navigation (header, footer and sidebar). if you provide it then only it will render.
— Best Regards, Mia
Hello,
I bought Vusejs template but I couldn’t use in my Nuxt project. Could you please prepare a skeleton for nuxt project? Because it is very important for me.
Thank you.
Hello mustafadeep,
Thanks for writing to us.
Vuse admin is Pure Vuejs CLI Admin template. We are not giving any support for nuxtjs for this item.
However, you can refer Vuetify below link for the nuxtjs integration. https://vuetifyjs.com/en/getting-started/quick-start/
— Thanks, Mia
Hello again, I am trying to migrate it to Nuxt since this morning. I couldn’t make it because there are lots of dependencies. Mixins, languages, configures etc. It is very well-made template. Please migrate it to nuxt for me. really, I want to make a project with your templates but it is useless if I can not use it with Nuxt.
It will be beneficial for you as well because customers are looking for support for Nuxt.js as well. It will be easy for you guys to migare it to Nuxt because you know this stuff.
Thank you.
Hello Mustafadeep,
Thank you for writing us back.
Unfortunately we are neither providing any support nor working on Nuxt.js. This theme is purely on Vuejs using Vuetify.
For now, there is no plan to convert/provide this theme in Nuxt.js. However, we have already noted the same in our reminder for future plans.
— Best Regards, Mia
We have trouble setting up the demo application. The skeleton application works without issue but the demo application keeps giving us issues with babel. After many installations regarding babel, we are however stuck with this error message “Error: Plugin/Preset files are not allowed to export objects, only functions. In {project_path}/node_modules/babel-preset-stage-2/lib/index.js”.
We have tried every suggested solution but we cannot seem to be able to get out of this and have been stuck on it for the past two days
Hello intelldannel,
Thank you for writing to us.
Both demo and skeleton has same package.json file. Only difference between these two different setup – skeleton is clean quick start project without any examples. Hence, it should be working, there is no specific/manual configuration required.
We have also performed a cross check, out team has also downloaded current bundle. Both are working fine.
Our machine NodeJs version: v14.16.0 Our machine npm version: v6.14.11
May I ask you to perform below steps:
Solution 1
1. remove node_modules package-lock.json 2. npm install
Solution 2
1. Download fresh copy from themeforest and try to install again
Looking forward to hearing from you .
Best Regards, Mia
lang
-en
-vuse
-xx.json
because of that i need to call all translation files like Vuse.Customers.CustomerName
i think en/index.js file not importing other folders under current language folder. can you provide any solution for this.
Hello Drascom,
Thanks for writing to us.
We have checked at our end. I confirm hereby, you must be able to add files and folders as many as you want for language.
You can see the same example in our demo project code as well. I would suggest you to restart your dev server, once you add any new file/folder for locale.
We have also checked with our Skeleton Project as well.
en/
test/
AntherFolder.json
vuse/
AnotherFile.sjon
AppDrawer.json
We are able to access it.
<h2 class="display-1">Hello Profile {{ this.$route.meta.props }}</h2>
<p>{{ $t(`Vuse.AnotherFile.SomeKey`) }}</p>
<p>{{ $t(`Test.AnotherFolder.SomeKey`) }}</p>
However, you are free to customise the way you want as your project requirements
— Best Regards, Mia
yes i test and it is working now the key is restarting dev server tnx.
do you have any system bar design for debug runtime errors. mine is looking very ugly inside of yours.
Hello Drascom,
Thank you for writing to us.
We are pleased that it works for you. Regarding runtime error handling, we don’t have any system to debug runtime errors by default.
— Best Regards, Mia
hi i just bought your products.But i have one issue about router. At the route with path xxxx/:id if navs:false i can get id as props in component if navs : true props getting undefined
sample route { params: { path: ”/customers/:id”, name: “customers/CustomersProfile”, props: true, }, defaultComponentPath: “Pages/Customers/Profile”, navs: true, }, at profile.vue file props is undefined until change navs: false
how can i solve it
Hey Drascom,
Thanks for writing to us.
Better to write this way in your case.
{
params: {
path: '/customers/:id',
name: 'customers/CustomersProfile',
meta: { props: true },
},
defaultComponentPath: 'Pages/Customers/Profile',
navs: true,
},
Params would take path, name and meta. In meta, you can provide any additional config.
Please read more on routing on this: https://router.vuejs.org/guide/advanced/meta.htmlHope this help you.
— Best Regards, Mia
i’m sorry it still not working.
with meta: { props: true }, props undefined at all no matter navs is true/false.
i’m getting id prop from this.$route.params.id, for now
somethings happening here i suppose const componentObj = navs
? {
components: {
default: LazyLoad(defaultComponentPath),
sidebar: AppSidebar,
header: AppToolbar,
footer: AppFooter,
},
}
: {
component: LazyLoad(defaultComponentPath),
};
Hello drascom,
The given solution must work.
Kindly refer attached screenshot for the same. https://www.dropbox.com/s/owvxv6b44m4mwzv/Screenshot%202021-04-02%20at%2010.37.50%20AM.png?dl=0— Best Regards, Mia
{
params: {
path: "/customers/:id",
name: "Test",
props: true,
},
defaultComponentPath: "Pages/Customers/Profile",
navs: true
},
and this is the navigation item
{
icon: "dashboard",
title: "Test",
name: "Test",
i18n: "Test",
href: "/customers/60583620656639035b000264"
},
your navigation item component can use href if exist instead of name .
now i can get :id props to test details page .
tnx for replies by the way.
it is good to now there good support here..