Hi There,

Thank you for reaching out to us. We’re sorry for the delayed response.

Unfortunately, we only have Rubick (Adobe XD) design files available at the moment, and not all pages are included. You can check out this link for more information:

Let us know if you have any further questions or concerns.

Hello!

Thank you for reaching out to us. We appreciate your support in choosing our template. I’m sorry to hear that you accidentally made a double purchase. Not to worry, we’ll be happy to help you with a refund. To get started, please click on the link below, and follow the instructions to request a refund.

If you have any further questions or concerns, please don’t hesitate to let us know. Have a great day!

Dear mabusaid,

We hope this reply finds you well! First of all, we want to apologize for the delay in our response. Thank you for reaching out to us and providing feedback on the template. We’re thrilled to hear that you’re enjoying it!

Now, let’s address your questions:

Migrating from Vite to Next.js: While we don’t have a specific guide for migrating from Vite to Next.js at the moment, we can certainly help you with the process. Generally, migrating involves setting up a new Next.js project and manually transferring your code and dependencies from the Vite project. You’ll need to update the build configuration, import statements, and any Vite-specific features you may be using. The Next.js documentation and community resources are great references for guidance on the migration process. If you need any assistance or have specific concerns during the migration, please let us know, and we’ll be glad to help you.

Making components modular: We’d love to assist you in making your components more modular. Could you please provide more details or examples of the specific external styles you mentioned? This will allow us to understand the issue better and provide you with tailored guidance. Our goal is to help you achieve modular and self-contained components that enhance the maintainability and reusability of your code.

@left4code/tw-starter dependency: The ”@left4code/tw-starter” dependency includes CSS/JS utilities that were utilized in previous versions of Midone. However, in the current version, we no longer rely on this package. For users transitioning from older versions, we have kept this package as a dependency to ensure a smooth transition and provide compatibility with their existing codebase. Rest assured, we have plans to remove this package from future versions as we continue to refine and improve Midone.

Once again, we sincerely apologize for the delay in our response. We value your feedback and are committed to providing you with the best support possible. If you have any further questions, concerns, or need assistance with anything else, please don’t hesitate to reach out to us. We’re here to help!

Thank you for your understanding and patience.

Warm regards, Left4code Team

Hi there!

I’m so glad to hear that you were able to find a solution to your issue. We really appreciate your feedback and will take it into consideration as we work on improving our product. In the meantime, we’ll be releasing an update with the latest version of HeadlessUI soon. Thank you so much for reaching out to us!

Or perhaps you could give me an example of how to use Tabulator in PHP MVC, since the documentation provided by Tabulator is not very clear to me.

Hello!

Sorry to hear that you are experiencing issues with implementing DataTable in your project. It could be caused by various factors, including conflicts with other libraries or incorrect implementation.

I suggest you ask for support on the discussion thread of the same item you purchased, and make sure to include details about the license you have. This will allow the support team to better assist you and provide specific solutions to your issue.

Hi there!

Thank you for your response. I’m sorry to hear that you’re still experiencing issues with the Alert component. I understand how frustrating this can be. Based on the screenshot you provided, it appears that there’s an error with the component. However, I’m having trouble reproducing the issue on my end.

Would it be possible for you to email us your project at ‘leftforcode@gmail.com’? This will help us investigate the issue further and provide more personalized assistance. Thank you!

const AlertComponent = Object.assign({}, Alert, {
  DismissButton: DismissButton,
});
export default AlertComponent;

export const DismissButton = <C extends React.ElementType = "button">({
......
);
};

const AlertComponent = Alert;
export default AlertComponent;

And in usage section import and use DismissButton directly instead of Alert.Dismiss Hope this doesn’t cause any other impact, please validate and apply the change if applicable to the source. Thanks!

Hi,

Thank you for sharing the workaround you found to resolve the issue with the exported object and how vite or Preact treats it. We appreciate your contribution and taking the initiative to share the solution.

We will review the changes you made and evaluate their impact on the source code. If the changes align with our guidelines and do not introduce any adverse effects, we will consider applying them to the source for future updates.

Thank you once again for your collaboration and providing valuable insights. If you have any further questions or need assistance, please feel free to reach out.

Best regards, Left4code Team

Hello!

Congratulations on your purchase of the Midone React Template! To customize the template using a different color theme, you will need to edit the primary, secondary, warning, danger, and other color settings in the “tailwind.config.js” file.

For example, to change the primary color to yellow, you can use the built-in yellow color from Tailwind as follows:

You can find more information on customizing colors in Tailwind’s documentation:

Once you’ve made changes to the “tailwind.config.js” file, you can use the new color theme throughout your application by referencing the color classes in your CSS and TSX files.

I hope this helps! Let us know if you have any further questions.

Hi there!

Thank you for reaching out to us. We’re sorry for the delayed response.

To use burgundy or navy-blue as your default theme color, you can refer to the default colors available in the TailwindCSS documentation at https://tailwindcss.com/docs/customizing-colors.

If the colors you need are not available by default, you can add them manually in the “tailwind.config.js” file.

Here’s an example code snippet that you can add to the “tailwind.config.js” file:

Once you have added these colors to your Tailwind config, you can use them in your CSS by referencing the color name.

For example, if you want to use the burgundy color, you can use the following code in your ”/src/assets/css/_colors.css” file:

We hope this helps! Let us know if you have any further questions.

Hi Hanafi Indra,

Thank you for your kind words and support! We apologize for the late response.

Regarding your question, the general CSS code is written in the file ”/src/assets/css/app.css”. However, most of the styling codes have been moved to each component using utility classes from Tailwind. For color settings, you can open the “tailwind.config.js” file.

To help you with changing the padding of the card, could you please provide a screenshot of the card section that you want to customize?

Best regards, Left4Code team

Hi there,

Thank you for your interest in Midone – React Admin Dashboard. I’m happy to let you know that Midone is built entirely on functional components, which should be perfect for your project needs.

If you have any further questions or concerns, please don’t hesitate to ask. We’re always here to help.

Best regards, Left4code

Hi, please send the JS version to jojojjose@gmail.com

Hi, thank you for your request. We have already sent the JS version of the file to your email address. Please let us know if you have any further questions or concerns.

Hi there,

Thank you for reaching out to us. Based on the error message you provided, it seems like there might be a typing issue with one of your components, specifically related to the HeadlessUI library.

We did some checks and it looks like there was an update to the typing for the HeadlessUI component after version 1.7.12. Therefore, we suggest you use version 1.7.11 or below for now while we work on adjusting the typing with the latest version.

https://github.com/tailwindlabs/headlessui/releases/tag/%40headlessui%2Freact%40v1.7.12

To do this, please run the following command: “yarn add @headlessui/react@1.7.11” and rebuild your project. This should resolve the issue.

Please let us know if you have any further questions or concerns.

Best regards,

Many thanks, this solution worked!

Great to hear that the solution worked! You’re welcome, and please don’t hesitate to reach out if you have any further questions or concerns. Have a great day!

Hi,

I apologize for the delay in responding to your comment.

Thank you for letting us know about this issue with the tabGroup component. We are sorry for any trouble it has caused you. We would be more than happy to help you resolve this problem.

To fix the issue, please open the file located at ”/src/base-components/tab/index.js”. Then, locate line 115 and make the necessary changes according to the following example.

useEffect(() => {
    init(dom(tabListRef.current).parent(), tabGroupProps);
  // }, [tabGroupProps]);
}, [tabGroupProps.length]);

If you need further assistance, please don’t hesitate to reach out to us.

Hi mahdikamali,

Thank you for reaching out to us,

We’ve sent the JS version, I hope these resources help you get up to speed quickly. If you have any further questions or concerns, please don’t hesitate to reach out to us. We’re here to help!

Best regards, Left4code Team

Hi mahdikamali,

Thank you for reaching out to us,

We’ve sent the JS version, I hope these resources help you get up to speed quickly. If you have any further questions or concerns, please don’t hesitate to reach out to us. We’re here to help!

Best regards, Left4code Team

Hi mahdikamali,

Thank you for reaching out to us,

We’ve sent the JS version, I hope these resources help you get up to speed quickly. If you have any further questions or concerns, please don’t hesitate to reach out to us. We’re here to help!

Best regards, Left4code Team

@Left4code please check comment and let us know we need to purchase theme ASAP.

Hello Inextrixharsh,

Thank you for your interest in our Enigma React theme. We apologize for the late reply, and we appreciate your patience.

Regarding your concern, we would like to inform you that our Midone theme is currently initialized from scratch with Vite and does not have Next.js version by default. Our team has not yet tried it on Next.js.

We want to assure you that the components we use, such as dropdown, modal, etc. have already switched to HeadlessUI which supports Next.js. However, we have not tested it with some other 3rd party library components (TomSelect, Litepicker, etc).

We hope this information helps. Please let us know if you have any further questions or concerns. We will be more than happy to assist you in any way we can.

Thank you for considering our Enigma React theme, and we look forward to hearing from you soon.

Best regards, The Left4code Team

Dear bysimsek,

Thank you for reaching out and I apologize for the delayed response. I’m sorry to hear that you are encountering an error with the source code of the ReactJS template you recently purchased.

It seems that there may be an issue with the latest version of Tailwind, which is causing the error you mentioned. As a temporary solution, could you please try using the previous version of Tailwind (version 3.2.7) until we find a permanent solution for this issue?

Please run the following command:

yarn add tailwindcss@3.2.7

If you continue to experience any issues, please don’t hesitate to reach out.

Best regards, Left4code Team

Hello!

We are happy to inform you that the issue has been resolved in the latest version of Tailwind (3.3.1) and you can check the changelog at the following link.
https://github.com/tailwindlabs/tailwindcss/releases/tag/v3.3.1
We recommend that you update your Tailwind version to the latest release. To do this, please run the following command:

yarn add tailwindcss

Please let us know if you have any other questions or concerns, we are always here to help.

Best regards, Left4code Team

Hi astrowaypro,

Thank you for reaching out to us and I apologize for the delay in my response.

We just sent you the latest JS version, kindly check your email..

Best regards, Left4code Team

Hello Srijontours!

I apologize for the delay in my response. Sure! Here’s an example of how to write a Redux slice in TypeScript:

import { createSlice, PayloadAction } from '@reduxjs/toolkit';

interface CounterState {
  value: number;
}

const initialState: CounterState = {
  value: 0,
};

export const counterSlice = createSlice({
  name: 'counter',
  initialState,
  reducers: {
    increment: (state) => {
      state.value += 1;
    },
    decrement: (state) => {
      state.value -= 1;
    },
    incrementByAmount: (state, action: PayloadAction<number>) => {
      state.value += action.payload;
    },
  },
});

export const { increment, decrement, incrementByAmount } = counterSlice.actions;

export default counterSlice.reducer;

In this example, we define a CounterState interface to define the shape of our Redux state. We also define the initial state, which sets the value to 0.

We then use the createSlice function from @reduxjs/toolkit to create a Redux slice, which includes a name, initialState, and reducers property. The reducers property defines the actions that can be dispatched to update the state.

Finally, we export the actions and reducer from the slice, which can be used in other parts of the application.

Here are some files that you can take a look at for examples:

- stores/colorSchemeSlice.ts - stores/darkModeSlice.ts - stores/sideMenuSlice.ts - stores/simpleMenuSlice.ts - stores/topMenuSlice.ts

Perhaps, if you’re not familiar with Typescript, we can send you the JS version. Let us know if you have any further questions or concerns. We’re always happy to help!

Hi . thank you . admgroup_co@yahoo.com

Just note that I am talking about this. . http://icewall-react.left4code.com/top-menu/dashboard-overview-1

Great to hear back from you! We’ve just sent over the plain JSX version of the file to the email address you provided. Please let us know if you have any further questions or if there’s anything else we can help you with. Have a wonderful day!

Best regards, Left4code Team