Forum Replies Created
WOW! Finally =) ! That’s great!
I’m still with WP 6.7 due to your plugin =)
Hello,
do you have some news? =)
Smash Balloon Joel answered today. Maybe you can write him to understand how they solved the issue.
“…
Thank you for following up here. The issue has been identified, resolved and we are in the final stages of testing the next version of the plugin. This update will shortly be available on wordpress.org. That being said, I have created a version with the fix that can be used by users here experiencing the _load_textdomain_just_in_time error. This link will be active for a week as the plugin update will be sent out in that time: https://a.supportally.com/f/3IeXbV.
Please test installing this version and if you have any further issues about this, please let us know. The plugin version is the same as the current one, so you will be able to update when the next version is released, including the same fix.
Many thanks!
…”
Thank you!
But, as we understand, your plug-in has some problem when used with WPML and the new WP 6.7.
I don’t want to change it, because i like it =)
.
Please, find the bug!
.
By the way, I disabled again your plug-in. In this way you are able to enter my staging website!
Hi, sorry, I forgot to disabled the problematic plug-ins.
Now you have access to my staging website =)
Also, Lars
PHP error in WP 6.7: Notice: Function _load_textdomain_just_in_time was called..
has my same problem.
So, it’s clear that the problem is your plugin.
I’m sorry, but this is not true.
Your plug-in has a bug when used with WPML and WP 6.7
When WP 6.7 was released, I had a lot of PHP error exacly like you!
All programmer fixed the problem, except you and “Feed Instagram” from Smash Balloon.
.
If you look at my staging website, I activated Feed Instagram.
And, as usual, I have the same exact problem like you.
.
They told me they found the problem and they will fix it.
https://wordpress.org/support/topic/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called-5/
.
I think you have to contact come other programmers to ask how they fixed the problem.
.
This problem occurs when you have WPML installed, and you have a NON ENGLISH LANGUAGE set as a primary language.
.
Try to create a dummy, test website, install WPML and set a Indian language as main language.
Then translate some pages and… DONE! PHP error occurs.
HEllo Tahasin,
done =) I disabled Download manager. Now you are able to enter =)
Hello
the new v3.3.05 didn’t solve the PHP error =)
Hello Tahasin, any news? Can you fix the bug in your plugin? =)
I did it, and your plug-in is not compatible with WPML Multilingual CMS 4.6.15.
My staging website is in Italian. I only enabled OceanWP theme, Download Manager v3.3.04, and WPML Multilingual CMS 4.6.15.
https://www.staging25.francesc0legrenzi.c0m
Replace 0 with o.
If you switch my website to ENG, the Download Manager PHP error disappears.
If I turn off WPML, the Download Manager PHP error disappears.
So, you didn’t fixed your bug.
Can you help me?
Thank you.
Hello Tahasin,
do you have some news? I’m still running WP 6.6.2 due to this problem with your plugin.
Thank you! =)
Ok, I did some more deep test!
My website uses OceanWP 4.0.3 as theme and WPML Multilingual CMS v4.6.14 as translator plugin. All is update to today, November 27.
(*) With WPML Multilingual CMS v4.6.14 ON, Download Manager v3.3.03 gives me always these PHP errors (ERROR 01 and ERROR 02) in the back end only. While ERROR 01 appears only in the front-end.
(*) With WPML Multilingual CMS v4.6.14 OFF, no error at all.
——————–
ERROR 01
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the download-manager 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. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/customer/www/xxx.com/public_html/wp-includes/functions.php on line 6114
——————–
ERROR 02
Warning: Cannot modify header information – headers already sent by (output started at /home/customer/www/staging25.francescolegrenzi.com/public_html/wp-includes/functions.php:6114) in /home/customer/www/xxx.com/public_html/wp-admin/includes/misc.php on line 1438
——————–
If I disable Download Manager v3.3.03, no error appears in both back and front end.
So, something is wrong in Download Manager v3.3.03 with WPML.
Here the official WPML thread
PHP error WP 6.7: Notice: Function _load_textdomain_just_in_time was called
Can you fix it?
————————–
Thank you =)
If you need “help”, I’m here.
Francesco from Italy
Hello,
after the new update, I still have the same problem
WP 4.7.1
DM: 3.3.03
https://www.stagingXX.francesc0legrenzi.c0m
replace XX with 25, and francesc0legrenzi.c0m “0” with “o”.
Can you help me?
Hello Tahasin. That’s great! Thank you!
Hello,
as you know, WP 6.7 created a lot of problems to everybody.
did you find the bug in your plugin? =)
Sure!
https://www.stagingXX.francesc0legrenzi.c0m
replace XX with 25, and francesc0legrenzi.c0m “0” with “o”
Why do you need my wp-login credentials?
Another update:
I see websites not multi-language with the same PHP error:
And multi-language websites with the PHP error in both languages.
So, it’s not WPML problem, but the problem is because each plugin.
I hope I help you!
PS: this error is crazy! Many websites broken in these last days, everywhere!
Ok, WPML team answered me:
“Thank you for contacting WPML support.
Our team is aware of these notifications; however, we could not determine if they are directly related to the WPML plugin.
We recommend waiting for each plugin to address this notification. In the meantime, you can set the debug mode to false to prevent these notifications from being bothersome.”
From what I see, the bug must be fixed by each plugin team.
Hello Tahasin, I’m sorry, but it’s not as WPML problem.
WooCommerce and Yoast teams are already working for the fix for WordPress 6.7.
Look at these threads:
https://wordpress.org/support/topic/bug-with-the-latest-version-of-wp-6-7/#post-18133599
So, when can you fix your plugin? =)