Broken cut tags
I didn't post about this at the time because I figured I was the only person who was laggard enough to have the problem, but apparently there are more of us than I thought, and not all of us were annoyed enough to figure out how to fix it?
So, if cut tags on your journal have been broken since the summer, so that they no longer open in the page and you have to open in a new page, it is probably because you are still using a Core1 journal style you imported from LJ. When they made some updates to DW backend code recently, they accidentally broke javascript for Core1, which for most people mostly means the magic cut tags. (It probably also messes with expanding comment threads if you read comment pages in your style? I use site scheme there so idk.)
This is not something I will blame DW for, because Core1 styles were obsolete ten years ago when DW was founded and mostly have never met basic web accessibility standards, and it is frankly impressive they still support them at all. (Why are you still using Core1 on your journal, you deadbeat*?? Has "update journal style" really been on your todo list for MORE THAN TEN YEARS???)
Anyway, they are hopefully going to fix it in the next code push eventually.
Meanwhile, there are two options: you can go to Change Style and pick a style that was coded this millennium. This fixes it for everyone, and also means you are using a style that follows at least some web standards.
Or you can do what I did, stick stubbornly to your horrible ancient style that you've been using more than half your life, and go to the beta page and select "Turn ON beta testing" for "Temporarily revert updated journal page components" (I know it's counterintuitive to turn ON beta testing in order to turn OFF new features, but it's a workaround.) This will only fix it for you while you are logged in - other visitors to your journal in your style will still have broken cut tags. Then add
dw_maintenance to your reading list, so you'll know when it's fixed and you can turn it back off.
*also why is your style still Homestuck themed, what is wrong with you
So, if cut tags on your journal have been broken since the summer, so that they no longer open in the page and you have to open in a new page, it is probably because you are still using a Core1 journal style you imported from LJ. When they made some updates to DW backend code recently, they accidentally broke javascript for Core1, which for most people mostly means the magic cut tags. (It probably also messes with expanding comment threads if you read comment pages in your style? I use site scheme there so idk.)
This is not something I will blame DW for, because Core1 styles were obsolete ten years ago when DW was founded and mostly have never met basic web accessibility standards, and it is frankly impressive they still support them at all. (Why are you still using Core1 on your journal, you deadbeat*?? Has "update journal style" really been on your todo list for MORE THAN TEN YEARS???)
Anyway, they are hopefully going to fix it in the next code push eventually.
Meanwhile, there are two options: you can go to Change Style and pick a style that was coded this millennium. This fixes it for everyone, and also means you are using a style that follows at least some web standards.
Or you can do what I did, stick stubbornly to your horrible ancient style that you've been using more than half your life, and go to the beta page and select "Turn ON beta testing" for "Temporarily revert updated journal page components" (I know it's counterintuitive to turn ON beta testing in order to turn OFF new features, but it's a workaround.) This will only fix it for you while you are logged in - other visitors to your journal in your style will still have broken cut tags. Then add
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
*also why is your style still Homestuck themed, what is wrong with you
Thanks for the PSA
I admire your commitment to maintaining a decade-long distance from the current moment, which is eminently avoidable.
Re: Thanks for the PSA
no subject
(Anonymous) 2020-10-06 06:55 pm (UTC)(link)no subject
no subject
no subject
Are you sure your style isn't core1? It looks like you're using a variation of Punquin Elegant, same as me. Punquin is core1. Remember there was S1, and then S2, and then S2 split into Core1 and Core2, and then the DW-native system is Stylish. Punquin is S2 but Core1. I was confused by this as well when trying to track down the problem.
no subject
My style is Punqin Elegant, yes, but someone updated it for core2 at one point. I just checked my layers, and I even still have a core1 Punqin Elegant layer in there, but the one I'm using says "Child of layer 550: Dreamwidth S2 Core, v2".
no subject
That's weird that your style is Core2 but it's still broken. I would assume if it was generally broken in Core2 a lot more people would have been upset. Maybe the update carried something over that is also carrying over the brokenness?
no subject
Yeah, it must have. I wish I knew how to figure out what it is. *sighs*
no subject
I didn't look at it too closely because elsethread it seemed like they had found a different cause in S1, but maybe that will still fix it in S2.
no subject
no subject
Go to https://www.dreamwidth.org/customize/advanced/layers , edit your active layer, click on page::print in the sidebar, and then try replacing the closing body tag in that function with Page::print_wrapper_end() and see if it breaks?
(...huh, when I go into that layer it seems to imply mine is also core2, but I'm pretty sure it's not...)
no subject
Thank you for trying!
no subject
(Either this wasn't showing before and changing styles and coming back made it appear, or... I've been clicking on the wrong place for cut-tags for who knows how long. Either way, it's a cool option to have now.)
no subject
no subject
hah, no wait, I thought I had this problem but actually don't. Well, thank you anyway!