Matthias Berndt
Forum Replies Created
-
Forum: Plugins
In reply to: [Loco Translate] transfer multiple translation filesIt’s a shame, it could have been possible to have a connection via HTTP request in your plugin that would allow you to read this on one page and enter it on another.
Forum: Plugins
In reply to: [Loco Translate] transfer multiple translation filesIs it possible to have this translation transfer via the WordPress API handled with an automation like n8n?
Unfortunately, I don’t find it practical to always search for all the files for each individual plugin and theme.
Forum: Plugins
In reply to: [Loco Translate] DeepL Translator: Unknown errorThank you for the quick fix.
It’s working really well for me, just like I’ve always been used to.
Unfortunately, I can’t find a way to mark this issue as resolved; I only have the option to disable my email notifications about it.
Forum: Plugins
In reply to: [Loco Translate] DeepL Translator: Unknown errorThank you very much, Tim,
for this explanation, so I already know that it’s probably a browser issue.
As a precaution, I had already sent the following question to DeepL support before your reply and am still waiting for their response:
question to DeepL Support
Can you please assure me that this use of the API in a WordPress installation as a plugin actually complies with your CORS policy, even if it is executed via a browser in a WordPress plugin by an external developer?I would like to commend you for developing this plugin and hope that you will overcome this hurdle soon.
Since you are providing this plugin to us free of charge, you deserve further praise.
What I can’t quite understand, however, is why you didn’t include your own translation API, from the following page, in the API key input.
I don’t access anything. The API key is stored on YOUR server. It’s as safe as the people who have access to your WordPress admin and your database.
That’s what I assumed, too; otherwise, this plugin wouldn’t have been on the market for almost 12 years. 😉
Forum: Plugins
In reply to: [Loco Translate] DeepL Translator: Unknown errorHello Tim W,
what is the problem with the CORS policy?
https://developers.deepl.com/docs/best-practices/cors-requests
We users of Loco Translate do use the API in the browser, but not through direct calls, but rather through the software you provide and therefore not through direct calls, and you certainly do not access the API keys stored there, so they are safe in our plugin installation, right?
Above this page I found the following link to the current guide on developing an API for DeepL.
https://github.com/DeepLcom/deepl-php
I would like to understand the problem in order to possibly help to build a bridge between Loco Translate and DeepL API, because I really like using both Loco Translate when needed and would like to be able to use it for automated translation with Loco Translate because of the manageable translation costs, because with the other translation API providers available I unfortunately see much higher costs for me.
Best regards
MatthiasForum: Plugins
In reply to: [Loco Translate] DeepL Translator: Unknown errorUnfortunately, I hadn’t noticed the pinned posts because I was using the search function and this page didn’t bring me this post.
https://ww.wp.xz.cn/support/topic/deepl-cors-error/
It’s very annoying, though, that this doesn’t seem to work with DeepL anymore.
I’ve opened a ticket with them and just ordered an API plan, because I assumed this might be due to the free version.
With the messages embedded above, I almost thought so, but I just wanted to include them because they could be adjusted in a new version.
Thank you
Hi,
Yes, I know that, but if you have to go through several list pages WP Security> Firewall> 404 Detection and don’t want to block all of them, you can lose track of which one is already in a range on the first pages of the list grabbed and which are not yet on the blacklist.
Or you are forced to go through the entire list to the end before revising the blacklist.
Kind regards
Hi,
if I execute the entries listed under WP Security> Firewall> 404 Detection with the action “Blacklist IP”, the relevant IP address is added to the WP Security> Blacklist and receives in the column “Blocking status from WP Security> Firewall> 404 detection of the entry “blacklisted”.
If I have numerous similar IP addresses with different last or penultimate blocks, but which are otherwise the same, I converted these direct IP addresses to IP address ranges with the star in the WP Security> Blacklist and removed the others relevant IP addresses from this IP address range. (xxx.xxx.xxx.xxx> xxx.xxx.xxx.* or xxx.xxx.*.*)
After this change in WP Security> Blacklist, these relevant entries in WP Security> Firewall> 404 Detection are no longer marked as “blacklisted” in the “Blocked Status” column of WP Security> Firewall> 404 Detection.
Kind regards
Addendum: Occasionally I only use small IP address ranges like (xxx.xxx.xxx.x*) so as not to exclude too many immediately.
- This reply was modified 5 years ago by Matthias Berndt.
- This reply was modified 5 years ago by Matthias Berndt.
Hi,
In the case of IP address (xxx.xxx.xxx.xxx) in the blacklist, “blacklisted” appears in the last column of the “404 detection” and if an IP address range (xxx.xxx.xxx.* or xxx. xxx.*.*) is in the blacklist that contains this specific IP address from the “404 detection”, no “blacklisted” is shown in the last column of the “404 detection”.
Sorry, I can only speak a little English, which is why I use Google’s translater.
Forum: Plugins
In reply to: [wpForo Forum] newly registered users do not appear in the member listAhh Ok thanks, you also take the right user list. 😉
not -> /wp-admin/users.php
but in wpForo -> /wp-admin/admin.php?page=wpforo-members