Hello Andres,

Thanks for pointing out the information about Easepick. We’ll certainly look into it for the next update, considering the suggestions provided on their website. Your feedback is appreciated, and we’re working to ensure our project stays current and effective.

If you have any further questions or specific preferences, feel free to let us know.

Best, Left4code Team

Hello,

Thank you for your request. We’ve sent the source code for the latest Laravel+Vue project to your email (rohmad.ew@gmail.com). Please check your inbox, and if you encounter any issues or have further questions, feel free to let us know.

Happy coding!

Hi,

This is a Vue.js template (client-side). If you require database modifications, kindly make a request to the backend server using a different language or framework. Feel free to reach out if you need further assistance or clarification.

Hi,

Thank you for your reply.

Yes, we have just updated our live demo link to a new address. Please check again on the live demo page of the item.

Hi vivano76,

I sincerely apologize for the delayed response, and I appreciate your understanding.

Regarding the issue you’re facing with the custom package, could you please provide more details about the specific package you’re adding? This will help me better understand the context of the problem and provide you with a more accurate solution.

As a general suggestion, this error might be related to the plugin you’re using extending the base type. You can find more information about a similar issue on the Vue.js GitHub repository here.

Once you provide additional details, I’ll do my best to assist you further.

Thank you for your patience and cooperation.

Best regards, Left4code

Hi vivano76,

I sincerely apologize for the delayed response, and I appreciate your understanding.

Regarding the issue you’re facing with the custom package, could you please provide more details about the specific package you’re adding? This will help me better understand the context of the problem and provide you with a more accurate solution.

As a general suggestion, this error might be related to the plugin you’re using extending the base type. You can find more information about a similar issue on the Vue.js GitHub repository here.

Once you provide additional details, I’ll do my best to assist you further.

Thank you for your patience and cooperation.

Best regards, Left4code

Hello mohamme5d,

I sincerely apologize for the delayed response, and I appreciate your understanding. I regret to inform you that, at the moment, we don’t have any plans to release an Angular version. However, I truly value your interest in our product and your feedback is noted for future considerations.

If you have any further questions or if there’s anything else I can assist you with, please feel free to let me know.

Thank you for your patience and understanding.

Best regards, Left4code

Dear amwn85,

I sincerely apologize for the delayed response, and I appreciate your patience. I understand the frustration you’ve encountered with the reactivity of the ‘variant’ attribute in our Button component.

After thorough investigation, it appears that our component, by default, is not designed to handle reactive props. The use of object destructuring (const { as, size, variant, elevated, rounded }) can cause props to lose reactivity.

To address this issue, I recommend modifying the code as follows:

”/src/base-components/Button/Button.vue”

const { as, size, variant, elevated, rounded } = withDefaults(
  defineProps<ButtonProps>(),
  {
    as: "button",
  }
);

const props = withDefaults(
  defineProps<ButtonProps>(),
  {
    as: "button",
  }
);

const computedClass = computed(() => twMerge([
  // ... existing styles ...
  props.variant == "primary" && primary,
  // ... other variant styles ...
  // ... remaining styles ...
]));

This adjustment should ensure the reactivity of the ‘variant’ prop based on the provided example.

Once again, I apologize for any inconvenience this may have caused. If you have any additional questions or concerns, please feel free to reach out.

Best regards, Left4code

Hi,

I sincerely apologize for the delayed response, and I appreciate your kind understanding. I’m delighted to hear that the issue has been resolved. If you have any more questions or need further assistance, feel free to reach out. Thank you for your patience, and I wish you a great experience with our product.

Best regards

Hi,

I sincerely apologize for the delayed response, and I appreciate your understanding. Regarding the error you encountered in the ‘topbar-menu.ts’ file, it seems there might be an issue with the import statement.

Instead of:

import { Icon } from "@/base-components/Lucide/Lucide.vue";

Please use:

import Icon from "@/base-components/Lucide/Lucide.vue";

This should resolve the error you’re facing. If you encounter any further issues or have additional questions, please feel free to ask.

Thank you for your patience.

Best regards

Hi,

I sincerely apologize for the delayed response, and I appreciate your patience. It seems there might be a misunderstanding in the installation process. Please note that, with Vue.js applications, it’s crucial to follow a specific set of steps, including the compilation process.

Unfortunately, the login information provided is for your DirectAdmin panel, which doesn’t directly relate to the installation of the program. Here are the general steps you should follow:

Compile the Vue.js Application:

1. Ensure you have Node.js and npm installed.
– Open a terminal and navigate to your project directory.
– Run the command: npm install to install dependencies.
– After installation, run: npm run build for the compilation.


2. Upload to Hosting:
– Upload the contents of the ‘dist’ directory (created after the build) to your hosting server.

3. Configure DirectAdmin (if necessary):
– DirectAdmin is not directly involved in Vue.js app installation. Ensure your hosting environment supports Vue.js.

If issues persist, please provide more specific details or error messages encountered during the process.

Once again, I apologize for any confusion, and thank you for your understanding.
Best regards

Hello,

I followed your steps as listed but in the file downloaded there is no folder called “dist” what I have here is (I) Source (starter) (II) Source

I have upload both folders to see if either of them will work, but when I login to SSH to install npm, I keep getting the error message in the screenshot I have attached and emailed to you at: leftforcode@gmail.com.

Please I will need a step by step Instruction on how to install the program properly since I am new to Vue.

Hi,

Thank you for your response.

You need to install dependencies first and run the compiler to generate the ”/dist” directory. You can use the project in the “Source” or “Source (starter)” directory; the only difference between the two versions is the number of pages.

Please follow the step-by-step instructions below to install dependencies and run the compiler.

- Install Node.js : Please install latest version of Node.js from https://nodejs.org
- Install Yarn from https://yarnpkg.com
- Extract downloaded project files : Extract the admin dashboard to your suitable directory or folder.
- Access console : Open node.js console.
- In console, navigate to the location where main folder is extracted.
- Navigate to the Source folder inside main folder.
- Run yarn install command to install package dependencies.
- Run yarn run dev to start compiling assets or yarn build for production use.

Hi Adnan Zaheer,

I sincerely apologize for the delayed response and any inconvenience caused. I appreciate your understanding.

Regarding your inquiry, it’s important to note that our template is built on Vue.js, and the integration with Laravel 10, Inertia, and Jetstream is not included in the package. The template is primarily designed to work with Vue.js.

If you have specific requirements for Laravel 10, Inertia, and Jetstream integration, you may need to customize the template accordingly. Unfortunately, we don’t provide out-of-the-box support for these specific technologies in the current version.

As for the documentation, I apologize for any confusion. The included documentation is meant to guide you through the features and customization options available within the template. If you have any specific questions or need assistance with customization, feel free to ask, and I’ll do my best to help.

Once again, I appreciate your understanding, and I’m here to assist you with any further questions or concerns.

Best regards

Hi,

I sincerely apologize for the delayed response, and I appreciate your understanding.

Regarding your question, our template is based on Vue.js, and unfortunately, integration with Laravel 10, Inertia, and Jetstream is not included in the package. The template is designed to work seamlessly with Vue.js.

If you have any further questions or if there’s anything else I can assist you with, please feel free to let me know.

Thank you for your patience and for choosing our product.

Best regards

Hi,

I sincerely apologize for the delayed response, and I appreciate your patience.

I understand your concern about the updated documentation. We are currently working on providing the latest documentation, and it will be available shortly. In the meantime, if you have specific questions or need assistance with anything, please feel free to ask, and I’ll do my best to help.

Thank you for your understanding and for choosing our product.

Best regards

Hi,

I sincerely apologize for the inconvenience, and I appreciate you bringing this issue to our attention. It seems there was an oversight, and the breadcrumb store file should not have been included—it was unintentional.

Rest assured, we will rectify this in the upcoming version by removing the redundant breadcrumb store. Thank you for your understanding, and we value your diligence in reporting this.

If you have any further questions or if there’s anything else I can assist you with, please feel free to let me know.

Best regards

Hi,

I sincerely apologize for the inconvenience you’re facing. Regarding the dependencies you mentioned, @fullcalendar/common and @fullcalendar/core are already included in the @fullcalendar/vue3 package, which is a dependency for Midone. You can find this information in the node_modules/@fullcalendar/vue3/package.json file, so there’s no need to add them separately to the Midone package.json.

To assist you further with the issue, could you please provide more details or steps to reproduce the problem? This will help us investigate and resolve the issue more effectively.

Thank you for your patience and understanding.

Best regards

Hi. Anyone available for support?

Hi,

I sincerely apologize for any inconvenience. I understand your preference for the JS version of the theme. Unfortunately, there seems to be an oversight in the download options. I kindly ask you to contact us via email at leftforcode@gmail.com so that we can promptly provide you with the JS version and assist you further.

Thank you for your understanding and patience.

Best regards

Hi spormeon,

You can download the latest files as usual through your account. In our most recent update, we have incorporated the TomSelect dependency version “^2.2.0.” Please proceed with the update, and this should address the styling issues you’ve encountered. If you happen to face any further issues or have additional questions after updating, please don’t hesitate to reach out to us again.

Thank you for your understanding and cooperation.

Best regards

we’re still using the scss versions, these ra now just css, how can we get a converted version?

Hi,

Thank you for your response.

I apologize, but it seems you may need to manually readjust each CSS selector and property from the latest version to obtain the converted version.

Hi,

I sincerely apologize for the delayed response. Regarding your inquiry, I’d like to clarify that our template doesn’t include native support for InertiaJS by default. Therefore, integration with InertiaJS is not covered in our support.

If you have further questions or need assistance with other aspects of the template, feel free to ask.

Thank you for your understanding.

Best regards

Hi,

I sincerely apologize for the delayed response. Unfortunately, as of now, Tom Select does not have built-in support for virtual scroll loading data from Ajax. I appreciate your understanding.

If you have any other questions or if there’s anything else I can assist you with, please feel free to let me know.

Thank you for your patience.

Best regards