@Left4code reply

Hey! Sorry for the late reply. Yes, if you purchase the Regular License for $29, you can use it forever (lifetime use) and you’ll also get access to all future updates at no extra cost.

Let me know if you have any other questions!

Hey! Sorry for the late reply. Yes, if you purchase the Regular License for $29, you can use it forever (lifetime use) and you’ll also get access to all future updates at no extra cost.

Let me know if you have any other questions!

thanks

You’re very welcome..

Hi! Sorry for the late reply, and thank you so much for reaching out – we really appreciate your kind words about the template!

Yes, you can use the Extended License for that purpose. It allows you to include the template in a product like your ERP system that will be sold to multiple clients.

Let us know if you have any other questions or need clarification -happy to help!

Hi, Sorry for the late reply. Unfortunately, we do not support RTL versions at the moment.

Hi,

Thank you for your question! At the moment, we do not have any plans to add React Router v7 to the React version of our template.

If you have any other questions or need further assistance, please don’t hesitate to reach out to us.

Best regards

Hi there,

Thank you for reaching out! We’ve just released a compiled version of the template within the package, so you can redownload the project and you’ll find it included.

Regarding the JavaScript version, we currently only offer TypeScript, so unfortunately, we don’t have a JavaScript version available to send. If you need any further assistance with TypeScript, though, feel free to let us know—we’d be happy to help!

Best regards

There is all the jQuery files on js folder, on which integrating the HTML Version with React gives the problem.How to resolve it ?

Thank you for your question!

We understand your confusion, but we also find the question somewhat puzzling. For your information, React and jQuery have fundamentally different approaches to DOM management. React uses a reactivity system and virtual DOM to efficiently handle changes, while jQuery performs direct DOM manipulation.

We’d like to clarify that the HTML version of our template does not actually use jQuery. Instead, it includes lightweight helper functions that may look similar to jQuery but are not the same. These helpers are designed to keep the template simple and functional without relying on the full jQuery library.

Combining these helpers with React could still lead to conflicts, especially when modifying DOM elements outside of React’s control. Therefore, we generally do not recommend mixing these approaches.

Hi there,

Sorry for the late reply. We have just released an update to accommodate this feature.

Please update the “src/themes” directory, as we have added a React context that allows you to force the active menu from a child page.

You can now set the active menu from your pages with the following code:

import { forceActiveMenuContext } from "@/themes/Rubick/SideMenu/side-menu";
import { useEffect, useContext } from "react";

function Main() {
  const menuContext = useContext(forceActiveMenuContext);

  useEffect(() => {
    menuContext.forceActiveMenu("/dashboard-overview-2");
  }, []);
}


	
Let us know if you need any further assistance!


	
Best regards

Hi Team,

In what way can I modify this code to work with Next.js? Since ‘react-router-dom’ is not used by Next.js like it is by React.

Thank you.

Hi,

Unfortunately, we haven’t tried using Next.js yet, so we can’t provide specific suggestions at this time. Let us know if there’s anything else we can help with. Thank you!

Hi there,

Sorry for the late reply. You can ignore this warning as it will not affect the production build and only appears in development mode. Let me know if you have any other concerns!

Hi there,

Thank you for using our template and for bringing this issue to our attention. We are aware of the problem with the library.

For the time being, we recommend using the TypeScript version “~5.3.3” to avoid this issue while we search for an alternative plugin reference.

We appreciate your understanding and patience as we work on a solution. If you have any further questions or need assistance, feel free to reach out.

Best regards

Hello,

Thank you for your purchase and for your kind words about the Midone Tailwind CSS React Admin Dashboard template! We’re glad to hear that you’re eager to use it in your project.

To quickly customize the template for your needs, you can start by editing the stores/themeSlice.ts file. In the selectTheme function, please modify it as follows:

export const selectTheme = (state: RootState) => {
  if (localStorage.getItem("theme") === null) {
    localStorage.setItem("theme", "enigma");
  }

  if (localStorage.getItem("layout") === null) {
    localStorage.setItem("layout", "side-menu");
  }

  return state.theme.value;
};

Next, you can adjust the themes variable by leaving only the “Enigma” theme and the “Side Menu” layout, like this:

export const themes = [
  {
    name: "enigma",
    layout: "side-menu",
    component: EnigmaSideMenu,
  }
] as const;

This should help streamline the code and remove the unused themes and the theme switcher, making your project more focused.

If you need further assistance, feel free to reach out. We’re here to help!

Best regards

Thank you for the reply, though it’s not what I really wanted. After a few days of investigation, I have managed to achieve my goal. Thanks anyway.

Thank you for your follow-up! If you have any more questions or need further assistance in the future, don’t hesitate to reach out.

Thank you for your inquiry.

At this time, we only offer the template in TypeScript. We do not currently have a JSX version with React Vite available. If you have any other needs or require further assistance, please don’t hesitate to reach out to us.

Thank you!

Best regards

I upgraded the headlessui version to @headlessui/react@2.1.2, and it worked successfully, and the dropdown UI meets my expectations

alternatively I use Popover in version @headlessui/react@2.1.2

Hey there,

Thanks for the update! We’re glad to hear that upgrading to @headlessui/react@2.1.2 worked for you and that the dropdown UI meets your expectations.

For future versions of Midone, we are considering transitioning to ShadcnUI due to the slower updates with HeadlessUI recently.

If you need any further assistance, feel free to reach out!

Best

Hi there,

Thanks for reaching out!

We’ve noticed this issue with some of the components and have released a fix for it. To remove the warning, you’ll need to update some of the components in the ”/src/components” directory.

If you need any help with this, just let us know, and we’ll be happy to guide you through it!

Best regards

Everything working fine, thanks man

That’s awesome to hear! I’m really glad everything’s working fine for you..

Best regards

Good morning,

Unfortunately, we currently do not offer a version with only the bare essentials as you described. However, if you have any specific requirements or preferences, please let us know, and we’ll do our best to assist you further.

Best regards

never mind.. resolved it

Hey there,

I’m glad to hear that you were able to resolve the issue on your own! If you ever have any more questions or run into any other issues, please don’t hesitate to reach out. We’re here to help and make sure your experience with our project is as smooth as possible.

If there’s anything else I can assist you with, feel free to let me know. Have a great day!

Best regards

Hey there,

Thanks for reaching out, and I’m glad to hear you’re liking the Midone template! While we currently don’t have a JavaScript-specific version of the template available, I might have a solution that could work for you.

You see, even though the Midone template is built with TypeScript, there’s a configuration option called `allowJs` that you can use to include JavaScript files alongside TypeScript files in your project. This means you can still code in JavaScript within a TypeScript project.

To apply this configuration, you’ll need to modify your `tsconfig.json` file. Here’s how you can do it:

1. Open your tsconfig.json file. You should find this file in the root directory of your TypeScript project.

2. Add or modify the allowJs option. If it’s not already there, add a “allowJs”: true property in your tsconfig.json file. If it’s already present, just ensure it’s set to true.

3. Save the `tsconfig.json` file.

Here’s an example snippet of how your tsconfig.json file might look after adding the allowJs option:

{
  "compilerOptions": {
    "target": "ESNext",
    "useDefineForClassFields": true,
    "lib": ["DOM", "DOM.Iterable", "ESNext"],
    "allowJs": true,
    // Other compiler options...
  }
}

After making these changes, you should be able to seamlessly work with JavaScript files alongside TypeScript files in your project.

If you need further assistance or have any other questions, feel free to let us know. We’re here to help you out!

Best regards

Hi,

Certainly! You’ll need to make manual adjustments for integration with Next.js. Currently, we provide a TypeScript version. If you have any specific questions or need guidance on adapting it to Next.js, feel free to reach out. We’re here to assist you!

Best regards.