Steps to replicate the issue (include links if applicable):
What happens?:
The config is saved to the page SecurePoll:-1.
What should have happened instead?:
Config should have saved to page SecurePoll:1864, which as a result does not exist. I am not sure if this will impact the election when it goes live.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T398897 Fix bugs related to writing JSON when $wgSecurePollUseNamespace = true | |||
| Open | BUG REPORT | None | T406375 SecurePoll: Config saving as SecurePoll:-1 for election id 1864 |
I'm not sure if this would impact the election (the config appears to be saved correctly so it is probably fine?) but would really appreciate PSI have a quick look at this just in case.
It won't impact the election. The SecurePoll pages are read-only mirrors of what's actually stored in the database, and are not used as a source of truth.
But it works alright for 1872? For 1864, looks like it's saved to SecurePoll:-1 while creating it, and when editing it as well. That suggests the system thinks the election is really having id -1, but everything looks fine in the database.
I don't immediately see why this could be happening.