[bug] Forum Breakage after Board Maint. and "Click to edit" errors within posts
#1
There seems to be something going on with some of the threads in Casa it seems-- as of about an hour ago. A lot of posts have changed to say 'click to edit' even though I can see that their coding is still there in the 'find all posts' section -- link -- When I edit the afflicted posts, the coding and post actually written is still there, it's just not showing up on board, see here.

it's not just me that's seeing this, other Cavaliers are too. A glance showed that it didn't seem to be happening in the other packs, but I didn't look extensively but it did affect non-casa characters posting in the casa forum too. I've included a few screenshots.

Link, Link, Link

Edit: Have found evidence of it outside of Casa too -- Link
  Reply
#2
I can see the messed up posts too. Cache clear and hard reload does not fix the issue; issue is on both Desktop and Mobile, Chrome and Mozilla browsers/apps.

EDIT: See my secondary post below (unless you just wanna see our trial-error finding process xD)




While editing this post too, I noticed that the "Quick Edit" didn't always actually save/submit? So, not sure if the above might be tied to this issue as well? :O



I've also been getting one of these two errors (1, 2) consistently for the past week (I thought it was just me, but, now I'm not sure?). The page will load after a few seconds if I'm given Error #1. I have to manually refresh the page to fix Error #2. It's never the same thread, never the same forum. It's completely random when it shows and how consistently it shows that day. Sometimes I'll get it 3-4 times a day. Other times, I'll have it show up once. Time of day is always different too when this pops up. The errors only ever show up on my Desktop too?
  Reply
#3
Found more posts here:
  • OOC Accounts
  • IC Accounts
    • Ash Del Mar: post (In OOC area)

In the case of OOC Accounts, posts that have image or media attachments seem to be disproportionately affected vs. text-only posts? (Perhaps there's something linked towards image hosts?)
  Reply
#4
I know for me personally when I posted on Lucian this morning with his usual code it did the 'Click here to edit'. When I removed the image part of the code, the words reappeared. I know a good portion of us use images in our code.
[Image: SoSuWriMo2022_winner.jpg]
  Reply
#5
It's definitely linked to images.

Upon posting in the Testing thread, I made the following posts:
Post One, and Post Two.

Only difference between them was the removal of the image in the code.

Edit: Noting the break also appears on profiles of IC Accounts, all of my code that has an image present has erased the visibility of the entire field, seen:
Nazario del Bosque, Esperanza Tejada, Briarblack, Monet Firestone, Owen Winsor, Lothric Coara, Cassidy Sinclaire, Fallow

Edit x 2, electric boogaloo:
Can verify with Songbird that it is the small image code!
Post Three in the Testing Thread kept the image tag, but removed the (smimg) tags.
  Reply
#6
I think the smimg code is one of the main causes (though, maybe it's just one thing in a larger issue). I just tried to preview the post I made above with a smimg code in it, and it just gave me a blank preview screen. When I plugged a regular BBCode img code, it worked fine.

HOWEVER, the above does not hold true for the following areas/issues with the same "Click to edit" problem:

  • No posts made within the board-wide News sub-forum are effected by the presence of the smimg code (ex. 1, 2).

  • Mandi's Rafaela post examples that I highlighted in my first post. Mandi did not use smimg code in the post that was effected by the "Click to edit"
    Songbird Wrote:Most of Mandi's posts appear fine, except for this one, for example, despite having the same IP address as those made in this thread, where the posts are unaffected.
    The only way I was able to fix her post was to remove the simple-ized quotes within the hovertext code. I used hovertext code in a recent Kamari post that didn't break, however, it looks like the stylized quotes that carried over from when I copy+pasted from Google aren't treated the same as those in Mandi's effected post.



I do think that the "Quick Edit" option has an error with it too though, as seen by this error that I keep sometimes getting when I try to look at the effected posts via "Quick Edit", or, even editing here now on these posts of mine @___@ It's not super consistent, and easily fixable by canceling and going into the Full Edit option, but, it's showing up none the less.



And I have no idea how to explain the reasoning behind those page loading errors that I mentioned above that I keep getting x,D



Another thing to add that might be related to that recent board maintenance update: my pink "Unread" leaf icons no longer change to the greyed out "Read" icons now on the forum's main/"front" page despite all threads within the sub-forum being read? The only way I've gotten the "unread" icons to clear is to "Mark All Forums Read" or to click on the actual icon indicator specifically? o___O
  Reply
#7
Don't know if this is related, but it looks like the threads that Mel started on Whisper Eternity's account aren't counting views. It's stuck on zero even though it's been hours and I know that I've looked at them multiple times. Here's a screenshot so you can see what it looks like for me, in case it looks different for you.

I also don't think I'm getting email notifications when someone replies to a thread I've subscribed to anymore. I checked my settings and they haven't been reset or anything, but I haven't gotten any notifications since before the board maintenance.
  Reply
#8
  • [smimg] issue should be resolved.
  • Email notification issue should be resolved.
  • [hovertext] is not intended to accept plain double quotes. Because this bbcode translates everything between "[hovertext=" and "]" into <span title="text"> superfluous quotes make the resulting HTML into <span title=""text""> which will not parse correctly. One of the updates basically made the parser more strict, so if this worked before, it was unintentional. (The parser becoming more strict was also why smimg was failing -- the HTML translation we set previously did not "close" the img tag with the forward slash before the closing >.)
  • I could not replicate thread view issue. Viewing threads from accounts and as a guest correctly increment view counts for me.
  • I could not replicate "mark as read" error. Clicking the leaf icons on forums correctly marks the forum as read for me.

I'll look into additional errors later this afternoon, but let me know if the above fixes resolved any of them.

(As a side note, I have Discord blocked for large portions of the day to avoid distraction. An unfortunate side effect of this is not being able to see images uploaded to Discord, which is why I'll look into screenshotted errors later.)
it was me. i broke it.
commission info | instagram
  Reply
#9
(28 May 2022, 12:34 PM)Songbird Wrote: I've also been getting one of these two errors (1, 2) consistently for the past week (I thought it was just me, but, now I'm not sure?). The page will load after a few seconds if I'm given Error #1. I have to manually refresh the page to fix Error #2. It's never the same thread, never the same forum. It's completely random when it shows and how consistently it shows that day. Sometimes I'll get it 3-4 times a day. Other times, I'll have it show up once. Time of day is always different too when this pops up. The errors only ever show up on my Desktop too?
If they've been happening for a week, they pre-date the maintenance update (which occurred early morning ET May 28th), however, they may be related to DNS issues with our host last week.

Let me know if they keep happening though.

(28 May 2022, 01:45 PM)Songbird Wrote: I do think that the "Quick Edit" option has an error with it too though, as seen by this error that I keep sometimes getting when I try to look at the effected posts via "Quick Edit", or, even editing here now on these posts of mine @___@ It's not super consistent, and easily fixable by canceling and going into the Full Edit option, but, it's showing up none the less.

Wasn't able to replicate this, but if you notice any pattern wrt to the types of posts this seems to affect, please let me know.
it was me. i broke it.
commission info | instagram
  Reply
#10
From the looks of it, the unread issue is fixed now? Along with the view count issue that Juni had too? :O

When I got home this afternoon, both look to be working like they used to pre-maintenance update (they were both still broke yesterday, and the view count was still broken when I checked before work this morning). So, they might have somehow been tied to the other issues that were fixed somehow?



(28 May 2022, 12:34 PM)Songbird Wrote: I've also been getting one of these two errors (1, 2) consistently for the past week (I thought it was just me, but, now I'm not sure?). The page will load after a few seconds if I'm given Error #1. I have to manually refresh the page to fix Error #2. It's never the same thread, never the same forum. It's completely random when it shows and how consistently it shows that day. Sometimes I'll get it 3-4 times a day. Other times, I'll have it show up once. Time of day is always different too when this pops up. The errors only ever show up on my Desktop too?
(31 May 2022, 03:46 PM)Kiri Wrote: If they've been happening for a week, they pre-date the maintenance update (which occurred early morning ET May 28th), however, they may be related to DNS issues with our host last week.

Let me know if they keep happening though.

I'm still getting them as of this afternoon, and it's spread to the Wiki now too of giving a similar error message Dx At this point I'm not sure if it's just something with my internet provider or something though if nobody else is seeing the error message at all?

EDIT: Also notating that now it's appearing in announcement boxes too (Ex. NC's announcement box that I caught messing up) @___@ This one did not fix itself until I manually refreshed the page.
  Reply
#11
(31 May 2022, 06:32 PM)Songbird Wrote: From the looks of it, the unread issue is fixed now?  Along with the view count issue that Juni had too?  :O 

When I got home this afternoon, both look to be working like they used to pre-maintenance update (they were both still broke yesterday, and the view count was still broken when I checked before work this morning).  So, they might have somehow been tied to the other issues that were fixed somehow?



(28 May 2022, 12:34 PM)Songbird Wrote:
I've also been getting one of these two errors (1, 2) consistently for the past week (I thought it was just me, but, now I'm not sure?).  The page will load after a few seconds if I'm given Error #1.  I have to manually refresh the page to fix Error #2.  It's never the same thread, never the same forum.  It's completely random when it shows and how consistently it shows that day.  Sometimes I'll get it 3-4 times a day.  Other times, I'll have it show up once.  Time of day is always different too when this pops up.  The errors only ever show up on my Desktop too?
(31 May 2022, 03:46 PM)Kiri Wrote: If they've been happening for a week, they pre-date the maintenance update (which occurred early morning ET May 28th), however, they may be related to DNS issues with our host last week.

Let me know if they keep happening though.

I'm still getting them as of this afternoon, and it's spread to the Wiki now too of giving a similar error message Dx  At this point I'm not sure if it's just something with my internet provider or something though if nobody else is seeing the error message at all?

You're not the only one seeing the errors. I am getting them extremely sporadically too. But they've been so quick to auto-refresh and resolve that I haven't thought to say anything or look for any bug fix for them until now, but seeing someone else seems to be having a similar problem I figured I'd speak up!

EDIT: I will try to catch a screenshot of an instance of one of them happening if I can!
  Reply
#12
Quick update: I made [hovertext] compatible with quotes, so [hovertext="stuff"] will work now instead of erroring out in a very unintuitive manner. Without the quotes also still works.

Re: the remaining error. This definitely isn't a forum software thing and screenshots probably won't help much unless they contain different errors. I still think it may be related to ongoing host issues, even though the maintenance they're doing seems unrelated. All the systems I have control over are green, so I think this is an error we'll just have to wait out.

If the error changes or if it continues and there isn't a corresponding "active incident" on our host status page, let me know and I'll escalate to support. :V
it was me. i broke it.
commission info | instagram
  Reply
#13
Seeing another issue with the Click to Edit posts with 'SA posts, I'm sure it's been seen already but I figured I'd go ahead and note that it is ongoing~
Post example
I DON'T WANT TO BE A PROUD MAN, JUST WANT TO BE A MAN
a little less like my father, and more like my dad
  Reply
#14
Yeah, I fixed it lol. New parser is strict indeed. u_u
it was me. i broke it.
commission info | instagram
  Reply
#15
(28 May 2022, 12:34 PM)Songbird Wrote: I've also been getting one of these two errors (1, 2) consistently for the past week (I thought it was just me, but, now I'm not sure?). The page will load after a few seconds if I'm given Error #1. I have to manually refresh the page to fix Error #2. It's never the same thread, never the same forum. It's completely random when it shows and how consistently it shows that day. Sometimes I'll get it 3-4 times a day. Other times, I'll have it show up once. Time of day is always different too when this pops up. The errors only ever show up on my Desktop too?
(31 May 2022, 03:46 PM)Kiri Wrote: If they've been happening for a week, they pre-date the maintenance update (which occurred early morning ET May 28th), however, they may be related to DNS issues with our host last week.

Let me know if they keep happening though.
(31 May 2022, 06:32 PM)Songbird Wrote: I'm still getting them as of this afternoon, and it's spread to the Wiki now too of giving a similar error message Dx At this point I'm not sure if it's just something with my internet provider or something though if nobody else is seeing the error message at all?

EDIT: Also notating that now it's appearing in announcement boxes too (Ex. NC's announcement box that I caught messing up) @___@ This one did not fix itself until I manually refreshed the page.
(1 June 2022, 01:15 PM)Kiri Wrote: Re: the remaining error. This definitely isn't a forum software thing and screenshots probably won't help much unless they contain different errors. I still think it may be related to ongoing host issues, even though the maintenance they're doing seems unrelated. All the systems I have control over are green, so I think this is an error we'll just have to wait out.

If the error changes or if it continues and there isn't a corresponding "active incident" on our host status page, let me know and I'll escalate to support. :V


I'm still getting this error (now on mobile, even while roaming), and the link you gave has shown a green "Operational" the whole time Dx
  Reply
#16
I've also been getting this error frequently, mostly on my phone
  Reply
#17
I talked to our host about the ERR_FAILED errors. Unfortunately, this is a difficult to diagnose issue. Support suggested it might be an individual firewall issue, but I doubt this since it's intermittent and usually clears on refresh. (You can check your firewalls anyway and report back if you want though, I guess?)

The other suggestion was to run a trace route to see if your connection is reaching our host servers correctly and then to contact support with that info ASAP to try and catch the issue, but this is really hard to do, obviously.

The server to run a trace route on is ns1.dreamhost.com. You can also run it for ns2.dreamhost.com and ns3.dreamhost.com for more info.

You can run a trace route manually on a Windows machine via Start>CMD>
Code:
tracert ns1.dreamhost.com

Not sure how to do it on other machines/mobile, but I'm sure you can look it up.

The results of a trace route should look something like:
Code:
Tracing route to ns1.dreamhost.com [162.159.26.14]
over a maximum of 30 hops:

  1    1 ms    11 ms    <1 ms  192.168.0.1
  2    16 ms    21 ms    19 ms  your-isp-address.comcast.net [192.168.0.1]
  3    16 ms    17 ms    21 ms  your-isp-address.comcast.net [192.168.0.1]
  4    *        *        *    Request timed out.
  5    58 ms    48 ms    40 ms  4.69.219.210
  6    37 ms    26 ms    17 ms  4.30.140.62
  7    30 ms    29 ms    29 ms  ns1.dreamhost.com [162.159.26.14]

You can PM me or post the resulting information (the private info it may contain is your IP address) along with the exact time it ran (pls include timezone) and I'll try to see if support can do anything with the info.
it was me. i broke it.
commission info | instagram
  Reply
#18
Still getting this issue despite all the cache flush + changes made to settings by our Host. I'm not sure about other players since I seem to be the only one saying that I have this isssue, but, for me, it's to the point that I can't even enjoy the website (especially on my tablet) because I keep running into the error on the forum / wiki. Like, it's to the point that I hate getting on 'Souls anymore Dx

While the error happens while browsing, it seems to happen more often when I'm previewing or submitting things, I've noticed? The Quick Edit button option is also not saving my edits about 50% of the time again, too. I'll hit "Save," and it basically just treats it like I hit "Cancel," and everything I typed is gone. Full Edit doesn't have that issue though.

EDIT: I searched on the great Googler to see if I could maybe do something different on my end and stumbled across this website that mentions other individuals with DreamHost coming across the same issue recently (as in, pretty much within the same time period as it was reported here)? :O According to one of the replies, they were told that it's related to a "bug in the latest version of Chromium, which affects chromium based browsers (Chrome, Edge, etc)", and, if you use another browser like Firefox, you won't see the error issue? That's a lie, because I just ran into an equivilent issue on my Firefox app on my tablet DX (Screenshot)
  Reply


Forum Jump: