Discussion on Vuexy - Vuejs, Nuxt, Next.js, HTML, Laravel, Asp.Net & Django Admin Dashboard Template

Discussion on Vuexy - Vuejs, Nuxt, Next.js, HTML, Laravel, Asp.Net & Django Admin Dashboard Template

Cart 29,646 sales
Recently Updated
Well Documented

PIXINVENT supports this item

Supported

This author's response time can be up to 1 business day.

1730 comments found.

​Hello Vuexy Team,

I would like to report a security vulnerability affecting the current Vuexy v10.11.0 21/11/2025 template.

The template uses React 19.2.0, which is impacted by the React2Shell vulnerability (CVE-2025-55182) related to React Server Components deserialization.

Could you please let us know if there is a planned update to address this issue, and the expected timeline?

Thank you for your support.

Best regards,

Donhko84 Purchased

I’m having trouble installing the full version of nextjs with npm -> ts version: vuexy-admin-v10.11.0\nextjs-version\typescript-version\full-version.

Error: npm install npm warn Unknown project config “auto-install-peers”. This will stop working in the next major version of npm. npm warn Unknown project config “shamefully-hoist”. This will stop working in the next major version of npm. npm warn Unknown project config “node-linker”. This will stop working in the next major version of npm. npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: vuexy-mui-nextjs-admin-template@5.0.0 npm error Found: @tiptap/core@3.11.0 npm error node_modules/@tiptap/core npm error tiptap/core“3.11.0” from the root project npm error npm error Could not resolve dependency: npm error peer tiptap/core3.13.0” from @tiptap/extensions@3.13.0 npm error node_modules/@tiptap/extensions npm error peer tiptap/extensions3.11.0” from @tiptap/extension-placeholder@3.11.0 npm error node_modules/@tiptap/extension-placeholder npm error tiptap/extension-placeholder“3.11.0” from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with—force or—legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see:

neel_brahma

neel_brahma Author Team

Dear Donhko84,

We would like to recommend using the pnpm package manager as an alternative to npm.

pnpm offers several advantages, including efficient disk space usage by storing packages globally, faster installation speeds, and enhanced security through strict dependency isolation. Unlike npm’s flat structure, which allows any package to access others in the `node_modules` directory, pnpm ensures that each package has access only to its declared dependencies.

To facilitate a smooth installation process, we have provided the `pnpm-lock.yaml` file, which contains the updated lock file, ensuring that no errors or warnings will occur during installation.

However, if you prefer to continue using the npm package manager, please ensure that you run the following command to avoid any compatibility issues: `pnpm install—legacy-peer-deps`.

If you have any further questions, we kindly request that you submit a support ticket through our support portal: https://pixinvent.ticksy.com/

Regards.

I purchased this Vuexy Vuejs + HTML + Laravel Admin Dashboard template expecting a fully functional product according to the documentation. Sadly — the template has serious performance issues, and many documented features simply don’t work.

I submitted a support ticket with details, but the maintainers never fixed the problems. When I asked for a refund, they simply told me to open a ticket and then closed my refund request without resolution.

For more details and reproducible evidence, see: https://drive.google.com/file/d/1G1_WlfxiUa8Mz5Oh9TwTbS96CH_BbnTA/view?usp=sharing

As a paying customer, I expected a working product — not something I have to debug on my own. I hope the authors will either fix the issues or provide a fair refund. I share this to warn potential buyers: this template may not work as advertised currently.

Hello Ranjithjose3,

We are using the node v22 and the project is running without any issues. We have also deployed the project as demo, you can check it here: https://demos.pixinvent.com/vuexy-vuejs-laravel-admin-template/demo-1/dashboards/crm This also refers that our template is completely working in production as well. Please provide the list of issues you are facing and what is not working as documented, so that we can help you to resolve your issue.

we are always here to help.

Hello Ranjithjose3,

Thanks for sharing the video recording. I have tried to reproduce the issue but we are unable to reproduce the error on our system. For the reference I have also attached the screenshots, please check them out:

https://drive.google.com/file/d/1ywr60jh1PDcvPUCei-8-q1xLGARo8Afi/view?usp=drive_link https://drive.google.com/file/d/1ydJPxaqtYx1JtEYu4sHYnHeKs9dqCvlF/view?usp=drive_link

From the error log, it seems like the issue is from the extension you have installed. Can you try in the guest most or any other browser like chrome (in guest mode). Please let me know, if you still face the issue in the guest mode.

Awaiting your reply.

Hello,

It seems like the template does not have File section where we can upload file and display, something similiar to Media Library in Wordpress

neel_brahma

neel_brahma Author Team

Hi minyu9,

Could you please specify which version you are talking about (HTML, HTML + Laravel, ASP.NET Core, Django, Next.js, VueJS, VueJS + Laravel, or NuxtJS)?

Regards.

.

neel_brahma

neel_brahma Author Team

Hi oluwasusiv,

Thank you for contacting us.

How can we help you? If you have any questions or inquiries, please let us know and we will be glad to address them promptly.

Regards.

Hi, I’ve checked the demo and noticed that there’s an option to + Add Customer and + Add Product, but I don’t see any option to add a new order. Could you please let me know if this feature is included or how it can be enabled?

Hi jamotime,

Thanks for getting in touch with us.

Could you please specify which version you are talking about (HTML, HTML + Laravel, ASP.NET Core, Django, Next.js, VueJS, VueJS + Laravel, or NuxtJS)?

Regards.

Hi, thank you for reply. It was on HTML. But today everything is working.

Hello jamotime,

Thank you for your response!

We’re glad to hear that everything is working correctly. If you have any questions or need assistance in the future, please don’t hesitate to reach out by submitting a support ticket. We’re always here to help!

The select all checkboxes in the datatables extentions do not work as expected.
If you select all when the view is not for all rows, all of them are selected anyway.
This may cause unwanted data to be deleted or edited.
This is what it shows when the fisrt 10 are selected with the top chechbox:
Showing 1 to 25 of 100 entries100 rows selected

smit_bs

smit_bs Author Team

Hello guyzamir,

Thank you for reaching out to us!

We’re currently using a third-party library for DataTables. For the select feature, we’re utilizing its basic version to ensure it remains accessible and easy to use for all users. If you’d like to customize it further to suit your specific needs, you can refer to the official DataTables documentation for guidance. Although we don’t use these advanced features ourselves, the following discussion may help: Show Only Selected Rows – DataTables Forum: https://datatables.net/forums/discussion/75406/show-only-selected-rows

Please let us know if you have any other questions or need further assistance. We’re happy to help!

Well, I realize it is a third party library but it has a bug in it and I would suggest removing it or providing an alternative solution for it (I already created my own solution with JS) without using it on a regulart datatable.

smit_bs

smit_bs Author Team

Hello guyzamir,

Thank you for your valuable feedback. We completely understand the issue you’ve raised, and we appreciate the suggestion you’ve provided.

Regarding your concern, we recognize that the behavior of the “select all” feature can be confusing, especially when only a subset of rows is visible. As you’ve pointed out, selecting the checkbox currently applies to all rows in the dataset, not just the ones visible on screen. We will be addressing this behavior based on your input, and will consider making updates once we gather additional feedback from other users.

Your insight is important to us, and we will continue refining this feature to improve the user experience. If you have any further suggestions or encounter any other issues, please don’t hesitate to share them with us.

We’re happy to consider them as we work to enhance our service. Thank you again for helping us improve.

I need only Laravel demo not Laravel + Node. please provide it.

smit_bs

smit_bs Author Team

Hi web_revolution,

Thank you for reaching out to us!

We offer two versions of our Laravel templates: Laravel + HTML Laravel + Vue Unfortunately, we do not provide a Laravel + Node version at this time. If you have any questions or need clarification on either of these two versions, please feel free to ask! Here are links for each version: Laravel + HTML demo: https://pixinvent.com/vuexy-bootstrap-laravel-admin-template/ Laravel + Vue demo: https://pixinvent.com/vuexy-vuejs-laravel-admin-template/

If you have any other questions, don’t hesitate to let me know!

A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.

To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.

The label’s for attribute doesn’t match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.

To fix this issue, make sure the label’s for attribute references the correct id of a form field.

every page show the errors above! could you repair it

smit_bs

smit_bs Author Team

Hello bill991223,

Thank you for reaching out to us!

We’ve included both the id and for attributes in elements that use labels to ensure proper accessibility and functionality. If you’re noticing any issues on specific pages, please share them so we can review them and assist you more accurately. Regarding the name attributes, the current form fields are designed primarily for demo purposes. This approach allows users to customize them easily for various use cases. If you prefer having name attributes on all input fields, you can manually add them as needed. We intentionally kept them minimal to keep the demo simple and adaptable.

Please let us know if you have any further questions — we’re happy to help!

1. Navigate to https://demos.pixinvent.com/vuexy-html-admin-template/html/vertical-menu-template/ 2. Press F12 to open Developer Tools 3. Check the Console tab 4. Look at the Issues panel on the right side 5. That will displays the following issue:The label’s for attribute doesn’t match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.

To fix this issue, make sure the label’s for attribute references the correct id of a form field.

smit_bs

smit_bs Author Team

Hello bill991223,

The issue you mentioned originates from the Customizer. In the Customizer, we use labels with for attributes so users can easily associate and add inputs. This setup shouldn’t cause any problems. However, if you prefer to remove them, you can certainly do so at your convenience. To remove the labels, you can modify the following file: File path: `js/_template-customizer/_template-customizer.html`

Please let me know if you have any further questions or need assistance with the changes!

Hi,

I am using the Nextjs version. Here I found that after clicking the menu(Horizontal or Vertical) we have to wait for a long period before moving to the page. It seems it is stuck or not clicked at all.

I don’t want the waiting time after click the menu. How can I reduce to waiting time after clicking the menu(Horizontal or Vertical)? It should move to the targeted page right after the menu is clicked.

Hi ashrafulratul,

Thanks for getting in touch with us.

For technical queries, please create a support ticket on our support portal: https://pixinvent.ticksy.com.

Thanks for your response, I have created a ticket. https://pixinvent.ticksy.com/ticket/4501058

Hi ashrafulratul,

We have received your ticket and our technical team will respond shortly.

Regards.

Hau_n

Hau_n Purchased

Hi team, I’d like to know if there are any plans for a version using Nuxt-UI alongside Vuetify?

Hello Hau_n,

Thanks for the suggestion.

Currently, we have not planned anything related to providing Nuxt-UI version in our templates.

Thanks a lot.

Presale question: Can I use the landing page as my homepage, here example.com/ ? in nextjs, how does it work, is there any change to make to the files?

Hi lordmazus,

Thanks for getting in touch with us.

Yes, you can use the landing page as your homepage. To do so, you will need to transfer the landing page code, along with its layout, to the main homepage and layout files.

Please do not hesitate to contact us if you have any further questions.

Octeria Purchased

Hi, after installing the latest versions of the libraries on a new computer, i can’t pnpm install the Vue + Laravel version. I’m getting the error :

> vuexy-vuejs-laravel-admin-template@9.4.0 postinstall /Volumes/AppsDev/TestApp > npm run build:icons && npm run msw:init

> vuexy-vuejs-laravel-admin-template@9.4.0 build:icons > tsx resources/ts/plugins/iconify/build-icons.ts

/Volumes/AppsDev/TestApp/resources/ts/plugins/iconify/build-icons.ts:89 require.resolve(’@iconify-json/tabler/icons.json’), ^

ReferenceError: require is not defined in ES module scope, you can use import instead at <anonymous> (/Volumes/AppsDev/TestApp/resources/ts/plugins/iconify/build-icons.ts:89:5) at ModuleJob.run (node:internal/modules/esm/module_job:345:25) at async onImport.tracePromise.proto (node:internal/modules/esm/loader:651:26) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5)

Node.js v22.19.0 ELIFECYCLE Command failed with exit code 1.

​My environment :

MacOS Sequoia (15.6) Node v22.19.0 LTS NPM v10.9.3​ PNPM v10.16.1​​

Hello Octeria,

Thanks for reaching out to us.

This issue is due to the require. You just need to add the below two lines in build-icons.ts file

``` import { createRequire } from ‘node:module’ // <—add this const require = createRequire(import.meta.url) ```

Adding this should fix your issue. If you still face the issue, please feel free to create a support ticket at https://pixinvent.ticksy.com/. Our technical team will help you to fix the issue.

Thanks again.

smit_bs

smit_bs Author Team

Hello Blackholes,

Thank you for reaching out to us!

Cards (and other components) are not limited to a single page. You can use them on front pages or any other pages within the theme. To do so, you’ll just need to include the component code along with the required styles and JavaScript. Once added, the card will display and function wherever you place it.

If you have any other questions or need further clarification, please don’t hesitate to let me know—I’ll be happy to help!

I am going to buy it soon. I really like this theme. I think I’ll use the elements in the admin page on Frontpage. I hope I don’t encounter any problems.

smit_bs

smit_bs Author Team

Hello Blackholes,

Thank you for your kind words and for choosing our theme! We’re glad to hear that you like it. Rest assured, there should be no issues with using elements from the admin page on the front page. If you need any further assistance or have any questions, feel free to reach out.

Hi, I’m only concerned about the React.js version — is it stable, and can I customize it according to my project requirements? Honestly, I just want some reassurance from you before making the purchase.

Hi mohamdabdulatif,

Thanks for getting in touch with us.

Please be informed that you will receive the Next.js version, rather than the pure React version. Next.js is a React framework, and you may refer to its documentation at https://nextjs.org for further information.

Our template is fully customizable to suit your design needs. For guidance, you can refer to our documentation at https://demos.pixinvent.com/vuexy-nextjs-admin-template/documentation. This includes instructions on customizing the layout, theme, components, and more.

Please let us know if you have any further queries.

PRE-SALE Question, I’m very interested in the template for Nuxt, also I want to know if it’s possible to get the Figma prototype. I completely understand if it has an additional price, we need the prototype to build the views for the client first and then go to development. Thanks

Hello Azuaje45,

Thank you for your interest in our Nuxt template! Figma files are already included in the purchase. You will recieve both the figma file and nuxt template on the purchase. If you have any other issue, please feel free to get in touch with us.

If i use stater kit Next.js version. So can i use all the components or pages in starter kit that are available in the full version?

Hi kh4035209,

Thanks for getting in touch with us.

Yes, you may use any component or page from the full version within the starter kit.

Please let us know if you have any further queries.

Regards.

I am trying to install Vuejs Laravel version on my server with folder admin. I uploaded all files of vue-laravel-version/typescript-version/full-version mysite.com/project/admin but its not working due to path issue. Anybody can help me with path settings. I have already done many changes in vite.config.ts but every time build created and issue is coming.

Hello Bhavikkoradiya,

Thanks for purchasing our theme.

We have already created a deployment guide for deployment. Please refer to it here: https://demos.pixinvent.com/vuexy-vuejs-admin-template/documentation/guide/laravel-integration/laravel-deployment.html#laravel-deployment

You can also refer to official deployment guide of laravel. If you have any other issue, please feel free to get in touch with us.

Regards.

I would like to ask if it’s possible to switch my purchase to the Materialize Admin Template instead. I don’t need a refund, I just want to switch to the other template.

Just to confirm, I am required to purchase the new Materialize product first, and only then request a refund for the Vuexy product I already bought, correct?

Hi quocdat254,

Yes, that’s correct. You would need to purchase the Materialize product first, and once that’s done, you can then proceed to request a refund for the Vuexy product.

Regards.

Thank you for your support

daurand

daurand Purchased

I can’t find this file MaterialIconProvider.jsx

Hi daurand,

Thanks for getting in touch with us.

Could you please specify which version (HTML, HTML + Laravel, ASP.NET Core, Django, Next.js, VueJS, VueJS + Laravel or NuxtJS) you are using?

Regards.

daurand

daurand Purchased

Next.js

Hi daurand,

Thanks for specifying the version you are using.

We do not provide a file named ‘MaterialIconProvider.’ Instead, we utilize ‘iconify-icons’ through the use of classes, with the icons being generated via CSS. You can refer to the icons docs from here: https://demos.pixinvent.com/vuexy-nextjs-admin-template/documentation/docs/guide/layout/icons.

Please let me know if you have any further queries.

Regards.

by
by
by
by
by
by

Tell us what you think!

We'd like to ask you a few questions to help improve ThemeForest.

Sure, take me to the survey