I have also tried changing the theme to Twenty Twenty One, and it still did not pick up any strings.
Plugin Support
Alex
(@alexcozmoslabs)
Hi,
Mostly, this is happening when you use a speed optimization plugin. These plugins compress all JS files into one file, but this process can create errors when you load a page.
See if you have this type of plugins, disable them and try again to do the translation.
Please, see if your server has HTTP2 and GZIP.
If it does, autooptimize doesn’t actually has a positive impact on your website speed as HTTP2 means everything is downloaded in parallel, on the same connection and GZIP means minification doesn’t actually do anything.
If a string isn’t selectable with the pencil tool, you can search for it using the list of strings, available for translation from the Translation Editor. You can search for it also in the String Translation Interface –> Regular tab (this tab requires to be activated from TP Settings –> Advanced tab –> Debug section).
Kind Regards,
Hi there.
None of the above has worked. I have deactivated almost all plugins to find the issue and TranslatePress is still not working the way it should.
When I try to use Regular tab, I get an error saying that I “probably was logged out”.
Please advise.
Plugin Support
Alex
(@alexcozmoslabs)
Hi,
If you’re seeing the “You were probably logged out” error when trying to use the Regular tab in TranslatePress, this typically means there’s an issue with your WordPress authentication cookies or session handling. Here are a few things to check:
1. Make sure you’re actually logged in
Sometimes, your session might expire or get interrupted. Try:
- Logging out and logging back in again.
- Opening the TranslatePress editor in a private/incognito browser window.
- Checking if the error persists across browsers.
2. Check for Caching or Security Plugins
Even though you’ve deactivated most plugins, make sure there’s no caching layer still active:
- Clear all caches: page cache, browser cache, and any server-level cache (like Varnish, Cloudflare, or host-provided caching).
- If you have a firewall or security plugin (like Wordfence), make sure it’s not blocking admin AJAX calls or sessions.
3. Verify the Site URL Configuration
In Settings > General, check that:
- WordPress Address (URL) and Site Address (URL) match exactly.
- They’re using the same protocol (http vs https), no extra slashes, etc.
Mismatches can cause authentication cookies to not work properly.