Creative Themes
Forum Replies Created
-
@wpeditor3869 ok, thank you, let’s continue the discussion there, I am sure we will be able to solve this issue.
@wpeditor3869 no worries, just add a link to this thread in the text section and we will understand that this is related to this question.
@wpeditor3869 please submit a ticket from our website and we will take a closer look at your setup.
Hello @caritatang,
Your situation is different, even if you see the “Function _load_textdomain_just_in_time was called incorrectly” message – this is just a notice and not an error.
Most likely you have some other problems on your site that are not because of our plugin.
It would be great if you could contact us through our support channel from our site so we could discuss more detailed about this and help you.Hello @caritatang,
This will be fixed in the next public update.
In case you need or want to test the beta version – please submit a support ticket from our website and we will give you the build.
Hello @wpeditor3869,
Do you mean that you can’t log in to the site admin dashboard?
If so, could you please check your debug.log file and let us know what errors are you having there?
Forum: Reviews
In reply to: [Blocksy] Needs updateHello @myzenarts,
Everything works fine even with this issue – there are no reasons to worry.
This is just a notification that says that the
mini-cart.phpversion was changed in WooCommerce but this doesn’t affect in any way the compatibility.We will release a new update soon and this notification will disappear.
Again, there are no reasons to worry, this is not a bug or an error, everything works just fine.
Forum: Reviews
In reply to: [Blocksy] Needs updateHello @mariaew,
That’s because WooCommerce released today an update and changed some files.
We will also release an update until the end of the week and will fix this issue.
By the way, there is nothing to worry about, this is not an error, the site will work just fine.
Yes, we plan to release an update until the end of this week.
So, stay tuned 🙂
Hello @prusa,
Yes, we know about this issue, we already have an improvement for this case and will release it in the next public update.
In case you need or want to test the beta version – please submit a support ticket from our website and we will give you the build.
Have a nice day!
@itapress Hello
Thanks a lot for your reply.
Unfortunately, I have to report that this problem is still present in the latest released version (2.0.76).
You are right here, but not fully. Your original report had 2 issues:
- Untranslated message when Blocksy theme is not activated: https://snipboard.io/BlQzVu.jpg
- Untranslated Extensions tab: https://snipboard.io/byO0uf.jpg
I re-tested the whole flow and actually problem #2 is translated fully, without any problems, on a clean WP setup with 2.0.76: https://share.cleanshot.com/y5tr0sWx
But, yes, you are right, problem #1 is not fixed, because our method of exposing translations for the JS files (from the JSON files) relied on a function that is only defined in the Blocksy theme. And because of that, this screen was untranslated in this case. Starting with 2.0.77 this will be fixed.
—
Why we can’t just add your suggested fix?
First of all, I don’t know why you assume that we are generating the “Jed 1.x JSON files” by ourselves. Both in the theme and in the Companion plugin we use translations provided by translate.wordpress.org. It would’ve been a big mistake to not use the tremendous work done by the whole Polyglots team and by all the contributors from all the languages. Big thanks to them for that!
The difference is in the way we expose translations for our JS files. But the underlying translations are the same ones (the same JSON/PHP/MO/PO files from wp-content/languages/plugins,themes directory).
We don’t use
wp_set_script_translations()for exposing translations to JS files because we have a lot of entry points in the JS that are loaded in different situations on different screens (Main WP dashboard/customizer/widgets/gutenberg editor/etc). It’s too big a job to ensure to callwp_set_script_translations()for all those files. Instead, we just load the translations once and expose them via thewp.i18n.setLocaleData()call: https://share.cleanshot.com/zBrsZ3Rt This way, all the JS files can make use of those translations. Same way WP & many other plugin does: https://share.cleanshot.com/qMFBTFhGI hope this makes sense.
Forum: Themes and Templates
In reply to: [Blocksy] Getting Errors on editing page and blocksHi @modestybazarcom,
Could you please open a page where you have this issue and after that the browser inspector -> console, and see if there are any errors?
If you have any errors there, please take a screenshot and attach it here, maybe this way we will be able to better understand what’s happening on your end.
Forum: Themes and Templates
In reply to: [Blocksy] PHP Warning@levismodding as I mentioned earlier – please get in touch with our support on our website and we will provide you a beta version.
- This reply was modified 1 year, 6 months ago by Creative Themes.
Forum: Themes and Templates
In reply to: [Blocksy] PHP Warning@pagrob great, thanks for confirming that everything is fine now 🙂
Forum: Themes and Templates
In reply to: [Blocksy] PHP WarningWith pleasure @pagrob 🙂
