Laurent MILLET

Another version for this week ??
Because the i18n problem is always here !!!
See u next week ?
The convenience isn’t for me but for the community.
The more you wait the more translations wait.
I know some users who change for other Gutenberg blocks plugin because the language fr usage and explanations

• This reply was modified 5 months, 1 week ago by Laurent MILLET. Reason: to add more informations

Sorry, but it seems that 2 new versions has been released but the problem persists. The volume of strings to be translated has increased significantly since the problem first appeared, which could discourage contributors from translating them.

In the readme.txt file of your plugin you must put the name of your plugin in the form: ==Plugin Name == .
This would give you == Tags groups == .
If you want to give more details you have the description field which will help you as well as the keywords.
All this will make you easier to find on the repo.
You can change the readme without changing the version of your extension.
Thank You
more details on :https://developer.www.ads-software.com/plugins/wordpress-org/how-your-readme-txt-works/#example-readme

Hi,
if you have access to the extension files, go to public/cf7-material-design-custom-style.php and try removing the 3rd part of the if .
|| $this->options['use_custom_styles']
Then it seems to work fine.
But be careful, the dotorg and premium versions of the plugin no longer exist and are no longer maintained. I suggest you try to find another plugin or use CSS.

Hello again,
I am Global PTE in France and I would like to suggest you to try to follow the best practices which say to put in the tags directory the versions so that they appear on translate in the stable part of translate.
This simplifies our task since we focus on the version in production. So the chance for your users to have an up-to-date translation increases.
In your current setup, strings validated in dev go to stable (and thus to end users) if and only if they exist in stable. If there is a change in the dev that does not match the stable it stays in the dev.
If you modify it again we will translate it again but the previous work is taken for nothing.
Moreover I remind you that the Language Pack is generated at 90% of the stable. We have no visibility on it if it doesn’t appear.
I think it would not take you hours to add this into your process and would save us translation (for all locales) time, efficiency and work quality.
Thank you

Ok but it seems you have a problem on the i18n, (no text domain). If you want the extension to be translated by the community, please follow this doc :
https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#loading-text-domain

Because they rely only on nostalgia, not on advancement…Think about it. ??

The method is indicated in the following link:
https://developer.www.ads-software.com/block-editor/developers/internationalization/
As you can see, you just have to put in i18n dependency in your plugin then put the js as in the example
Finally tell WP that the Js contains translations. The last step is to generate the .pot files via wp-cli for example that the WordPress translation system will make available to the contributors.
Congratulations for the PHP part which is great
As PTE on this extension, as soon as it is compliant I will translate and publish it.
Thank you for your work

Just to know, do you have plans to make these changes (even if not immediately)? If not, there is no reason to translate the Readme.

done !

amazing !!

thank you for your answer and your work

I think something ?? not someone.
But I’m really interested in the possibility of for example:
– checked the files of the libraries.
– Reinstall the libraries individually.
I have wordfence installed on 2 site (one is the clone of the other) and one works but the other does not.
Many thanks

excuse me for the delay. I control the list of files and actually they are not there. After a complete reinstallation they reappeared in the right place. But I’m afraid it will happen again.
They were there in their place right before the passage in WP 5.3 without I can say that these 2 events are related. What to do like other tests?
Thank you

Tank u,
i see in console that there’s a lot of 404 error in h5p libraries.
At this moment, the only solution is :
– remove the plugin
– reinstall the plugin
– reload activities
I don’t know if there’s a solution to repair libraries or reload them.