Recent content by tlamprecht

Oh, one thing that might be relevant here too, we configured the spam cleaner to move threads into a hidden forum to still be able to restore threads while ordinary moderator users not getting their forum list views crammed with the soft-deleted spam messages, which is really annoying for all...

We recently got a new pattern of spammers that causes some annoying fallout when trying to spam clean them. They will register and then continuously post spam messages, while these land all in the approval queue (good!) it gets relatively big, well, not really that big, just close to triple...

Any update for this bug? As this is quite annoying for any community dealing with lots of log/config/... output that tends to be wrapped in these tags. FWIW, we updated to 2.3.5 yesterday, no changes in this regard. I can understand that such editors are complex, so a very quick fix might not...

We got a few similar server error logged over the last days: ErrorException: Passkey registration failed: MySQL query error [1406]: Data too long for column 'credential_id' at row 1 src/XF/Error.php:82 Stack trace #0 src/XF.php(266): XF\Error->logError('Passkey registr...', false) #1...

I've seen a few similar posts, not sure how related this is with them though. And FWIW, I never saw this error in the last decade running XenForo, but now got it once a day after finally upgrading from v2.2 to v2.3.4. UPDATE xf_user SET message_count =...

Yes, but IMO this is in the area of being technically correct, but still worse UX than it could be. As at least I definitively don't derive such a bit subtle semantics hints from which subgroup some option is included in, especially if it talks about "submission" and the whole thing is split...

Thanks for your answer! Well the label and the description of that option are rather confusing then, as that reads: is clearly talking about submission, not just about doing so when checking against the SFS DB. And yeah, SFS is definitively the actual place that would need to improve. For...

Hello, We got a report from a new forum user that their freshly created email alias (using the proton email provider) used to create an account on our forum quite quickly got spam and phishing messages afterwards. Something that didn't happen with other such aliases used by them. I then...

ah thx, I searched for "icode" in this forum but did not find that thread. But I don't see that part adressed there:

Hi, ran into this a few times since a while already, but only got finally annoyed enough for opening a report today. Since v2.2.12 selecting a few words, then pressing the Inline code button adds disruptive new lines we need to manually remove again, e.g.: let's show with a screenshot, first...

I fixed it manually anyway, like I had to do when the devs messed up earlier (thus this thread which I provided the workaround for until it got actually fixed). Sure, I can hack around manually, or the XF devs just can adhere to some proper software release hygiene, I mean we pay for that after...

They need to release an updated one with a higher version number then so that XF can pull that in, you cannot just update an already released ZIP - what's out is out.

Me too, I just re-applied my fix: https://xenforo.com/community/threads/e_warning-attempt-to-read-property-result_count-on-null.207377/#post-1583052 IOW. edit src/XF/Pub/Controller/Search.php and insert: if (!is_object($search)) { return $this->message(\XF::phrase('no_results_found')); }...

Please rename the options in the email server/credential setup for automatic bounce handling to less confusing terms, namely: Current TLS should get renamed to STARTTLS, as STARTTLS is a) opportunistic encryption and b) not necessarily using TLS, if encrypted. Current SSL should get renamed to...

Not if the fix is in another file, there maybe just some outside assumptions that got wrong with the last update. The workaround here that came from myself initially is pretty safe though and worked OK since Thursday, also, it'd be easy to remove even if a fix gets out that doesn't touch this...