Angelika Reisiger
Forum Replies Created
-
Forum: Reviews
In reply to: [Gutenberg] Naysayers gon’ naysaynay no none.
Not the language files are contributed by community members. The community members contribute translations.
As said, GlotPress works so: When a plugin is translated to 90% GlotPress/translate.w.org rolls the language file out to the backend of the users. These files are located then underwp-content/languages/plugins/
. But these files also are complete, says, they include 90% translation and 10% untranslated strings.The damaged file I mentioned is missing the untranslated strings.
The problem was not caused by the community. The plugin code determines how and which language files are integrated. As I understand it, however, the bug is being searched for in the community, which makes it very easy for the plugin developer and so the bug will remain permanent.
Whatever, since I don’t use WooCommerce and so no add-ons, this error does not affect me in any way. And so I couldn’t care less. I just wanted to be helpful and inform the plugin developer about it. Bye.
As an addition to my previous post above: I forgot to mention, that the damaged file is labeled with “100% translated” but it is only a quarter of the original translation file (120 KB)
This is never the normal behavior or process of GlotPress/translate.w.org. Something is wrong in your plugin.You can see the content of this file there
https://pastebin.com/aVHz4ZQ4Thank you for your feedback. This language files are managed by Glotpress
That is wrong. Language files from translate.w.org are only rolled out, when they are translated at least to 90 %. And the english strings would be submitted completely. But in the damaged file (I mentioned above) are only a quarter of the english strings.
More information about how you can contribute can be found at https://www.paidmembershipspro.com/paid-memberships-pro-in-your-language/#h-how-to-use-glotpress
I have been GTE for German language for years, I know the processes.
however this will allow you to use your own translations and let them take preference.
No, how could you translate missing english strings?
Apart from Loco Translate, let’s forget that <– is not installed.
If I install the Paid Memberships Pro plugin and have the website language set to German formal, then subsequently updates for the language are offered to install .Before the update, there was only a (German [formal]) language file in
wp-content/plugins/paid-memberships-pro/languages/paid-memberships-pro-de_DE_formal.po
with 3088 strings (over 1 MB)After the (german) language update there is an additional (and new) german language file in
wp-content/languages/plugins/paid-memberships-pro-de_DE_formal.po
with only 809 strings. (much smaller than 1 MB).The new file is damaged or whatever.
Forum: Reviews
In reply to: [Gutenberg] Very bad experience for responsive layout5 stars?
Forum: Reviews
In reply to: [Gutenberg] Frustration Maximum!I can completely empathize with you. You are not forced to use the block editor (Gutenberg) in forums, here is a how-to (in German language), use Deepl for translation if necessary.
Forum: Reviews
In reply to: [Gutenberg] The worst change made to WordPressSadly I have to give it 1 star.
No, you did not. You gave it 5 stars ??
Forum: Plugins
In reply to: [Classic Editor] Doesn’t Allow Editing with PHP 8+@einstein101
I can assure you that the plugin Classic Editor works well with PHP 8.x. It is the first plugin that I install on all websites (own and for clients).Disable all plugins (while running PHP 8.x) clear cache and enable plugin by plugin and test if the error occurs.
Or: Enable debug in wp-config.php and read where the error is coming from (and don’t forget to set it back to
false
).
https://developer.www.ads-software.com/apis/wp-config-php/#wp-debugThank you.
Thank you very much and have a nice day!
Forum: Reviews
In reply to: [Classic Editor] Not compatible with WP6It works fine with WordPress 6.0 and 6.1.
New version is available but the problem still exists ??
Hi,
talking with our developers, this is a time consuming task to us.
We suggest following the guidelines provided by iubenda:
https://www.iubenda.com/en/help/20625-google-fonts-gdpr-how-to-be-compliant
This is extremely disappointing. Tell me, what you see, when you block fonts? How will your website look, if it is displayed with default fonts?
To follow the GDPR Guidelines you must get the consent of the visitor = Opt-in, then show the font. If the user only agree to essential cookies, then the website will look ugly.
Your Devs say “it is time consuming”? I recommend https://google-webfonts-helper.herokuapp.com/fonts this does all the work for you. Only upload and integrate the code.
Unbelievable