Recent content by CarpCharacin

Android 12 with Chrome, also present when using Firefox for Android.

So you want to buy that forum? The only public forum owned by XenForo is the XenForo community.

I noticed that, but I put 2.2.5 because I was able to reproduce the bug here.

When I enable bold or italics, type a word, and then disable it, it undoes the bold and italics, and moves the cursor back to where it was before the word was typed. It's extremely frustrating. I'm using Chrome and Gboard on a Pixel 4 with Android 11, latest security patch. The issue is also...

Members are reporting that they've continued to run into the issue, even after the master data rebuild. :(

A forum which I'm not the owner of, and it's running 2.2.3. If it's necessary, I can send the details in a private conversation.

Some members have reported that they cleared the browser cache, yet still continued to encounter the issue.

We're using 7.3, and the issue has continued to occur sporadically.

The server error occurred a few more times when a member who had previously experienced the issue ran into it again. LogicException: Temp hash must be specified if no content is specified. src/XF/Entity/Attachment.php:270 Generated by: [member] Feb 10, 2021 at 10:04 AM Stack trace #0...

No. I've been trying to think of which add-on is likely causing the problem, but it's difficult. Especially since the issue can't be reproduced consistently. That particular error only occurred a few times, yet the issue with attachments remaining unassociated is still happening.

Any idea which one it could be, or at what kind of add-on could cause such a conflict?

Additionally, a member reported that alerts are showing up out-of-order, instead of being listed from newest to oldest. Also, thanks for looking into the issue with AMS the comment alerts!

What's also kind of weird is that other alerts were getting marked as read when the menu was opened shortly after the upgrade to XF 2.2, yet later that day it stopped automatically marking them as read in response to the menu being opened, despite the preferences saying that they should be...

Ugh, what's really troubling is that it can't be consistently reproduced. It appears to have spontaneously resolved, at least for now, and I know that it wasn't exclusive to Safari.

I noticed what appears to be the same error as the one posted above, yet it looks like it was only generated by one user uploading attachments which failed to associate, while the error was not logged when others ran into the same issue. It also now looks like the issue may have occured before...