1734 comments found.
When I purchased this, I received access to the Gitlab repo. It seems while this is still updated, I can’t see any Gitlab updates newer than 2 years ago. Did the repos change?
Hello PiousVenom,
Thanks for getting in touch. Yes, we moved away from GitLab to GitHub. You can raise repo request by filling up this form: https://tools.pixinvent.com/github/github-access. You can always download the latest package from themeforest as well.
Regards.
Hello – why hasn’t the React version of this theme been updated since August, and materially updated since earlier this year? Have you stopped supporting React/NextJS? When will be the next significant improvement on NextJS/React? Thanks!
Hello teave,
Thanks for getting in touch. We are working in latest Next.js app router update and it will be total re-write of the template where there won’t be single line of code similar to last one. We appreciate your patience. You should see the update by early next year my be in the first month.
Regards.
We are delighted to announce the release of our latest update for the Next.js version.
This update includes new apps such as eCommerce, Academy, Logistics, Email, Chat & Kanban and the front pages. You may access and download the updated package directly from your ThemeForest account.
We trust this update meets your requirements and appreciate your patience and continued support.
Hi mrmu8n3,
In latest verison of vuexy we use Suspense (https://vuejs.org/guide/built-ins/suspense.html) which doesn’t work well with Transition component that’s why we removed the transitions from latest vuexy version. Vue’s latest version indeed solved this but upon new finding we got another issue in Vue itself which you can find here: https://github.com/vuejs/core/issues/9661
Once issues related to Suspense & Transition is resolved we can use the page transition just like before.
We are glad that you are interested in transition feature. We do have cool new transition if this is fixed.
For further queries, Feel free to raise support ticket at our support portal: https://pixinvent.ticksy.com/
Best Regards, Vuexy Team
Im getting this error if i run ‘next export’:
The “next export” command has been removed in favor of “output: export” in next.config.js. Learn more: https://nextjs.org/docs/advanced-features/static-html-export
Hi ggopala,
Thanks for reaching out to us. For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
when running the command php artisan jetstream:install livewire—teams I have an endless loop of > Vuexy@1.3.0 build > npm run build. What to do to resolve it?
Hi hiwdyanne,
Thanks for reaching out to us. For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
I don’t have a support license. I’m trying to run the new version in typescript, on node 16 and 18, but I’m having the following error:
Uncaught SyntaxError: The requested module ’/node_modules/.vite/deps/msw.js?v=8441e9e2’ does not provide an export named ‘rest’ (at index.ts:3:10)
Hi marvintj,
Thanks for reaching out to us. It looks like you haven’t properly installed the node_modules, We recommend using pnpm as a package manager. Please try again and if possible try using Node LTS version (v20) and let us know if you are still getting the error.
Best of Luck 
You provide the UI design (figma or Adobe xd)
Hello jocarj,
Thanks for getting in touch with us. We already include Figma design file in the package. Please download the latest package from themeforest and you should find design file inside the package.
Let us know if you face any difficulties.
Regards.
Buen día, como se encuentra. Seria tan amable de indicarme como puedo actualizar la plantilla sin perder los cambios que he hecho en plantillas anteriores. Por favor explicarme el paso para actualizar mi plantilla. Gracias
Hi pedrovalegaortiz,
Thanks for reaching out to us. For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there. In case your support is expired, please mention which technology you are using so the we can help you further.
Best regards.
is there no way to bundle all the js and css into one file insteadof using multiple includes on the header for css and footer for js.
Hi mitnets,
Thanks for reaching out to us. For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
hi, i request a ticket #3520615, can you guys please check on that? thank you
Hello mailprototypeid,
Thanks for getting in touch and apologies for the delay as we were on the new year vacation. You must have received an answer. In case you have any further query. Please continue in that support thread.
Regards.
I made a purchase. May I have a receipt?
Hello,
Please refer this article: https://help.market.envato.com/hc/en-us/articles/205604563-View-Download-Invoices
It will help you find your invoice. Let us know if you have any further query.
Regards.
Hi,
Is there Attendance option?
Hello Unicomoda,
Thanks for getting in touch with us. We do not have Attendace option. Let us know if you have any other query.
Regards.
Hello, I’ve been dealing with a ridiculous problem for about a week. In fact, after not being able to find a solution for a long time, I published a post on stackoverflow.com as a last resort. You can find all the details in the link below.
https://stackoverflow.com/questions/77455832/the-url-problem-i-have-in-accessing-the-assets-folder-in-laravel-10Meanwhile, I was continuing to try some ways and perform various tests to solve the problem. And I realized that the problem that caused the problem I was experiencing was caused by the “template-customizer.js” file located in the “assets/vendor/js” directory. The problem arises from line 946 in this file. Something in this line breaks all the paths and causes the problem I mentioned on stackoverflow.com. If I add a slash before the href parameter in this line, the theme is loaded, but this time different errors occur.
Actually, I don’t want to use template customizer anyway. I just want to use the “dark/light” feature. But I have to use the template-customizer.js file for this. And the problem arising in the file prevents the entire project from working. I was able to do this in the previous version and I had completed many projects with the previous version. But unfortunately I can’t do it in this version. How can I solve this problem and is there a way I can just use the “dark/light” feature instead of the template customizer?
Hello Arafsan,
Thanks for getting in touch with us!!
If you are getting this issue due to removing template-customizer.js then we suggest you update the customization options explained in the documentation here: https://demos.pixinvent.com/vuexy-html-admin-template/documentation/laravel-init-configurations.html#customization-options
You don’t need to update includes manually for that.
Let us know how it works for you 
For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
The latest reactjs version does not contain the new apps like Academy, logistics etc. Could you add them to ReactJS version too. ??
The Demo seems to have new app pages.. but the download doesn’t have it..!
Hello mouryan,
Thanks for getting in touch with us. New pages are introduced in HTML, Vue and integrations like Laravel, .Net Core etc.. With React, our main priority will be to move this template to app directory structure. We will add those new pages in react in the 2nd phase next year. Your patience is appreciated.
Regards.
We are delighted to announce the release of our latest update for the Next.js version.
This update includes new apps such as eCommerce, Academy, Logistics, Email, Chat & Kanban and the front pages. You may access and download the updated package directly from your ThemeForest account.
We trust this update meets your requirements and appreciate your patience and continued support.
Why you removed Portuguese language support in this new update? We’re a few Portuguese here!
Hello bmgmatias,
Thanks for getting in touch. Translations are for demo purpose only, we have not removed support of any language.
For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
In the latest version I am getting too many errors in the browser console, can you please help me out in solving this.
jquery.js:9930 Access to XMLHttpRequest at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/earning-reports-charts.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. send @ jquery.js:9930 jquery.js:9930 send @ jquery.js:9930 dashboards-crm.js:596 Uncaught TypeError: Cannot read properties of undefined (reading ‘data’) at dashboards-crm.js:596:26 at dashboards-crm.js:859:3 dashboards-crm.html:2694 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 jquery.js:9930 Access to XMLHttpRequest at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/search-horizontal.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. send @ jquery.js:9930 jquery.js:9930 send @ jquery.js:9930 jquery.js:3773 jQuery.Deferred exception: Cannot read properties of undefined (reading ‘pages’) TypeError: Cannot read properties of undefined (reading ‘pages’) at HTMLInputElement.<anonymous> (file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/js/main.js:491:47) at Function.each (webpack://Vuexy/./node_modules/jquery/dist/jquery.js?:383:19) at jQuery.fn.init.each (webpack://Vuexy/./node_modules/jquery/dist/jquery.js?:205:17) at HTMLDocument.<anonymous> (file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/js/main.js:473:19) at mightThrow (webpack://Vuexy/./node_modules/jquery/dist/jquery.js?:3479:29) at process (webpack://Vuexy/./node_modules/jquery/dist/jquery.js?:3547:12) undefined jQuery.Deferred.exceptionHook @ jquery.js:3773 jquery.js:3783 Uncaught TypeError: Cannot read properties of undefined (reading ‘pages’) at HTMLInputElement.<anonymous> (main.js:491:47) at Function.each (jquery.js:383:19) at jQuery.fn.init.each (jquery.js:205:17) at HTMLDocument.<anonymous> (main.js:473:19) at mightThrow (jquery.js:3479:29) at process (jquery.js:3547:12) dashboards-crm.html:1 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 dashboards-crm.html:1 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 dashboards-crm.html:1 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 dashboards-crm.html:1 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 dashboards-crm.html:1 Access to fetch at ‘file:///C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json’ from origin ‘null’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. /C:/BeyondeBiz/DataTransfer/Sashware_New_Template/vuexy-admin-v9.9.1/html-version/Bootstrap5/vuexy-bootstrap-html-admin-template/assets/json/locales/en.json:1 menu.js:187 Uncaught TypeError: Cannot read properties of undefined (reading ‘contains’) at HTMLElement._evntElMouseOut (menu.js:187:220) _evntElMouseOut @ menu.js:187
Failed to load resource: net::ERR_FAILED
Hello FWDAU,
Thanks for getting in touch with us!!
Serve Files Locally: Instead of directly opening the HTML file in your browser from the local file system, set up a local development server to serve your files. This way, you can use a supported protocol (http://localhost) and avoid CORS issues.
We are using relative paths of assets, so you need to open the template on local servers like XAMPP, MAMP, WAMP, etc…
Let us know if you have any other queries 
Regards~
Hi PIXINVENT,
I tried publishing it in webserver and it worked fine.
Thank you so much for your help 
Hello FWDAU,
Thanks for your confirmation.
Cheers~
Hi Pixinvent,
The generated build size for the React – Next.js is 400 MB plus after upgrading to version 9, Can please help to reduce the build size.
Thanks
Hello SegWitz,
Thank you for reaching out to us. We understand your concern about the increased build size after upgrading to version 9 of React – Next.js. While installation, customization, optimization, and deployment are not included in our support, read more on support policy from here: https://themeforest.net/page/item_support_policy, We’d be happy to provide some advice on potential factors that might be contributing to the larger build size.
It’s important to note that several factors can influence build size in a React – Next.js project. Here are some areas to consider for optimization:
Dependency Management: Review the dependencies in your project. Outdated or unused packages can bloat the build size. Make sure you’re using the latest versions and consider removing any unused dependencies.
Code Splitting: Implement code splitting to load only the necessary components and modules when they are needed, rather than bundling everything into a single file. This can significantly reduce the initial bundle size.
Webpack Configuration: Check your Webpack configuration settings, as they can impact the build size. Adjusting the optimization settings and enabling tree-shaking can help remove unused code.
Image and Asset Optimization: Compress and optimize images and other assets in your project to reduce their size. Use modern image formats (e.g., WebP) and consider lazy loading images.
Server-Side Rendering (SSR): If your project uses SSR, make sure it’s configured efficiently. Unnecessary server-side rendering can increase the bundle size.
Analyzing Bundle: Utilize tools like Webpack Bundle Analyzer to identify which parts of your application contribute most to the bundle size. This will help you pinpoint areas that need optimization.
Minification and Compression: Ensure that your JavaScript and CSS files are minified and served in a compressed format to reduce their size during transmission.
Unused Code: Eliminate any unused code or components from your project to reduce the overall build size.
By reviewing and addressing these factors, you should be able to optimize your build size and reduce it to a more manageable level.
Please keep in mind that while we can provide advice, actual implementation and customization might require development expertise.
Thank you for choosing our product, and we hope this information helps you with your optimization efforts.
Why the Vue version doesn’t have File Uploader like Dropzone while the React version have it? Is it on your roadmap to update the Vue version about this?
Hi wojakmcwagies,
We try to ship as minimum as possible third party libraries for performance. If you notice we do provide dropzone feature but not as component at the movement on this page: https://demos.pixinvent.com/vuexy-vuejs-admin-template/demo-1/apps/ecommerce/product/add
We have added your request to converting this feature in component in next vue release. In meantime, Feel free to use that code and build your own component. I hope this resolves your query.
Happy coding
Hi there. if contentLayoutNav is horizontal in theme config, app will not switch to vertical layout on small screens. Go to https://demos.pixinvent.com/vuexy-vuejs-admin-template/demo-5/dashboards/analytics and hit f5 in small screen.
I try to upgrade my version. That problem took my hours because I thought the problem occurs from me…
Hi sdkakcy,
We are really sorry for the inconvenience. Switching to vertical nav in smaller screen is intentional to render the app UI properly. If we stick with horizontal nav UI even in smaller screen than top header (navbar and navigation) can occupie 20%-25% of device viewport which is really bad UX. This is the reason we intentionally switch to vertical nav in smaller device even when horizontal nav is configured.
Moreover, If you wish to not switch to vertical nav in smaller device just disable calling of `switchToVerticalNavOnLtOverlayNavBreakpoint()` in “src/layouts/default.vue” file.
I hope this resolves your query. However, Feel free to share your opinions and feature requests. We love to work on UX ♥️
Best Regards, Vuexy Team
Hi again.
I think you didn’t understand what I’m talking about. I know that app going to vertical layout in small screens. This is expected behavior but I said that in version 9 that’s not working. I have added link to reproduce. Open link on small screen device and see.
https://demos.pixinvent.com/vuexy-vuejs-admin-template/demo-5/dashboards/analyticsHi sdkakcy,
Sorry for the confusion
We got your point and we just made a fix.
Thanks for reporting this. We’ll make a patch release maybe tomorrow with this fix.
We are glad that you are really active with the template updates and helped us fix this crusial bug
Best Regards, Vuexy Team
It’s my pleasure, thank you for quick response and fix. You are the best!
By the way, you said I’m active with template. Yes, I want to keep my theme files up to date but it’s very hard because you make breaking changes usually. I was thinking of saying this in another topic but anyway;
I have a few small requests: First, we use the theme for production so if you use not stable packages like “suspense” for AppLoadingIndicator this gone a be breaking changes in the future. Even you can see this warning in chrome’s console. This is often undesirable. Second is about optimization. I want to keep my source code small for performance. But in this version; for example if I didn’t install tiptap dependencies build fails. I dont want to use tiptap editor and also dont change the @core codes. Please keep this in your mind and give us a solution. I should be able to choose which packages to use.
Finally please don’t change the package manager too
Small differences breaking the entire theme. For example yarn didn’t resolve “destr” package automatically so I must to add this dependency manually.
And those are really really last words: Sorry for grabbing your time but this theme is the best in the world and I want to contribute to it.
Thank you.
Hi sdkakcy,
Thanks for your inputs. We really appreciate taking time to review the template.
Regarding, Breaking changes we already discussed this recently and we are finalizing LTS like system for template that will keep template stable for as much as possible years from ourside. From now on, We’ll avoid introducing the breaking changes from Vue side. However, do note that this might include we might need to stick to older version of the packages if needed. This is because as we update the package we need to make some changes for compatability and it may break the single page or and application. As a aware developer you might know about the trade offs.
As we provided nuxtjs as well along with the vue, We had to align code for both frameworks and because NuxtJS was using suspense we need to introduce that in VueJS as well. To give you more insights, Evan You (creator of Vue) is working on making suspense stable in Vue 3.4 (expected soon) and that might be the reason Nuxt is officially using suspense even it’s experimental. Hence, It’s safe to use suspense in production.
Regarding optimization issue, Can you please mention if you are using full-version or starter-kit for development or provide some reproduction steps to help us reproduce the issue and we’ll solve it for sure.
”@core” is heart of our template and I guess it might have updated due to introduction of nuxtjs and alignment I mentioned earlier. However, for the future releases it’ll provide bug fixes and new features. I would love to know what changes in ”@core” broke the project so we can improve our future releases.
Changing package manager was great benefits for all of us, pnpm is way faster than npm and yarn. We made this decision because installing dependencies might take some good amount of time and development speed is crucial when you have deadline. Moreover, We also thought that developers also have option to choose yarn if they want to continue with existing package manager. We do tested the package from ourside with all three package managers and didn’t caught any issue however we’ll look into this issue as well.
Thanks for your appreciation, We’ll always try to push our boundaries to provide the best 
Feel free to share your feedback we’ll love to hear from you.
Best Regards, Vuexy Team
Hello again
It’s my pleasure. I will say one word for your answer: wonderful. You must have spent a lot of time on this. Thank you for your time. Appreciate for that. I hope it will be useful for your development process. Maybe some other user too. That’s why you have the best theme on the market.
Best Regards.
By the way I don’t remember which version I’m using but probably full version. I have changed @core, @layouts files and package versions I’m using. Added new packages except @tiptap. When I started the dev server, vite throw exception about “destr” and tiptap. Thank you.
Hi sdkakcy,
We also added some packages in our package.json so I request you to also compare the package.json file and install the packages you are getting error from. In this case, it looks like you are missing “destr” package.
After your response, we checked our source code and found that we do use tiptap package in our ”@core” dir which requires tiptap dependency. This makes it tiptap package required to run the template however if you aren’t using that component or any tiptap resource then it won’t get added in your build/production for sure. Surely, your point is right about only using the libs that’s necessary but for that we have to make template pluggable more which is more bigger task and likely introduce breaking changes. Hence, let’s install the tiptap for now as it won’t get bundled in your production app. Thanks so much for your feedback.
I really liked the attention to the detail and squeezing the performance till the last drop
You must be great developer.
I hope this resolves your query. Feel free to let us know if you have any further queries. We are happy to assist.
HI all, where is dockerfile/docker-compose locate? In the documentation it says that it is at the root of the project
Hello sunevil,
Thanks for reaching out to us. For technical inquiries, we kindly request that you create a support ticket on our support portal: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
sorry but my code has expired. I just need to know where the files that you indicate in your documentation (https://demos.pixinvent.com/vuexy-vuejs-admin-template/documentation/guide/docker.html) are. I do not have the files mentioned in the root of the project
Hi sunevil,
Thanks for raising the concern. Where intent to ship the docker file however at the movement it’s only available for VueJS (not for nuxt) version and due the docker’s limitation on windows we do not officially provide it.
Can you please let us know for which framework you want docker file, VueJS or NuxtJS?
Awaiting your response.
Oh…thank you so much. Im using vuejs version