WPIntell

Source evidence

Fatal error

SweepPress: Website Cleanup and Optimization · support · 2023-08-23T09:36:00+00:00

mixedsentiment
highseverity
0.95relevance
8replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 31 rows with source links

12.9% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

27 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
pasglop resolved
Hello, After download and activate the plugin, if i want to go to it dashboard, i’ve got a fatal error : Fatal error: Uncaught Error: Unknown format specifier “,” in D:\sites\toit\wp-content\plugins\sweeppress\d4plib\dev4press\core\admin\Plugin.php on line 264 Call stack: sprintf() wp-content/plugins/sweeppress/d4plib/dev4press/core/admin/Plugin.php:264 Dev4Press\v\C\A\Plugin::help_tab_getting_help() wp-content/plugins/sweeppress/core/admin/Plugin.php:199 Dev4Press\P\S\A\Plugin::help_tab_getting_help() wp-content/plugins/sweeppress/d4plib/dev4press/core/admin/Plugin.php:244 Dev4Press\v\C\A\Plugin::load_admin_page() wp-includes/class-wp-hook.php:310 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:334 WP_Hook::do_action() wp-includes/plugin.php:517 do_action() wp-admin/admin.php:23 With WP 6.3, PHP 8.0.7, Mysql 5.7.37 Thanks for your answer Hi, This is not the problem with the plugin, but with the French translation. At one point, the %s in the string was translated as % only, and that caused the issue. It has been fixed since, so I am not sure why you are getting that error now. This was discussed already here: https://wordpress.org/support/topic/error-1792/ Try to remove plugin translation file from your installation (it should be in wp-content/languages/plugins folder), and try again. Or switch language to English temporarily to confirm it is the translation issue. I have no control over the translations on WordPress.org, and if someone commits wrong translation it can cause problems. Milan I don’t understand. this is a copy of the french translation, and there is no problem with that. This is the validated translation : Original chain : To get help with %s, you can start with Knowledge Base list of frequently asked questions , user guides, articles (tutorials) and reference guide (for developers ). The translation : Pour obtenir de l’aide sur les %s, vous pouvez commencer par la liste des questions fréquemment posées de la base de connaissances, les guides d’utilisation, les publications (tutoriels) et le guide de référence (pour les développeurs/développeuses). What i can see in the Plugin.php file, in line 264, is that you use d4plib for textdomain, instead of SweepPress. Is there a reason ? regards Folder d4plib contains the shared library and it uses different domain. But, that is not the problem here, problem is that at some point the translation on WordPress.org was invalid, and the MO file download contains broken translation. Now, if I download French translation (after deleting the files I had previously), it downloads translation, and that one string is no longer translated. I am not sure what the problem is, but please, go to the wp-content/languages/plugins and delete sweeppress translation files. If the problem is gone, it means you had old translation file. Or, simply try switching to English to see if the problem is gone. It is possible that at different points in time, translation downloaded by WordPress was invalid, and was not properly updated. Let me know if the problem is gone when the files are deleted. And, try to download translations directly from WordPress.org manually, and replace them in the languages folder. Milan Without any translation french file (deleted), the problem is the same, same error, same file, same line. And same thing if i download the .mo file from translation.org. I precise that’s it’s sweepPress lite. This reply was modified 2 years, 9 months ago by pasglop . I have set up the blank test website, installed only SweepPress Lite, tried English, French and other languages, I can’t reproduce this error. The line in the code is valid. The only way to trigger the error is to download the invalid translation from WordPress.org and use that one (I have it in backup from previous report – same report same error, same language). I will try to reproduce the problem some other way, but the code is all valid, it is not triggering error on it’s own. I will keep you posted over the next week or so, if I find out something new. Hello, some news : It works with PHP 7.4, but not with PHP 8.0.7… OK, thanks, I will investigate this, and release update as soon as possible. PHP version change did the trick, and I have found the problem, thanks! Version 2.3.1 has been released with the fix.

Comments

8 shown
Milan Petrovic 2023-08-25T10:52:00+00:00

Hi, This is not the problem with the plugin, but with the French translation. At one point, the %s in the string was translated as % only, and that caused the issue. It has been fixed since, so I am not sure why you are getting that error now. This was discussed already here: https://wordpress.org/support/topic/error-1792/ Try to remove plugin translation file from your installation (it should be in wp-content/languages/plugins folder), and try again. Or switch language to English temporarily to confirm it is the translation issue. I have no control over the translations on WordPress.org, and if someone commits wrong translation it can cause problems. Milan

pasglop 2023-08-31T13:50:00+00:00

I don’t understand. this is a copy of the french translation, and there is no problem with that. This is the validated translation : Original chain : To get help with %s, you can start with Knowledge Base list of frequently asked questions , user guides, articles (tutorials) and reference guide (for developers ). The translation : Pour obtenir de l’aide sur les %s, vous pouvez commencer par la liste des questions fréquemment posées de la base de connaissances, les guides d’utilisation, les publications (tutoriels) et le guide de référence (pour les développeurs/développeuses). What i can see in the Plugin.php file, in line 264, is that you use d4plib for textdomain, instead of SweepPress. Is there a reason ? regards

Milan Petrovic 2023-08-31T14:23:00+00:00

Folder d4plib contains the shared library and it uses different domain. But, that is not the problem here, problem is that at some point the translation on WordPress.org was invalid, and the MO file download contains broken translation. Now, if I download French translation (after deleting the files I had previously), it downloads translation, and that one string is no longer translated. I am not sure what the problem is, but please, go to the wp-content/languages/plugins and delete sweeppress translation files. If the problem is gone, it means you had old translation file. Or, simply try switching to English to see if the problem is gone. It is possible that at different points in time, translation downloaded by WordPress was invalid, and was not properly updated. Let me know if the problem is gone when the files are deleted. And, try to download translations directly from WordPress.org manually, and replace them in the languages folder. Milan

pasglop 2023-08-31T15:48:00+00:00

Without any translation french file (deleted), the problem is the same, same error, same file, same line. And same thing if i download the .mo file from translation.org. I precise that’s it’s sweepPress lite. This reply was modified 2 years, 9 months ago by pasglop .

Milan Petrovic 2023-08-31T16:33:00+00:00

I have set up the blank test website, installed only SweepPress Lite, tried English, French and other languages, I can’t reproduce this error. The line in the code is valid. The only way to trigger the error is to download the invalid translation from WordPress.org and use that one (I have it in backup from previous report – same report same error, same language). I will try to reproduce the problem some other way, but the code is all valid, it is not triggering error on it’s own. I will keep you posted over the next week or so, if I find out something new.

pasglop 2023-09-01T07:32:00+00:00

Hello, some news : It works with PHP 7.4, but not with PHP 8.0.7…

Milan Petrovic 2023-09-01T07:34:00+00:00

OK, thanks, I will investigate this, and release update as soon as possible.

Milan Petrovic 2023-09-01T09:56:00+00:00

PHP version change did the trick, and I have found the problem, thanks! Version 2.3.1 has been released with the fix.