Manni02

@timwhitlock I’ve installed 2.6.14 released publicly today and the issue is resolved (with WP 6.6.2).

I’ve marked the topic as resolved ??

Thanks for resolving this issue so quickly, and more generally for your great plugin. Keep up the good work!

@timwhitlock ah that’s why both are working now ??

@timwhitlock thanks but the link in your last post gives a “this site can’t be reached” error. EDIT: This one works https://localise.biz/wordpress/plugin/faqs/early-domain-loading. EDIT2: Looks like the same link, both are working again now.

• This reply was modified 4 months ago by Manni02. Reason: provide correct link

@timwhitlock thanks for the explanation and no worries, these things happen all the time with WordPress, we just have to be ready for it ??

By the way, I haven’t upgraded to 6.7 yet, I always wait for a .1 release before upgrading WP itself, to give time to devs to adjust, so this is with 6.6.2.

Definitely no justification for abuse, especially from those using the free version of your excellent plugin. You’ve replied right away, are working actively on resolving the issue, are releasing dev versions for those who can’t use a workaround or revert to the previous version. As far as I’m concerned, you get top marks, I wish all devs on paid for plugins were as reactive as you are ??

I’m still very grateful that you’re offering this plugin to us, and this minor incident will certainly not put me off using it. It’s the first time I experience such an issue with Locotranslate in many years of use, and as long as people are prepared (keep previous versions of all plugins or test every new version in a staging site first) there is no reason for panic.

Strength and good luck!

• This reply was modified 4 months ago by Manni02.
• This reply was modified 4 months ago by Manni02.
• This reply was modified 4 months ago by Manni02. Reason: typos
• This reply was modified 4 months ago by Manni02.
• This reply was modified 4 months ago by Manni02.

@timwhitlock thanks for looking into this, I don’t have any time to debug this at the moment, and other users seem to still have issues (which you suggest might be the the case due to the relative path) so I’ll mark it as resolved when I have the time to test a publicly available version. As indicated in the first post, the issue is resolved by reverting to the previous version, so people know what to do if they need a workaround in the meantime.

This was a minor version and I usually install minor versions on the website without staging testing, given that I save all versions and can easily revert if there is an issue.

• This reply was modified 4 months ago by Manni02.

Thanks for the update Joel. Yes, it doesn’t sound critical, so I’m not worrying ??

First of all, thanks for the plugin, it’s great ??

Any update about this? In the report, it is said: “This is only exploitable when the leave a review notice is present.” What does that mean? I don’t see any option about leaving a review in the settings, so in which situation is the vulnerability exploitable, and is there a way to make sure it doesn’t happen before the updated version is released?

Thanks!

Hi Peter,

Thanks for your quick reply, and sorry to hear they didn’t consult with you first, that’s a real bummer.

Great to know it’s safe to use, I’ll keep it installed.

I love the plugin, it does the job perfectly, so keep up the great work!

Best,

Manni

Thanks a lot, I installed the update and no warnings in 24h, so it seems to be fixed!

I’ll let you know if it creeps back…

Thanks for the update, I had disabled it as I had not heard back. Updated and re-activated now.

Thansk for your work by the way, it’s a great plugin! ??

Have identified that the issue in 3.0 (still present in 3.0.4) is caused by an incompatibility with Redis Cache Pro (on Cloudways, but it could also happen with other hosts, and even with the non pro version of the plugin).

Creating a staging site with Redis disabled allows the staging site to work. Waiting for a fix, but I thought I’d let others know about the workaround in case they experience the same issue.

Done, please let us know when you’ve had a chance to look at it. It looks like it’s thrown by a dependency for one of our plugins. 2.16.0 has no problem dealing with this.

By the way, there was no wp-staging folder in the STAGINGSITE/wp-content/uploads/ so I only sent you the error when launching the site.

• This reply was modified 1 year, 7 months ago by Manni02.

Thanks for your quick reply and your good work ??

Thanks for fixing this so quickly!

Keep up the good work (and have a nice week-end!)

Thanks for the quick reply, looking forward to the patch ??