590 comments found.
Hi,
How do I go about downloading the XD Design files for the Enigma version?
I see the download files only include this for the Rubick version.
Hi,
I sincerely apologize for the delayed response. I regret to inform you that the XD design files are currently only available for the Rubick version, and they are not provided for the Enigma version.
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 understanding.
Best regards
Hey I have purchased the other version of this theme as discussed. Can you process refund for this order now?
i have also error Interface ‘Picker’ incorrectly extends interface ‘Litepicker’. after adding package “apollo-cache-inmemory”: “^1.6.6”,
Hi,
I sincerely apologize for the delayed response.
Regarding the error you encountered, we have released an update to address this issue. Please make sure to update the Litepicker base component to the latest version. If you face any further issues or have additional questions, feel free to let us know, and we’ll be glad to assist you.
Thank you for your understanding.
Best regards
I purchased other version. Can you process refund for this one now?
Hi,
I sincerely apologize for the delayed response. Thank you for reaching out. To process a refund, please follow this link: Refund Request.
https://themeforest.net/refund_requests/newIf you encounter any issues or need further assistance, feel free to let me know. Thank you for your understanding.
Best regards
Hello! How I can download old version?
Hi,
I sincerely apologize for the delayed response and any inconvenience caused. Unfortunately, we only provide the latest version at the moment.
If you have any specific concerns or questions about the latest version, please feel free to ask. Thank you for your understanding.
Best regards
Hi i’ve purchase your template a months ago. now when i try to build it it has this issue
src/base-components/Litepicker/litepicker.ts:9:11 – error TS2430: Interface ‘Picker’ incorrectly extends interface ‘Litepicker’. Types of property ‘on’ are incompatible. Type ‘((event: string, cb: (startDate: { dateInstance: Date; }, endDate: { dateInstance: Date; }) => void) => {}) | undefined’ is not assignable to type ‘(eventName: string | symbol, listener: (...args: any[]) => void) => this’. Type ‘undefined’ is not assignable to type ‘(eventName: string | symbol, listener: (...args: any[]) => void) => this’.
9 interface Picker extends Litepicker { ~~~~
Found 1 error in src/base-components/Litepicker/litepicker.ts:9
can you guide me on this? thank you
nvermind i’ve already fix this. hehe but please double-check it for others. by the way you guys have the best templates here in themeforest!
Hi,
I appreciate your understanding and I’m glad to hear that you were able to resolve the issue. If you have any further questions or encounter additional challenges, feel free to reach out. Thank you for your positive feedback; we strive to provide the best templates and support for our users.
If there’s anything else you need assistance with, please don’t hesitate to ask.
Best regards
Can you provide the download version of Midone (Vue + Vite) but without typescript please.
Hi,
I sincerely apologize for the delayed response. Unfortunately, we currently do not provide a version of Midone (Vue + Vite) without TypeScript. However, if you have specific concerns or customization needs related to TypeScript, please feel free to share them with us, and we’ll do our best to assist you.
For direct assistance, please contact us at leftforcode@gmail.com.
Thank you for your patience and understanding.
Best regards
Hello, Is it possible to have the same with javascript instead of TS ? Cheers, Best regards, Jérôme
Hi,
I sincerely apologize for the delayed response, and I appreciate your understanding.
For the JavaScript version of our template, please feel free to contact us via email at leftforcode@gmail.com. We’ll be happy to assist you further and provide the necessary information.
Thank you for your patience and interest in our product.
Best regards
Hi, is it possible to call method setHighlightedDays() from Litepicker instance?
Hi,
I sincerely apologize for the delayed response, and I appreciate your understanding.
Certainly! You can access the Litepicker instance as follows:
import Litepicker, { LitepickerElement } from "../base-components/Litepicker/Litepicker.vue";
import { ref, provide } from "vue";
const litepickerRef = ref<LitepickerElement>();
provide("bind[litepickerRef]", (el: LitepickerElement) => {
litepickerRef.value = el;
// Get instance here
console.log(litepickerRef.value.litePickerInstance)
});
<Litepicker
refKey="litepickerRef"
v-model="date"
:options="{
autoApply: false,
showWeekNumbers: true,
dropdowns: {
minYear: 1990,
maxYear: null,
months: true,
years: true,
},
}"
class="block w-56 mx-auto"
/>
Feel free to reach out if you have any more questions or need further assistance.
Thank you for your patience.
Best regards
Hello good day, I bought the vue template but when I run the application I get the following error: TypeError: Cannot read properties of undefined (reading ‘default’) at Object.fakePhotos (faker.ts:92:11) at faker.ts:428:20
Hi,
I sincerely apologize for the inconvenience you’re experiencing. To assist you better, could you please provide more details about the issue? It seems there might be a misconfiguration or a mistake in the file naming or path.
If possible, share relevant parts of your code or configuration related to the faker.ts file and the location where it’s being used. This will help me pinpoint the problem and provide you with a more accurate solution.
Thank you for your patience, and I’m here to help you resolve this issue.
Best regards
Hey I purchased this theme but its not the one I need. Can I change my license to the same Midone but the Laravel 10 version?
Hello,
Thank you for reaching out to us. We understand that the theme you purchased does not meet your requirements. Regarding changing your license to the Laravel 10 version of Midone, we can certainly assist you with that if the item has not been downloaded yet.
To proceed with the license change, please provide us with the purchase details, including the purchase code or any relevant information. Once we verify the details, we will be able to assist you further and arrange the license exchange.
Please let us know if you have any further questions or concerns. We are here to help.
Thank you for your understanding.
Best regards, Left4code Team
Hi! any news about updating Vue and Vite to their lastest version?
Hello,
Thank you for reaching out to us. We appreciate your interest in staying up to date with the latest versions of Vue and Vite. We want to inform you that we have released an update for our template, which includes the latest versions of Vue and Vite.
You can now download the updated version of the template from our platform. We recommend updating your project to benefit from the latest features and improvements offered by Vue and Vite.
If you have any further questions or need assistance with the update process, please feel free to reach out to us. We’re here to help.
Best regards, Left4code Team
Hi Left4Code!
We need to fix the @vue/compiler-sfc issue in version 3.3 Got a lot of errors.
We are considering this template for a bigger project, and we will need purchase the extended license.
Can you please update all base componentes in order to work with the lastest version of vue?
Hello,
Thank you for your interest in our template and considering it for your project. We appreciate your feedback regarding the @vue/compiler-sfc issue.
We understand the importance of keeping the template up to date with the latest versions of Vue and its dependencies. We have taken note of your request, and we are committed to providing timely updates to ensure compatibility with the latest versions.
We have already released an update that includes the latest dependencies. You can download the latest version of the template, which includes the necessary updates for Vue and other base components.
If you have any further questions or need assistance with the update, please feel free to reach out to us. We’re here to help!
Thank you for your support, and we look forward to serving you in your bigger project.
Best regards, Left4Code Team
First of all, I am sorry for my poor English skills. I’m about to use HTML version. I modified src/css/_color.css for primary-color change. Next, I ran “Yarn run watch”. The app.css in the dist has been changed, but the screen does not look normal. Changed from app.css (662KB) to app.css (416KB) in dist. What’s missing?
Hello,
Thank you for reaching out to us regarding the issues you are facing. We apologize for any inconvenience caused and we are here to assist you.
In addition to the points mentioned in our previous response, it’s important to ensure that the tailwind.config.js file is properly configured. Tailwind CSS uses this configuration file to determine which files to watch and include in the compilation process.
Please check the tailwind.config.js file and specifically the content section. By default, Tailwind CSS watches files with specific extensions specified in the content array. If you made modifications to a file with an extension that is not included in the content array, it won’t trigger the compilation process and reflect the changes in the final app.css file.
Here’s an example of how the content section in tailwind.config.js might look:
module.exports = {
// Other configuration options...
content: [
'./src/**/*.html',
'./src/**/*.vue',
'./src/**/*.js',
// Add other file extensions you want to include for watching and compilation
'./src/**/*.css',
],
};
In this example, the content array includes file extensions such as .html, .vue, .js, and .css. If you made changes to a file with the .css extension, it should trigger the compilation process and reflect the modifications in the final app.css file.
Please make sure to add the relevant file extension to the content array if you made changes to a file that is not being watched currently. After updating the configuration, run the Yarn run watch command again to see if the changes are reflected correctly.
If you have any further questions or need additional assistance, please feel free to reach out to us. We’re here to help.
Thank you for your patience and understanding.
Best regards, Left4code Team
there’s issue in Pagination.Link
const is_active_1 = ref<boolean>(false);
<Pagination> <Pagination.Link :active=”is_active_1” @click=”is_active_1 = !is_active_1”>test 1</Pagination.Link> </Pagination>
<button @click=”is_active_1 = true”>asdf</button>
the class is not updated
There is an issue with the Tom Select component. It is not functioning as expected when used with the load() hook. The component clears the input on each selection, and the default option is not getting selected automatically when the load() method populates the options asynchronously.
Hello,
We apologize for the delay in responding to your message regarding the issue with the Tom Select component. Thank you for bringing it to our attention.
We would like to inform you that we have implemented a wrapper for the TomSelect component in our Vue component, allowing you to dynamically load options just like a regular select element. This enhancement will enable you to load options dynamically and have them behave similarly to a standard select element.
<template>
<div>
<TomSelect v-model="selectedOption" class="w-full px-4 py-2 rounded border border-gray-300 focus:outline-none focus:ring focus:border-blue-500">
<option value="">Select an option</option>
<option v-for="option in options" :key="option.id" :value="option.id">{{ option.name }}</option>
</TomSelect>
</div>
</template>
<script setup lang="ts">
import TomSelect from "../base-components/TomSelect";
import { ref, onMounted } from 'vue';
interface Option {
id: number;
name: string;
}
const selectedOption = ref<number | null>(null);
const options = ref<Option[]>([]);
onMounted(async () => {
try {
// Make an API request to fetch the options
const response = await fetch('your-api-endpoint');
const data: Option[] = await response.json();
options.value = data;
} catch (error) {
console.error('Error loading options:', error);
}
});
</script>
If you have any further questions or need additional assistance, please don’t hesitate to reach out. We are committed to resolving this issue and ensuring that your experience with the Tom Select component is seamless and meets your expectations.
Thank you for your understanding and patience.
Yeah, I appreciate the support. The issue I was facing wasn’t with the implementation, but with the code quality. As you know, declaring a function on the load() hook decouples the logic from Vue lifecycles, which is what I want to achieve. But that’s okay. I was able to spot the issue with the wrapper component you guys built on top of Tom-Select, and I will work on a fix that’s compatible for both slot-level and prop-level options
Thank you for your feedback and for sharing your concerns regarding the code quality and the implementation of the load() hook in the wrapper component for Tom-Select. We apologize for any inconvenience this may have caused.
We understand your desire to decouple the logic from Vue lifecycles and achieve a more flexible solution. We appreciate your efforts in identifying the issue with the wrapper component and working on a fix that is compatible for both slot-level and prop-level options. If you need any assistance or have any questions during the process, please feel free to reach out to us. We are here to support you.
Thank you for your understanding and dedication to improving the compatibility and functionality of the wrapper component. We value your feedback and will take it into consideration for future improvements.
Best regards, Left4code Team
Thankyou
Hello. I was wondering if your plugin comes with a landing page
which file i should replace to apply latest update?
Hello,
Thank you for reaching out. To apply the latest update, you need to replace the following files:
”/src/base-components/Form” ”/src/base-components/Litepicker”
Simply replace the existing files with the updated ones, and the changes will take effect. If you have any further questions or need assistance during the update process, please don’t hesitate to ask. I’m here to support you!
Best regards, Left4code Team
Hello, There is an issue with the dashboard or tailwind. Borders don’t print. It shows on the dashboard but It doesn’t print borders when trying to print the page. Try printing this on the invoice page and you will see :
https://github.com/crushman1/dashboardissue/blob/main/code.htmlHi,
Thank you for providing the code snippet. After reviewing it, we noticed that the borders you used appear correctly in the print preview. It seems that there is no issue with the borders when printing.
To further investigate the problem you’re experiencing, could you please provide us with more detailed steps to reproduce the issue? This will help us understand the specific problem you’re facing and assist you better in resolving it.
Thank you for your cooperation. We look forward to helping you resolve this matter.
Best regards, Left4code Team
How could i download Enigma – Version 1.0.5 release date 21 May, 2022?
Because our project has used that version and we haven’t upgraded because of time limit.
