Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter diyajose8

    (@diyajose8)

    Hello Team,

    Thank you for your response.

    At the moment, we are using the free version of TranslatePress, and unfortunately, we are unable to open a support ticket on the website, as ticket support is available only for paid plans.

    Since upgrading immediately may not be possible for us, could you please let us know if there is any guidance or troubleshooting advice you can share here that would help resolve this issue? Or any way to connect the support on the website without any license number requirement as in the form.

    Thank you for your understanding, and we truly appreciate any support you can provide.

    Best regards,
    Diya Jose
    Mallu Developer

    Thread Starter diyajose8

    (@diyajose8)

    Hello Team,

    Thank you for your response and for sharing the options regarding image replacement and conditional shortcodes.

    We are already familiar with image replacement in TranslatePress, and in this case, the issue is not related to replacing individual images. I have replaced images accordingly using translatepress already.

    The main problem is that the FWD 3D Carousel itself fails to load on the Arabic pages. When the language is switched to Arabic, the carousel does not render at all, and browser errors indicate that carousel skin assets and internal paths are incorrect or not being resolved properly in the translated version. You can see the problem to yourself by checking the website : [double URL removed]

    So to clarify:

    • The carousel works perfectly on the English (default) pages
    • On Arabic pages, the carousel script initializes but fails because asset paths (skins / images / resources used by the plugin) appear to be altered or broken after the language switch
    • Because of this, the carousel does not display, regardless of image replacement settings

    This seems to be related to how TranslatePress handles URLs, paths, or dynamic shortcodes/scripts when switching languages, rather than a content-level image translation issue.

    Could you please help us with:

    • How TranslatePress handles plugin asset paths on translated pages
    • Whether there are any known compatibility issues with JavaScript-based sliders/carousels
    • If there is a recommended way to prevent path rewriting for plugin assets
    • Any specific configuration needed to ensure scripts and skins load correctly on RTL languages

    We are happy to provide:

    • Console errors
    • Network tab screenshots
    • Debug logs
    • Or test any suggested configuration from your side

    It would be really helpful if you could guide us on how to correct this so that the carousel works properly on the Arabic pages as well.

    Looking forward to your support.

    Best regards,
    Diya Jose
    Mallu Developer

    • This reply was modified 7 months ago by threadi.
Viewing 2 replies - 1 through 2 (of 2 total)