Translation

polatonik
(@polatonik)

2 months ago
Hello Blocksy Team,

I am a long-time user of the Blocksy theme and I am currently finalizing a project for a local development association (yenipazaryeg.org.tr). I am achieving 100/100 performance scores on PageSpeed Insights and I want to maintain this by using native .po and .mo files instead of translation plugins.

However, several UI strings remain in English despite having the correctly named blocksy-tr_TR.mo file in my /wp-content/languages/themes/ directory.

The strings that are not translating are:
- Post Navigation: “PREVIOUS” and “NEXT”. Note: “PREVIOUS” renders as “PREVİOUS” (with a Turkish dotted İ), suggesting a hardcoded strtoupper transformation.
- Comments Section: “Leave a Reply”, “Add Comment”, and “Post Comment”.
- Buttons & Archives: “More”, “Show more”, and “Read more” labels.
- Search Results: “Search Results for” and “Nothing Found” messages.
Could you please clarify:
1. Are these specific strings wrapped in the standard __() or _e() functions in the latest version of Blocksy?
2. Why does the theme appear to bypass the native translation files for these specific components?
3. Which template files (specifically in template-parts/ or inc/) should I check to manually wrap these strings if they are currently hardcoded?
I want to resolve this at the source code or file level to keep my performance metrics at 100/100.

Thank you for your assistance.

Best regards, Ömer Polat
- This topic was modified 2 months ago by polatonik.
- This topic was modified 2 months ago by polatonik.
- This topic was modified 2 months ago by polatonik.
The page I need help with: [log in to see the link]

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

Eduard
(@cteduard)

2 months ago

Hello @polatonik,

Are you certain you have verified and created these files correctly? I can confirm that these translations are present in the main .pot template file and can be translated without issue. However, as you have chosen to pursue a custom translation route, you are responsible for ensuring the files are correctly implemented. We do not “bypass” any translations, and the issue is most likely in how you have implemented these translation files.

Here is a collection of screenshots demonstrating these strings are findable in the translation files and template, and work correctly when modified:

https://ibb.co/7J3QCT27 https://ibb.co/zH04NRBq https://ibb.co/GfhNwSBt https://ibb.co/jPHnht4F https://ibb.co/wFPyG0P4 https://ibb.co/CK5czQ25 https://ibb.co/6Jbr9Z5q https://ibb.co/p6ynkRLz

Thanks,
Eduard

Thread Starter polatonik
(@polatonik)

2 months ago

Actually, I prefer to keep things simple and avoid dealing with complex translation plugins or extra overhead. I only need to translate about 7-8 specific strings on my site, and I prefer to do this directly through the files.

I am aware that these changes might be overwritten during an update, but I am comfortable reapplying them manually. My priority is to keep the site lightweight without installing additional plugins. I just want to ensure that I am targeting the correct files for these specific strings.

Eduard
(@cteduard)

2 months ago

Hello @polatonik,

Unfortunately, we are unable to advise on custom implementations as we cannot assess the implications of your setup. There are numerous unknown variables that could affect this workflow.

In general, there should not be any issues or restrictions when editing these files. However, there could be other variables affecting your workflow that we are not aware of.

Thanks,
Eduard

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

You must be logged in to reply to this topic.