Specific server settings?

  • Resolved webshoppie

    (@webshoppie)


    5 years, 4 months ago

    Hi there,
    So before i begin i want to say that i read through the faq and other forums before posting this issue here. And yes it’s a “translation not showing” issue :), but not a noob one.
    So to begin. I had the plugin installed on my old server where it was translating everything fine. Now I moved it to a new server on siteground. All the files have moved along and I can see the translation source. But the strings on the theme are not translating anymore.

    Now I have been in contact with siteground support, to see if the rights with all the folders where ok. They requested a little more details if there are specific folders which need specific rights for the plugin to work. So not just the folders where the translation files are house, but also or any plugin-specific folders.

    Is there anything you could tell me about that?

    Please let me know if you would need any other details.

    Gr,
    Erick

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

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

    (@timwhitlock)

    5 years, 4 months ago

    When you say “not translating”, I assume you mean “not displaying” and that the strings are already translated and saved to MO files on your disk. As you know already, it is WordPress that actually reads these files and your theme that loads them and ensures they are displayed properly.

    The one situation where my plugin is involved is when you have translation files stored in the safe (custom) directory. In this case you must have Loco Translate enabled. There are situations that can cause this to fail. But you’ve read the FAQs, so I assume you’ve eliminated the issues here.

    As to your question about specific folder rights. As long as WordPress can read the files, then they can be loaded. This has nothing to do with Loco Translate, notwithstanding the previous paragraph. I don’t have any other details I can give you, unless you have a more specific question.

    Thread Starter webshoppie

    (@webshoppie)

    5 years, 4 months ago

    Hi there,
    First of all, sorry for the late answer. I was waiting for your reply but I didn’t get an email about it. when I decided to take a look on the forum, I did see you answered. So excuse me for that.

    I have made a details video of the situation

    Here you can see the difference between the live site ( where it’s not working) and the staging site ( where it is working, after deleting the translation and starting over).

    Now I don’t want to start over on the live site, so I hope you can get some clues to what might be set up wrong from the video I made.

    Gr,
    Erick

    Plugin Author Tim W

    (@timwhitlock)

    5 years, 4 months ago

    Thanks for spending the time to make the video, but it doesn’t make me any better positioned to guess at the cause of your problem.

    The ONLY way to solve issues like this is to DEBUG your site. That means finding the code that displays the text and finding which exact file it’s been loaded from.

    Looking at the front end and then looking at the contents of a PO file is not going to tell you what’s going on. It is the code that runs in your theme and in your plugins that determines which MO file is loaded and then what happens to the translated strings. There are infinite possibilities, which is why – with my file editor installed on a million servers – I cannot investigate these issues personally.

    Thread Starter webshoppie

    (@webshoppie)

    5 years, 4 months ago

    Hi there,
    I figured it out. I had to do with the filename. The file was called themename_nl_NL.po
    but it was supposed to be called themename_nl_NL_formal.po. In this specific case, it was besa-nl_NL.po VS besa-nl_NL_formal.po
    Got the clue when u deleted the file and wanted to upload it again.

    So case closed 🙂

    Thanks.
    Gr,
    Erick

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Specific server settings?’ is closed to new replies.