aniketji

Hi @adadediev95,

Our current version doesn’t support this We’ll definitely consider your suggestions for future updates, including compatibility to translate acf fields.

We appreciate your support and understanding.

Thank You.

Hi @robin6990,

Thank you for reaching out! Could you please provide a screenshot of the error message you’re showing and let us know when this error occurs?

Thank You.

Hi @cyprien24,

Thank you for reaching out!

We are currently focused on the Pro version of our plugin, which includes full-page translation support for Elementor. Once this version is released, we will begin researching Divi compatibility to assess its feasibility within our plugin.

If the integration works smoothly, we will consider adding support for Divi in a future update. We will keep you informed about our progress. Let us know if you have any questions in the meantime.

Thank You.

Hi @e4f389f0a0f320c ,

Sorry for the late reply! I checked the URL, and it’s working fine on iPhone here. It might be a cache issue on your end. Try clearing your browser cache, or check it in a private/incognito window. You can also test it on another device.

Let me know if the issue persists!

Thanks!

Hi @jperlman,

User Role option not available in free version and if you want to add custom role so you have need to modify the code.

If you are using the Pro version you can create a support query on our support page for premium plugin support.

Thank you.

Hi @gaousti,

As there has been no response from your end, I am closing this query.
If your issue is not resolved in the next update, you can create a new ticket.

Thank You.

Hi @skrapion,

As there has been no response from your end, I am closing this query.
If you are still facing any problem please create a?new topic?here.

Thank You.

Hi @hossam91,

Thank you for your suggestion. We appreciate your feedback and will keep this feature in mind for future updates.

Thank You.

Hi @riazkhan186,

It looks like the issue is with WPForms, which is a different plugin, not ours. Our plugin, County Code for Elementor Form Telephone Field, only works with Elementor forms. I checked the link you shared, and it seems you’re not using Elementor or an Elementor form.

If you’re having any issues with our plugin, feel free to let me know.

Thanks!

• This reply was modified 1 month, 2 weeks ago by aniketji.

Hello @majito,

Thank you for your message. Unfortunately, the content you provided doesn’t work for us since we need the plain text code.

To assist us further, please follow these steps:

1. Click on the three dots on the right side of your window.
2. Select the “Code Editor” option from the Editor section.
3. In the Code Editor, you’ll see the raw code of your post instead of the rendered content. Please copy this code and share it with us. This will allow us to recreate the same page on our end.

Regarding the translation membership you mentioned, we are ready to proceed with this and will discuss it with our team. For membership-related support, please feel free to contact us through the support page.

Thank you!

Hi @majito,

Regarding your concern about content ownership, you don’t need to share the original content of your post. You can create a dummy post with placeholder content and translate that instead. If the content still doesn’t appear in the translation string table, you can share that dummy post with us. This will help us recreate the same issue and investigate why the content isn’t showing up in the translation table.

Thanks so much for sharing your feedback! I can understand the issues you’re facing, and I appreciate you taking the time to explain them. Here’s a response to each point you mentioned:

1. Translation Issues with Names and Special Terms:
   We know there are sometimes issues with translating names, months, and places, where parts of words get translated incorrectly or not at all. This is likely due to the translation engine, and we’re working to improve this in future updates.
2. Can’t See Blocks Before Translation:
   It sounds like you’re unable to see content blocks before translating, which is causing problems. We’ll look into this issue and work on a fix so that you can view all the blocks properly.
3. Retranslation Option:
   Right now, there’s no way to retranslate a post once it’s been translated, but we’ll consider adding this feature in a future update. Thanks for suggesting it!
4. Duplicate Plugin and Image Alt Text:
   You don’t need the duplicate plugin just for translations. It’s mainly for replacing only the translated parts while keeping the rest the same. Also, we’ve noticed the issue with image alt text not translating, and we’ll fix this in an upcoming update.
5. Translation for Tags and Categories:
   At the moment, our plugin doesn’t support translating tags and categories, but we’re working on adding this to the Pro version in the future.
6. Character or Block Limits:
   There aren’t any specific limits on characters or blocks, but large posts with a lot of translation can sometimes cause issues. We’re improving this to prevent disruptions.
7. Using Chrome AI Translation on Mobile:
   Right now, Chrome’s AI translation only works on desktop, and unfortunately, it’s not available on mobile. We’re looking into other options for mobile users.
8. Completing Translations Later:
   We love your idea of being able to complete translations later, and we’ll consider adding a feature to do this in the future.

Regarding your suggestion about providing a translation membership to help test the plugin on your posts, we truly appreciate your offer! We will definitely share this idea with our senior team for further consideration and see how we can work together.

Thanks again for your helpful feedback, and we’ll continue working to make the plugin better!

Thank You.

Hi @totem1,

You can set the image size for your Cool Timeline story from the editor. Just edit the story you want, find the image size setting, and choose either small or full size. After that, save your changes.

Click here to see how to set story image size.

Thank You.

Hi @camerons2f,

Thank you for bringing this to our attention! We’ve reviewed the issue regarding the “Double Slash in URL” and can confirm that it will be addressed in our next plugin update. We appreciate your patience and understanding as we work on resolving this, and it should help prevent any future SEO flags related to this URL.

Feel free to reach out if you have any further questions or concerns!

Thank You.

Hi @majito,

Could you please share any post content that aren’t translated correctly? This will help us recreate the page, identify the problem, and ensure it’s addressed in our upcoming update or provide a better solution.

Thank You.

Hi @pifvouchers,

Can you please share the screenshot or tell what exactly you wanted so that I can understand it easily.

Thank You.