• Resolved yorne

    (@yorne)


    Hi,

    We encountered a significant problem with our website (Pure Wood Design). Every page we tried to access resulted in an error message (not a 404 or similar, but rather a “Page Not Found, Try Searching Here” message). Essentially, some links were inaccessible. This error appeared suddenly, without any updates or changes on our end, so we are unsure of the cause.

    We reported this issue to our hosting company, and they identified the Loco Translate plugin as the culprit. They disabled the plugin, and the pages became accessible again. However, this plugin is crucial for our website as it manages our multilingual content. Disabling it caused all languages to be mixed up, which is not a viable solution. I reactivated the plugin, and everything remained visible.

    To prevent this from happening again in the future, we would like to understand the cause of this issue and how to resolve it. Such errors lead to lost sales, and naturally, we want to avoid this.

    Thank you in advance for your response!

    Best regards,

    • This topic was modified 6 months, 2 weeks ago by yorne.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tim W

    (@timwhitlock)

    Firstly, it’s not necessary to point out your loss of sales. Perhaps not your intention, but this reads as though I am somehow responsible for your losses.

    As to the actual cause of your problem. I need to see error messages from your log files to know anything about a cause. Please ask your hosting provider to find these.

    If all your hosting provider did to resolve the issue was to?disable my plugin, then this is not sufficient evidence that it was the root cause. As an example, loading badly formatted translations can produce fatal errors. This is very common, although I don’t know how this would produce a “Not found” page.

    Thread Starter yorne

    (@yorne)

    Thank you for your quick response. It was certainly not my intention to point fingers or make you responsible for the situation. I just wanted to share that this is a difficult situation for us because our sales are dependent on a well-functioning website.

    At the moment, I am caught between three parties pointing fingers at each other. Polylang and your plugin are pointing to my hosting provider, and the hosting provider is pointing back to the plugins. This makes it hard to identify the real cause.

    I’ve made a screen recording today showing how I apply the “quick fix,” but unfortunately, this is not a sustainable solution as I have to do it manually every day. Today, the issue was related to the Polylang plugin, while yesterday the website worked after I disabled and re-enabled the Loco Translate plugin.
    https://vimeo.com/1006091095
    Password: Kingsberry

    I have attached the log files so you can review them. Hopefully, they will help to identify the cause.
    https://we.tl/t-GDGIxV2sU2

    Thank you very much for your help, and I look forward to your response.

    Plugin Author Tim W

    (@timwhitlock)

    I don’t really follow your video, but it appears like something to do with URL routing / permalinks.

    My plugin doesn’t interfere with URL routing, but creating custom translations of important identifiers could break permalinks. (I’m GUESSING HERE). If you have a product category in your URL and something is allowing that to be translated (i.e. tafels, tische tables), then whatever handles that logic is possibly expecting a particular set of values that it controls. Changing one of these values without its knowledge seems like a potential cause of error. (Still GUESSING). Also you show some other plugin that uses a custom path e.g. /smart in your video. Again, my plugin won’t stop that working, but a plugin that translates permalinks might.

    If disabling my plugin fixes your problem, then it’s likely due to a translation being loaded that would not otherwise be loaded. That’s the only thing I can say about its involvement. Your log files show nothing indicating it has caused an error.

    You’ve not actually mentioned what you’re using my plugin for, or what you’ve done with it. If it seems to cause a problem, then I suggest you simply keep it disabled. It’s not necessary for it to be enabled in production unless you need it to merge custom translation files. It’s a file editor and not much else.

    As for being caught between multiple parties pointing fingers: The onus is actually on you to diagnose the fault. You’ve elected to combine the functions of multiple plugins to achieve some effect that’s highly specific to your website. It’s entirely possible that this combination has problems, but unless you have a developer on your payroll who can debug it properly, then I suggest you keep it as simple as possible. If your login hiding plugin stops working due to some other change (possibly translatable URLs) then don’t use it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Issue with Website Accessibility due to Loco Translate Plugin’ is closed to new replies.