Plugin Author
Tim W
(@timwhitlock)
Please post the following:
(1) Enable WordPress debug mode and show me the results from Loco Translate > Settings > Debug
(2) Post any errors appearing in your browser console from the editor screen.
(3) Provide a full list of all other plugins you have installed.
(1) Debug mode is set “on”. When i open loco translate, navigate to the plugin i want to translate (where the editor is missing), no error is logged…
(2) No error in browser. Using Chrome.
(3) Here is the list: https://we.tl/t-5dvZTOu90I It’s quiet a lot, but there is no new plugin. All of them worked fine with loco before…
Thank you!
Plugin Author
Tim W
(@timwhitlock)
(1) As I asked = please show me the results from Loco Translate > Settings > Debug
(3) That is a lot. Too many for me to go through and personally verify for conflicts. Is it possible to know which ones have been added or updated since Loco Translate last worked as expected? Note that Loco Translate itself hasn’t been updated for 2 months.
(1) I don’t find this setting. See screenshot: https://we.tl/t-mQOjGESNBb
(2) I translated the last strings nearly 6 month ago…
Tim
Plugin Author
Tim W
(@timwhitlock)
The Debug tab will be visible if you have WordPress debug mode on.
You can forcefully view this tab by viewing admin page wp-admin/admin.php?page=loco-config&action=debug
Here is the report:
Versions
Loco Translate:
2.4.0
WordPress:
5.4
PHP:
7.2.32 (cgi-fcgi)
Server:
Apache/2.4.10 (Unix)
Unicode
UTF-8 rendering:
ΟΚ ✓
Multibyte support:
ΟΚ ✓
Ajax
Endpoint:
/wp-admin/admin-ajax.php
JSON decoding:
ΟΚ ✓
Ajax test result: ΟΚ ✓
Translation APIs
Google Translate:
No API key
Microsoft Translator:
No API key
Yandex.Translate:
No API key
Limits
WP_MEMORY_LIMIT:
256 MB
WP_MAX_MEMORY_LIMIT:
256 MB
PHP memory_limit:
256 MB (changeable)
PHP post_max_size:
999 MB
PHP max_execution_time:
600
Filesystem
Custom languages directory:
wp-content/languages/loco
Directory writable:
Yes
File mods disallowed:
No
File mod safety level:
Warn
Debug settings
WP_DEBUG:
Off
WP_DEBUG_LOG:
Off
WP_DEBUG_DISPLAY:
Off
PHP display_errors:
Off
PHP log_errors:
Off
PHP error_log:
(none)
Plugin Author
Tim W
(@timwhitlock)
Firstly I can see that WordPress debug mode is “Off”. So fix that and try again. You may get more useful errors appearing on the page.
I don’t see any other problems, except to note that version 2.4.1 was released yesterday, so best upgrade.
I have activated debug mode and updated the plugin (no changes). Will come back to you within the next days…
Thank you for your quick support – awesome!
Tim
Hi Tim,
here is the debug log – debug mode is activated for nearly two days. The normal debug log is empty…
Versions
Loco Translate:
2.4.1
WordPress:
5.4
PHP:
7.2.32 (cgi-fcgi)
Server:
Apache/2.4.10 (Unix)
jQuery:
1.12.4; ui/1.11.4; migrate/1.4.1
Unicode
UTF-8 rendering:
ΟΚ ✓
Multibyte support:
ΟΚ ✓
Ajax
Endpoint:
/wp-admin/admin-ajax.php
JSON decoding:
ΟΚ ✓
Ajax test result: ΟΚ ✓
Translation APIs
DeepL Translator:
No API key
Google Translate:
No API key
Microsoft Translator:
No API key
Yandex.Translate:
No API key
Limits
WP_MEMORY_LIMIT:
256 MB
WP_MAX_MEMORY_LIMIT:
256 MB
PHP memory_limit:
256 MB (changeable)
PHP post_max_size:
999 MB
PHP max_execution_time:
600
Filesystem
Custom languages directory:
wp-content/languages/loco
Directory writable:
Yes
File mods disallowed:
No
File mod safety level:
Warn
Debug settings
WP_DEBUG:
Off
WP_DEBUG_LOG:
On
WP_DEBUG_DISPLAY:
On
PHP display_errors:
Off
PHP log_errors:
Off
PHP error_log:
(none)
Thank you!
Plugin Author
Tim W
(@timwhitlock)
Well, I can’t reproduce any error like yours.
Some ideas….
(1) Verify your debug log is actually working and you know where it’s logging to. I notice that your PHP error_log setting is empty and your WP_DEBUG setting is still Off. Personally I’d enable all the debug options to make failures as noisy as possible. Related: WordPress docs.
(2) View the source of the admin page and see if it has stopped rendering prematurely. i.e. Whether you have a complete HTML document, right up to the closing </html> tag. If it did end prematurely you may be able to see the reason in the source, although you may have to switch more debugging options on first. Failing that, note where the HTML document stops. This may help you find your point of failure.
(3). Disable other plugins one-by-one to see if any are interfering. You should always do this when you have an unexplained error that cannot be reproduced by others.
