Malae
Forum Replies Created
-
Hello Nik,
We are still seeing this issue even after the update to version 1.8.39.Forum: Plugins
In reply to: [Photo Gallery by 10Web - Mobile-Friendly Image Gallery] Deprecated PHPHello Nik,
We are still seeing the deprecated PHP even after the update to version 1.8.39.Forum: Plugins
In reply to: [Spotlight Social Feeds - Block, Shortcode, and Widget] Deprecated PHPHalo Hendra,
Thank you for the heads up. The update appears to have fixed the issue.Hello,
Yes it’s been around for a long time and many plugins were affected. Most with active support were fixed a long time ago. This plugin is the only one we are using which still causing problems. There are no issues on the front end, but please refer to my previous posting, which strangely disappeared and I insert below:
——————————————————————————————————————-
Malae(@malae)
After more than 5 weeks and a recent update the above deprecated PHP warnings are still flooding the wp_debug.log file together with the Notice: Function _load_textdomain_just_in_time was called incorrectly. This makes it difficult to track down other issues.
Please fix these issues.
——————————————————————————————————————-
When I say flooding, this perhaps an understatement. If the debug log file with the 4 warnings (1 Notice and 3 deprecated PHP) is left running for a few days it becomes several MB in size and cannot be opened on the server and must be downloaded. This is a back-end issue that is very annoying
Forum: Plugins
In reply to: [Photo Gallery by 10Web - Mobile-Friendly Image Gallery] Deprecated PHPHello Nik,
Yes the version is 1.8.38.
Forum: Plugins
In reply to: [Photo Gallery by 10Web - Mobile-Friendly Image Gallery] Deprecated PHPAfter more than 5 weeks and a recent update the above deprecated PHP warnings are still flooding the wp_debug.log file together with the Notice: Function _load_textdomain_just_in_time was called incorrectly. This makes it difficult to track down other issues.
Please fix these issues.
Forum: Plugins
In reply to: [WPGlobus] WPGlobus Translate Options StatusFurther to my posting above, I have updated two websites and returning to the first one updated, I found that the plugin was no longer Active, but the second one was still active. Reactivating the first site again, the second was deactivated. This is repeatable and it appears that only one site can be activated at a time.
I returned to the update download page an repeated the download assuming that I would get a new key. However, the new download has the same key. How can I activate the plugins on both sites?Forum: Plugins
In reply to: [WPGlobus] WPGlobus Translate Options StatusThank you for your reply with the link to download the update. I was surprised it is now a no-charge subscription, as it was always free.
After installing, there was a request for a key, which I located on the order page and after pasting it was active. The two deprecated PHP warnings are no longer shown.
In the Updates: Active line below the plugin on the WordPress Plugin page I see the key and below: 2 out of 3 activations remaining. Does this mean the update can only be applied to three sites? Or, if on one site and deactivated three times, it can no longer be used?
Forum: Plugins
In reply to: [WPGlobus] WPGlobus Translate Options StatusThank you for the update of WPGlobus from ver. 3.01 to 3.02. I am still getting deprecated PHP warnings from the WPGlobus Translate Options plugin. Another month has passed an it is not yet listed in the WordPress directory. Please make it available on GitHub as you suggested.
Forum: Plugins
In reply to: [Security Header Generator] PHP Warnings@kevp75
Thank you for the reply.
If I want to debug other issues the the wp_debug must be set to true, but with the volume of PHP warnings from the Security Header Generator this is not practical.
The simplest solution is to deactivate the plugin until the PHP is fixed. In the meantime, I will add CSP headers to the .htaccess file, which have worked well in the past.Forum: Plugins
In reply to: [Query Monitor] Doing it WrongMany thanks for your prompt reply. Relating the issues to somebody often triggers more thought on a subject and your reply encouraged me to dig deeper. In my desire to minimise the messages yesterday, I had not included a second message, which was different. it did not refer to scm, but to html-validation. Long ago when so many messages had appeared I had not paid enough attention to all of them. Now they stand out: scm is from the Simple Contact Form plugin and html-validation is from the HTML Validation plug-in. As we say, hiding in plain site! The appending of domain probably threw me at the time.
Hello @titsmaker and @wpkube,
Thanks for the quick tip. It works and will use it for the time being, but I hate to modify plugin files that should be actively maintained and then sometimes overwritten by an update which didn’t fix the issue anyway. I made a plugin that worked suppress this issue with some plugins, but would like to remove it and have this cleared up on several sites.
Its been more than 8 months since I first posted about this. This is the message is the same, but will repeat with more details:Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the scf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. (This message was added in version 6.7.0.).- wp-includes/functions.php:6131
wp_trigger_error()
wp-includes/functions.php:6071_load_textdomain_just_in_time()
wp-includes/l10n.php:1419get_translations_for_domain()
wp-includes/l10n.php:195translate()
wp-includes/l10n.php:340esc_html__()
wp-content/plugins/simple-basic-contact-form/simple-basic-contact-form.php:42
Forum: Plugins
In reply to: [Security Header Generator] PHP WarningsThank you for your prompt reply. I am aware that they are only warnings, but when I said flooding , that was an perhaps an understatement. The debug. file will grow to Megabytes size in a day and this requires the file to be downloaded to open. When I make changes to the site I activate the logging, but this issue makes it very difficult to use debugging and must resort to deactivating your plugin, which is not desirable.
Forum: Plugins
In reply to: [Security Header Generator] PHP WarningsSorry WordPress is version 6.9.
Forum: Plugins
In reply to: [Spotlight Social Feeds - Block, Shortcode, and Widget] Deprecated PHPWasn’t ever fixed!