Another new bug

[TheLobster]

It does not matter what you use to center the text. It sometimes breaks on <center> it sometimes breaks on <p align=center> and it sometimes breaks with no tags at all because you centered the text in a word processor.

I used right-aligned paragraphs in a few stories and haven't had that happen. It's odd that it would be centering in particular that triggers the big, considering the whole centered section is apparently gone rather than just becoming invisible due to botched CSS

 

[PennyThompson]

*sigh*

@PennyThompson, the book!

The HTML witches are back!

 

[old_prof]

I used right-aligned paragraphs in a few stories and haven't had that happen. It's odd that it would be centering in particular that triggers the big, considering the whole centered section is apparently gone rather than just becoming invisible due to botched CSS

If you have paragraphs, it seems to be okay. Every case I have heard of is using centered strings of punctuation (+ or * or = or ...) My How To used centered section sub titles and they all seem fine.

A big unknown to me is unicode, like @TheRedLantern wants to center korean text at points. I can easily imagine a stupid check for text that only matches [a-zA-Z]

 

[SugarStorm]

The HTML witches are back!

The candles are lit, the code is unstable… it’s getting hot in here.

View attachment 2584010

Edit // I guess things got a bit too hot. I'm sorry, AH_Mod.

 

[old_prof]

This appears to be fixed! At least for my test case I was checking.
It was still broken yesterday afternoon.

Thank you @Manu

 

[TheLobster]

This appears to be fixed! At least for my test case I was checking.
It was still broken yesterday afternoon.

Thank you @Manu

Praise Manu! (May he live forever).

 

[MrPixel]

This appears to be fixed! At least for my test case I was checking.
It was still broken yesterday afternoon.

Thank you @Manu

It is not fixed. My story that just went up an hour ago has the problem. I posted a new thread in the tech forum.

What I've found is: 1) Problem is browser dependent. Firefox/MacOS is fine. DuckDuckGo, Safari, and Vivaldi (MacOS) are not; 2) Centered dividers on Page 1 are all there. Pages >1 is where things are hit and miss, mostly miss.

I submit all my stories as .docx uploads with no hidden HTML to bugger things, as I have for years.

Frankly, my stories read like mush without the breaks. Play by the rules, get kicked in the ass. This kind of basic bug pisses me off. Sorry.

Edit: Tried the current SeaMonkey. It displays the centered breaks fine, but has problems with other LitE page formatting, especially the bottom-of-page stuff like page numbers and voting stars.

Edit #2: Broken on Firefox/Linux and Chromium/Linux.

 

[RocketGrunt]

I've been putting my scene breaks in left-aligned. There's just no way to know if center-aligned text is going to display. Clicking the page shift button (even shifting back to page 1 from a later page) causes some of the center-aligned lines to vanish. No combination of formatting or text content reliably leaves it spared.

A left aligned screen break looks worse and is less obviously a scene break, but at least it doesn't intermittently break the site code.

Sadface.

 

[onehitwanda]

Still not fixed - firefox on windows or firefox on iphone.

At which point do I have to move on to acceptance?

now, I suppose.

 

[AwkwardlySet]

Still not fixed - firefox on windows or firefox on iphone.

At which point do I have to move on to acceptance?

now, I suppose.

What I don't understand is, if they are unable to fix the problem, why don't they simply roll back the interface to the version that worked fine until they figure it all out?
I mean, doing things on the fly is a ridiculous approach in itself, but then at least be ready to react swiftly to problems that pop up. Yet we are in this state where stories don't display correctly, a most fundamental flaw in the website's function, for over a month now.

 

[onehitwanda]

What I don't understand is, if they are unable to fix the problem, why don't they simply roll back the interface to the version that worked fine until they figure it all out?
I mean, doing things on the fly is a ridiculous approach in itself, but then at least be ready to react swiftly to problems that pop up. Yet we are in this state where stories don't display correctly, a most fundamental flaw in the website's function, for over a month now.

the correct story is being served from api.literotica.com - we've had multiple people confirm this. It's even available - correctly formatted - in the source code of the stories page.

It's entirely possible the display bug is being caused by whatever front-end CMS platform they've based Lit on, and potentially the various "backend changes" were done in November (that fucked the site like the village bull) are tied to the front-end software version and cannot be rolled back.

but it would be nice if someone would just fucking say "yes, we know, and we're sorry, we're working on it, but there's no eta" so we at least know that SOMEONE out there was listening.

 

[AwkwardlySet]

the correct story is being served from api.literotica.com - we've had multiple people confirm this. It's even available - correctly formatted - in the source code of the stories page.

It's entirely possible the display bug is being caused by whatever front-end CMS platform they've based Lit on, and potentially the various "backend changes" were done in November (that fucked the site like the village bull) are tied to the front-end software version and cannot be rolled back.

but it would be nice if someone would just fucking say "yes, we know, and we're sorry, we're working on it, but there's no eta" so we at least know that SOMEONE out there was listening.

I suppose that's possible, but backend and frontend being tied like that is unusual. And even if that's so, that would make their decision to do things on the fly even more of a joke.
So much time has already passed without a fix. To me, all of this feels like a case of severe incompetence.

 

[onehitwanda]

I suppose that's possible, but backend and frontend being tied like that is unusual. And even if that's so, that would make their decision to do things on the fly even more of a joke.
So much time has already passed without a fix. To me, all of this feels like a case of severe incompetence.

Or the usual magpie thing of chasing the new shiney while letting the subframe rust away.

 

[MrPixel]

This problem so seriously affecting story quality is the type of thing that drives content creators elsewhere. Literotica doesn't need more incentives to leave, it has enough working against it already. I couldn't sleep last night mulling my next move, which would definitely not be a happy one.

I'm saying this having been in the publishing and related business for 50 years.

 

[AwkwardlySet]

This problem so seriously affecting story quality is the type of thing that drives content creators elsewhere. Literotica doesn't need more incentives to leave, it has enough working against it already. I couldn't sleep last night mulling my next move, which would definitely not be a happy one.

I'm saying this having been in the publishing and related business for 50 years.

A lot of this seems to be the case of Lit acting as if this is still a small site that a few people can manage. Hire some god damned professionals to work on developing the interface and the database, if that's what you want to do. If money is the issue, put the link to donate on the front page, the same as AO3 does, and I'm sure the sum would be reached within a day.

This all feels like one or two people stubbornly insisting on them developing and fixing stuff that's clearly beyond their skill and knowledge.

 

[MrPixel]

I've been putting my scene breaks in left-aligned. There's just no way to know if center-aligned text is going to display. Clicking the page shift button (even shifting back to page 1 from a later page) causes some of the center-aligned lines to vanish. No combination of formatting or text content reliably leaves it spared.

A left aligned screen break looks worse and is less obviously a scene break, but at least it doesn't intermittently break the site code.

Sadface.

I had been mulling this. However, with 100+ stories in the bank using the centered dividers, going back to patch them up as a workaround... gawd... then enduring the weeks of waiting for each edited reload to pass muster and be posted? Ho-lee cow.

This is @Manu 's problem to fix, not mine.

 

[old_prof]

I want to add an update for anyone else I know who has experienced this problem

I adjusted my section separator from a row of + to a row of x for my story that just appeared. Using non punctuation does not fix the problem, unfortunately.