Hi, we just approved the refund.

thank you

You are welcome, please reach us out again if you encounter any issues.

Hi, we don’t block any cookies, if you wish to forward cookies while sending a request, you could set withCredentials: true to your axios request.

Hi, thank you for your interest in our template. However, we currently have no plans to create an HTML version.

Hi, we have only React version for this template at the moment.

Hi, currently we have no figma version for this template.

Hi, we just released a hot fix for this.

hi, i notice a new release was done in Jan 15 but i dont see any changes on the changelog file, still says: v1.3.7 01 Dec 2025

Hi, this update was a ThemeForest file patch to fix a missing file. It does not impact the current template version.The next version update is scheduled for the end of this month.

Hi, we are currently working on NextJs version, estimated it will be released on next year January or February.

Hi, Next.js version is now available! You can check it here https://themeforest.net/item/ecme-nextjs-tailwind-admin-template-app-router/56475600

Hi, we are currently working on NextJs version, estimated it will be released on next year January or February.

Beautiful theme, but I would appreciate it if the theme included one or two SaaS landing pages.

Hi, we will consider including the landing page we had in the demo, as it’s not designed for template purposes for now.

Hi, we are currently working on Nextjs version, estimated will be released in January or February next year

Hi, Next.js version is now available! You can check it here https://themeforest.net/item/ecme-nextjs-tailwind-admin-template-app-router/56475600

Sure, every layout can be customise based on needed.

Hi, based on your review, you mentioned a re-render issue. Can you provide more details? Specifically, where in the component are you seeing this happen, and what kind of performance issue is it causing?

If you’re talking about two renders happening at the same time, that’s normal behaviour caused by React’s Strict Mode. You can read more about it here: https://react.dev/reference/react/StrictMode

Other than that, we are not seeing any increase in render times in our template.

If you intend to resolve the issue, we are always ready to help.

If you are really not satisfied with the template, you can request a refund on ThemeForest, and we’ll approve it.

Can I reset it somehow? I do need to keep the state

Thank you so much

The persistent state is stored in localStorage. If you need to manipulate it for development purposes, you can do so directly by opening DevTools, navigating to the Application tab, selecting Local Storage, and deleting the theme key-value pair.

If you’re building this for a client application and need a more user-friendly solution, consider adding a reset method like this in useThemeStore:

export const useThemeStore = create<ThemeState & ThemeAction>()(
    persist(
        (set) => ({
            ....
            resetState: () => set(themeConfig),
        }),
        {
            name: 'theme',
        },
    ),
)

You can call this method whenever you need to reset the theme. Let us know if you need further assistance!

Hi, you can download the latest version from your ThemeForest download page

cool, thanks, is there any changelog?

Hi, here’s the changelog, https://ecme-react.themenate.net/guide/changelog

Hi, html version was not available at the moment .

Hi, thanks for telling this issue, find out that we are missing the initial direction attribute append for the body, To solve this issue, you can import useDirection hook to src\components\template\Theme.tsx

import useDirection from '@/utils/hooks/useDirection'

and init it as following:

const Theme = (props: CommonProps) => {
    useTheme()
    useDarkMode()
    useDirection()

   ...

This could solve the issue, we will include this fix in our next update.

Please let us know if you have any further questions or if the issue still persists.

Regards

Thank you

You are welcome! feel free to reach us out via email, if you encounter any issues again.

Hi! We just sent you an email—please check.

You’re welcome!

Having documentation on the Chat AI UI and its usage would be nice.

Thanks for your feedback, we will enhance the documentation on this part.

While we are not an expert in Laravel & Inertia, we found some useful guides online that should help you integrate the template into your stack. Here’s an article https://medium.com/@demian.kostelny/set-up-laravel-app-with-inertia-js-react-js-and-vite-js-60f1f5fb8b73 that covers setting up Laravel with Vite, Inertia.js, and React. This should give you a good starting point. If you encounter any specific issues, feel free to reach out via our email, and we’ll do our best to assist.

Thanks for the link, but the environment itself is already set up.

How can I disable routing, authentication, authorization, and other features? Also, how can I integrate only the UI components into the existing framework?

Hi,

To quickly integrate only the UI components, you can copy the following directories under /src:

• @types
• assets
• components
• configs
• constants
• store
• utils

These folders include all the necessary pieces, such as layout components, basic UI elements, and utility components. You can also update App.tsx to the following:

import Theme from '@/components/template/Theme'
import Layout from '@/components/layouts'

function App() {
    return (
        <Theme>
            <Layout>
                Your page content
            </Layout>
        </Theme>
    )
}

export default App

And modify Layout.tsx like this:

import type { CommonProps } from '@/@types/common'
import { useThemeStore } from '@/store/themeStore'
import PostLoginLayout from './PostLoginLayout'

const Layout = ({ children }: CommonProps) => {
    const layoutType = useThemeStore((state) => state.layout.type)

    return (
        <PostLoginLayout layoutType={layoutType}>
            {children}
        </PostLoginLayout>
    )
}

export default Layout

Please note that some components may import hooks from react-router-dom and @auth, which you might need to remove manually.

Feel free to reach out via email if you run into any issues during the migration. We’ll be happy to assist!

Hi, we have no plan to create HTML version for now.

Thank you!