[Resolved] Module forum thread is locked and hidden, critical update not being seen by forum members.

[FireWire]

Not sure who would be the best person to reach out for help on this but there's a critical update for my module, Fluency, and getting the word out is not possible because the thread is locked and hidden from everyone but me. I edited my original post last week (IIRC), which I've done before, and I didn't know that this hid it, which hasn't happened before. This is a bit odd given how old my forum account is and reputation 🤔 

 

 

I'm attempting to let all Fluency module users know that there is a critical update that must be installed for all users that are using DeepL as their translation service or all translation services will fail with an error. This is due to a short-notice breaking change by DeepL stating that they're deprecating their previously documented authentication method on January 15th, 2026. If you're reading this and use Fluency, please update your module installs to version 2.2.0 which now available via a ProcessWire admin module upgrade, the modules directory, Github, and Composer. I pushed the update as soon as I could to give ProcessWire devs as much time as possible to update their installs and those of their clients.

Thanks to whomever sees and can/does unlock the thread!

[ryan]

@FireWire I see it says Resolved now, but did you find out how it happened? I looked at the moderation log for the topic and there's no entry where anyone hid or locked the topic. Though I do see an entry where Netcarver fixed the issue. So I'm wondering what broke it in the first place? Maybe a side effect from the recent forum upgrade is the only thing I can guess so far. 

[FireWire]

@ryan Saw nothing on my side except that it was fixed (thanks to Netcarver). I received notification saying "Your post was approved". I'll have to go with your thought on the forum upgrade. Only tidied up some info on that original module post which I don't do very often. I think it happened once a while ago for the same reason, but it was approved quickly so I didn't think anything of it.