1736 comments found.
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
I’m using react NextJS version. it seems that it doesn’t let me login. not even in the full version with the mock username and password. any suggestions? Thanks in advance
Hello leof240,
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 want to ask a question before buying. I read your documentation regarding the React version and it seems it’s using Next.js as well? But is there any React version that is purely React without any Next.js? Because I want to integrate it with back-end language and make a monolith app.
Hello wojakmcwagies,
Thanks for getting in touch. We don’t have pure react version. We only have Next.js version as of now.
Let us know if you have any further questions.
Regards.
I’m using Html+Laravel version. when the site i reloaded the site automatically gets dark mod and white mod. How I disable this? I want a default light mod. Site link: https://genpdf.api-bash.com/
another help:-
and How I can make the active menu in my admin panel like the demo.
I want it like this. see the screenshot. https://prnt.sc/_7Z5enOG8KJBHello Themeducket,
You can check Laravel configuration documentation to set the default light/dark template here: https://demos.pixinvent.com/vuexy-html-admin-template/documentation/laravel-init-configurations.html
Please check Laravel Menu documentation here: https://demos.pixinvent.com/vuexy-html-admin-template/documentation/laravel-menu.html
In case you have any further technical queries, Please create a support ticket on our support portal: https://pixinvent.ticksy.com/. Our technical team will be delighted to assist you there.
Best Regards.
Hey, I’m using the React Typescript version. a suggestion: Please consider changing types to interfaces for example in this path “src/context/types.ts” or any other path’ that you may define types so they can be extendable by developers.
export interface LoginParams {
email: string
password: string
rememberMe?: boolean
}
export interface UserDataType {
id: number
role: string
email: string
fullName: string
username: string
password: string
avatar?: string | null
}
export interface AuthValuesType {
loading: boolean
logout: () => void
user: UserDataType | null
setLoading: (value: boolean) => void
setUser: (value: UserDataType | null) => void
login: (params: LoginParams, errorCallback?: ErrCallbackType) => void
}
If you do so, developers will be able to declare a custom module and extend these interfaces without touching the main ones. like so:
declare module 'src/context/types' {
interface LoginParams {
implicitSignIn?: boolean | undefined
}
}
Certainly, I understand your concern. TypeScript provides developers with the flexibility to extend both interfaces and types. You can choose between using interfaces and types based on your specific needs.
Extending Interfaces:
As you’ve mentioned, using interfaces is a great choice when you want to create an open, extendable contract for your types. By defining your types as interfaces, developers can easily extend them in custom modules without modifying the main definitions, just as you demonstrated with the declare module approach. This is particularly useful when you want to allow multiple extensions of the same interface.
Extending Types:
TypeScript also allows you to extend types using intersections, which is useful when you need to combine or augment existing types with additional properties. For example, you can extend a type like this: typescript
type ExtendedLoginParams = LoginParams & {
implicitSignIn?: boolean | undefined;
};
The above code creates a new type ExtendedLoginParams that includes all properties from LoginParams along with the implicitSignIn property. While it’s less common to extend types in this way, it can be useful in certain situations.
In conclusion, both approaches are valid, and the choice between using interfaces and type extensions depends on your specific requirements and coding style. If you prefer a more extensible and open approach, using interfaces as you suggested is a good choice. If you need to combine or augment types, extending them with intersection types is a suitable alternative.
In case you have any further technical query, Please create a support ticket on our support portal: https://pixinvent.ticksy.com/. Our technical team will be delighted to assist you there.
Regards.
HI, I think you have a bug in new release for html + laravel version. When select a language, the display doesn’t change to the selected language.
Hello Felixwei,
Thanks for getting in touch with us!!
We have checked about your concern on our live demo: https://demos.pixinvent.com/vuexy-html-laravel-admin-template/demo-1/ And, it’s working fine with us, can you please share the exact steps that you are following with our Live demo to reproduce the issue?
We kindly request that you create a support ticket on our support portal for any technical inquiries: https://pixinvent.ticksy.com/
Our technical team will be delighted to assist you there.
Best regards.
I’m using the HTML+Laravel version. I’m using Jetstream for authentication. I want to create a new user from my admin panel. How can I do it?
I’m logged in as admin so I want to create more users from the admin panel. after creating a new user successfully will be redirected to a specific route.
How can I do it?
when I edit any user information I also will update the password. how can I do it?
Hi Themeducket,
Thanks for getting in touch with us!!
We have provided Jetstream documentation here: https://demos.pixinvent.com/vuexy-html-admin-template/documentation/laravel-auth-jetstream.html
We have created an example using Jetstream & Livewire, so user can customize the template as per their requirements.
You can find Laravel’s official documentation on Jetstream Authentication here: https://jetstream.laravel.com/features/authentication.html
Customization & integrations are not part of the support. You can read all about the support policy here: https://themeforest.net/page/item_support_policy 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 tried the React version demo and there is one thing I didn’t understand. What’s the difference between Controlled Wysiwyg Editor and Uncontrolled Wysiwyg Editor? Because it visually looks the same.
Hello macellinosetyajis,
There is no difference in visually appearance between the Controlled and Uncontrolled Wysiwyg Editor. The Uncontrolled Wysiwyg Editor functions in a standard manner, while in the Controlled Editor, it utilizes the React useState hook for state management, enabling users to exercise control over the editor’s value.
Regards.
as said in our previous message, please create a support ticket, our technical team will be delighted to assist you there.
Best regards.
Hello dokula,
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.
Can you guys please update the React version to include a React TinyMCE and SweetAlert2?
Hello macellinosetyajis,
We regret to inform you that React TinyMCE and SweetAlert2 are not included in our React version template. However, we do offer React Draft Wysiwyg: https://jpuri.github.io/react-draft-wysiwyg/#/ for the editor functionality and MUI Dialog: https://mui.com/material-ui/react-dialog/ or react-hot-toast: https://github.com/timolins/react-hot-toast for displaying alerts, both of which are widely used in the React version in our present template.
For our forthcoming major release, we will be implementing react-toastify: https://github.com/fkhadra/react-toastify#readme for alert notifications.
Django “Vuexy Admin Template additionally provides 10 different applications which enable you to get started and build your applications faster.”
This is misleading. These are “empty” applications.
Hello telfo,
Thank you for reaching out to us. We understand your concern. As template authors, our primary focus is on providing a user interface (UI). The applications included in the Django are indeed empty applications, and we utilize mock or sample data to demonstrate how these applications could function in real-world scenarios. These applications are intended to serve as a starting point for your own development, allowing you to build your applications more efficiently based on the provided structure.
If you have any specific questions or require assistance with using our template, please feel free to ask on our support portal: https://pixinvent.ticksy.com/, Our technical team will be delighted to assist you there.
Best regards.
Hi,
Any update when NextJS v13 with new app directory will be available?
Hello sidewayset,
Thanks for getting in touch. It will be available early next year.
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 is it that in the vue+laravel version the code on the frontend to make the api calls to authenticate isn’t included and we have to look it up in the documentation, doesn’t make any sense. Could you please include that already. Logic is that if you’re using vue+laravel of course you’ll be making frontend api calls to laravel for authentication.. Thanks
Hi Freevizion,
Thanks for getting in touch with us. Source code of API calls’ response is present in @fake-db or /plugins/fake-api directory that mocks the API calls.
We haven’t written API in laravel because not everyone makes API call to laravel when using laravel + vue and there’s lots of integration when using Vue + Laravel together. Hence, mocking API calls is best bet to consider every aspect of Vue + Laravel development. If you want to make an API using laravel you are free to do so with our template. Even in future if you want to go with Firebase or some other third party integration you can do that as well. I hope you now understand the reason we didn’t provided the API in laravel. We have also written note regarding this on our item page’s “notes” section.
In addition to this, do check out our documentation for famous integrations like passport if that’s applicable to you. We’ll always try to provide best in class.
Please let us know if you have any further query. We are happy to assist.
First of all, this template is amazing! It looks very clean and appears to have all necessary features, I’ve been looking for a dashboard template and this is by far one of the best.
On to my question… I have a Laravel-Inertia-React project, I’m very experienced with Laravel but fairly new to React, so I’m wondering… seeing as you have different versions that include one or the other, would it be possible to use the react version and integrate it into my current project? Or even starting from scratch, would it be possible to integrate the react version with Laravel+Inertia?
Any plans for a Laravel-React version? I know Vue is the go-to for Laravel but just a thought. Thanks!
Hello hxmoyu,
Thank you for reaching out and for your kind words about our template. Your feedback and question are greatly appreciated. I will relay your suggestion and requirements to our core development team. Currently, we don’t have immediate plans to create a Laravel-React version, nor do we have Inertia integration in place at the moment. However, we may consider these options in the future.
If you have any further questions or need assistance, please don’t hesitate to ask.
Warm regards.
Hi,
I m a big fan of this template, i bought a license two years ago.
I m interested in the Angular version, and as we all know its no more available.
I m here to ask if its possible to buy the last version you published which has Angular version included?
I don t mind if you guys don t support it anymore. i just want the license and the code base.
Thank you.
Hello wajih123,
Thanks for showing your interest in our theme and getting in touch with us.
Unfortunately, there has been a decline in community interest in the Angular framework using Bootstrap, as well as a lack of updates for its third-party libraries for new Angular features. Additionally, there has been a decrease in sales and customer interest in the Angular framework year over year.
Due to these reasons, it has become increasingly difficult for us to maintain the Angular version of our template.
However, we have tested live version (https://demos.pixinvent.com/vuexy-angular-admin-template/demo-1/) which we can provide you once you purchase the item.
Cheers~
is figma file included ?
Hello rhsshawon,
Thanks for getting in touch with us. Yes, figma file in included in the package.
Regards.
any information on when you guys will release the nuxt one?
Hello mailprototypeid,
Thanks for getting in touch. Nuxt version will be released in this month.
Regards.
any specific date? thank you
No, we haven’t decided any date.
Hi mailprototypeid,
Nuxt version is released now
Hi,
Nuxt version is released now
You can download it from download page of ThemeForest.
Happy coding
thankyou!
any suggestions where to deploy that you guys recommend?
Hello mailprototypeid,
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.
In Html + Laravel version.
when I change the content mode “Wide” from “Compact” and reload the site. the page looks bad.
and show error on console. check the image preview.
https://prnt.sc/gVfgn4sR2DlMthis happen sometime not all time.
This is a very bad user experience. if occur a error sometime it’s very dangerous.
I’ve lost lot of time to fix but can’t. Please fix it now and give code here.
I’m really unhappy.
Hello Themeducket,
Thanks for getting in touch with us and apologies for the inconvenience caused.
Actually, we are not getting this issue in our live demo: https://demos.pixinvent.com/vuexy-html-laravel-admin-template/demo-1/
Please share the steps to reproduce this issue, if you find the same issues in our live demo.
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.
Regards~
