Article updates do not save 'ISEXTINCT: Expected boolean, received string'

closed
· Articles & templates ·
By WynFiadh on 11/18/2025
· Assigned to katerinach
· Waiting for Response Under Investigation

On some of my articles I get and error message ('ISEXTINCT: Expected boolean, received string') and nothing saves since last night.

Steps to Reproduce

Open an article, update the content, autosave is not working

Operating System

MacOS

Browser

Google Chrome

Related Entity

Any updates made to existing species articles are not saved.

History

katerinach @ 19 Nov, 2025 08:05:49 Assignee
Assigned katerinach
katerinach @ 19 Nov, 2025 08:05:55 Assignee
katerinach Added tag Under Investigation
irpguardian @ 19 Nov, 2025 06:56:50

I've encountered this as well, specifically when attempting to modify a "species" article and set a parent for a category when using the visual editor

WynFiadh @ 22 Nov, 2025 10:44:29

I am getting tired of this, it worked for a day, now it is happening again and I cannot make progress on my writing. This is the opposite of creative motivation, when you want to finish a campaign and you can't get it ready in time because this bug keeps reappearing.

TheeLuisifer @ 23 Nov, 2025 11:07:30

Has anyone solved this yet? I'm getting this error and cannot update a species name.

TotallyNotAWizard @ 23 Nov, 2025 06:01:46

I'm experiencing this, also on a Species article.

The error appears as soon as I place any text in the 'Content' field.

Dawn-giant-dragon @ 26 Nov, 2025 11:17:38

i got this on the Material article template while trying to bruteforce another bug for testing purposes, no idea what caused it

katerinach @ 27 Nov, 2025 11:08:28 Assignee

Hello, we've deployed a fix that should resolve this bug! Please try again and let me know if it's been fixed for you.

katerinach @ 27 Nov, 2025 11:08:36 Assignee
katerinach Added tag Waiting for Response
TotallyNotAWizard @ 28 Nov, 2025 08:15:34

I tested and am still experiencing the bug. I created a new Species article, and after inputting the title I am presented with the red bar below the header image stating: ISEXTINCT: Expected boolean, received string

I can navigate away from the article, and come back to the title and error message, but any content typed into the article does not save.

TotallyNotAWizard @ 29 Nov, 2025 04:26:47

Sorry for double post, I just noticed that Species articles that I have previously created and added content to (months ago) also display this error when they are opened, preventing me from adding any new content to them.

Lady Leah @ 30 Nov, 2025 04:33:51

I wasn't sure if I should open a new ticket because I'm having the exact same problem but exclusively with rank/title articles. After the title of the article saves, the green check never appears again and any work I write is lost when I go back.

I typically work on a Microsoft PC and I use the browser Ecosia.

katerinach @ 01 Dec, 2025 07:46:08 Assignee

Thanks for the information, I will be looking into this again and extending to the Rank articles.

katerinach @ 01 Dec, 2025 09:20:47 Assignee

I have identified the problem, until a fix is deployed for anyone that wants to keep working on these articles, the workaround is to disabled "Expand all article prompts" feature from the Features page .

SoulLink @ 02 Dec, 2025 07:43:21 Moderator
Bug has duplicate ISEXTINCT Error Bug
katerinach @ 03 Dec, 2025 10:34:26 Assignee

Hello again, we have made an additional fix which should resolve any form errors you see because of the "Is Extinct" field - please try again and let me know!

Lady Leah @ 05 Dec, 2025 03:20:27

Hello, save function is working for me on Species articles now, but my Rank/Title article is still not autosaving. It also does not get that "Is Extinct" error message.

katerinach @ 09 Dec, 2025 11:27:54 Assignee

Hi Lady Leah, is this still the case? We also pushed a seperate fix for a different issue affecting Rank/Title articles.

Lady Leah @ 09 Dec, 2025 07:54:12

I just tried editing my "Emperor" page and the autosave works again! Thank you, katerinach!

katerinach @ 10 Dec, 2025 07:41:17 Assignee
set this bug to closed