Chapter synopsis "max length exceeded" could be more informative - GC Forums

Community

smbhax
smbhax

smbhax

Releases read: 52

Posts: 38

Member since: Nov 21, 2019

posted Nov 21, 2019

Chapter synopsis "max length exceeded" could be more informative

After typing out a "synopsis" entry for a new release, I got a "max length exceeded" error when clicking the "Save changes" button.

But there is no indication of what the max length is, or how far I was over it, leaving me to try cutting my text down via trial and error until the page would finally save without the error.

Ideally, there would be a "[current characters/max characters]" updating readout at a corner of the text entry field.

Nimloth admin supporter posted Nov 21, 2019

Ideally, there would be a "[current characters/max characters]" updating readout at a corner of the text entry field.
I've added this, it should be live within the next few minutes!

smbhax posted Nov 24, 2019

Nice!

Ran into a bug with this new feature--this happens in both the left-hand margin version of the field that you get when you're initially entering a new release's info, or the wider version you get to you click "Save changes" after having entered valid title, synopsis, and image info from the initial page:

- Enter text until the character counter exceeds 400/400.
- Click "Save changes."
= A "Max length exceeded" warning appears under the field--but at this point, adding or subtracting characters to the field does not change the counter.

It will start working again if you manage to eyeball and remove enough characters, without benefit of a working counter, and then click the save button.

Nimloth admin supporter posted Nov 25, 2019

I think I fixed and prevent character length beyond the 400 at this point even before saving. Let me know if that's not the case :)

smbhax posted Nov 28, 2019

Up to just now it seemed to be fixed, but I did encounter the problem while adding my latest page this evening--I'm not sure how I did it, because after pasting this 399-charactger text chunk into the left-margin version of the synopsis field, the counter said 408/400, and then wouldn't change count as I deleted characters:

Ink sketch for a reader supporting the comic through http://patreon.com/smbhax my Patreon campaign : D :http://smbhax.com/stuff/191127_patreon_sketch.jpg

^)^ Thank you!! : D

I'm off for the rest of the week for the Thanksgiving holiday; back with a new A* page on Monday! : )

~~~~~~~~~
The original 16" x 6.75" watercolor art for today's new A* page is https://www.ebay.com/itm/143454795994 : )

I've tried to get it to happen again with this same chunk of text, but now it's counting it as 399/400 correctly, and won't seem to go over 400 no matter what I do. So...I don't know how it broke it the first time. I'll have to keep an eye out during future updates.

Nimloth admin supporter posted Nov 28, 2019

Ah yes, I put in a fix for the going over the cap :)

smbhax posted Dec 13, 2019

Had this happen again--a 396 character chunk initially registered as a 401 character chunk, and the counter was stuck. I deleted the text and hit save, and was able to enter it--counted correctly--on the next screen. This was the text:

http://smbhax.com/stuff/191212_strange_suspense_stories_38_barbaric.jpgFrom "Specimen" in Strange Suspense Stories #38, September 1958. Pencils by Bill Molno, inks by Vince Alascia.

~~~~~~~~~
The A* original art holiday sale is on now! http://smbhax.com/cgi-bin/buy.pl?d=00390005 The original 16" x 6.75" watercolor art for today's new A* page is up for immediate sale at half price, just $25!

Eh hm, pasting it in here, the return and blank line between "barbaric.jpg" and "From" got removed. Let me try it again now in an edit:

http://smbhax.com/stuff/191212_strange_suspense_stories_38_barbaric.jpg

From "Specimen" in Strange Suspense Stories #38, September 1958. Pencils by Bill Molno, inks by Vince Alascia.

~~~~~~~~~
The A* original art holiday sale is on now! http://smbhax.com/cgi-bin/buy.pl?d=00390005 The original 16" x 6.75" watercolor art for today's new A* page is up for immediate sale at half price, just $25!


Looks okay as I enter it...

smbhax posted Dec 13, 2019

^ I'm getting timed out trying to add to that post. Here's what I was trying to edit in:

Eh hm, pasting it in here, the return and blank line between "barbaric.jpg" and "From" got removed. Let me try it again now in an edit:

http://smbhax.com/stuff/191212_strange_suspense_stories_38_barbaric.jpg

From "Specimen" in Strange Suspense Stories #38, September 1958. Pencils by Bill Molno, inks by Vince Alascia.

~~~~~~~~~
The A* original art holiday sale is on now! http://smbhax.com/cgi-bin/buy.pl?d=00390005 The original 16" x 6.75" watercolor art for today's new A* page is up for immediate sale at half price, just $25!


Looks okay as I enter it...

(Edit to THIS post: Okay, after entering this, the previous post reloaded and I guess my edit there, which was stuck on the rotating loading icon after I tried to update that post, went through, so now this is a double post. Ah, forum.)

smbhax posted Dec 13, 2019

(My edits to posts seem to be timing out, then maybe turning out to have gone through somehow anyway when I make a new post.)

smbhax posted Dec 13, 2019

Huh, that same text chunk was also hitting an over 400 error on the new Smack Jeeves, even though its text counter only counted it as 396. I wonder if both sites are converting some of the special characters there into code characters that are then counted as more characters. (For SJ, I deleted most of that row of tilde characters, and then it went through.)

smbhax posted Dec 13, 2019

(Like, quotation marks being converted into

"
and thus being counted as six characters internally, or something like that.)

smbhax posted Dec 13, 2019

^ Eh okay the HTML "& + quot + ;" still converted into a quotation mark, even though I had it in the "code" tag.

Nimloth admin supporter posted Dec 20, 2019

Hrrm... that input field should be single-char based. I think the field validation automatically uses HTML entities for decoding, which seems to cause an issue here. I'm not sure off the top of my head to easily fix this...

I'll think about it for a bit.

Thanks for being so detailed and granular on this reporting!