Multiverse: Server-side Cache won't update

Mechanics | Upcoming releases | Skeleton

Mockup
Plain

CardName: Server-side Cache won't update Cost: RR Type: Pow/Tgh: / Rules Text: /cardsets/2580/visualspoiler constantly reverts back to one of the earliest iterations. Card updates roll back on that page and don't reflect the hundreds of edits on pages, including but not limited to arturls, card titles, and rules text. On occasion the visual spoiler WILL reflect the up to date cards, however for some unknown reason when the page is returned to the edits are rolled back. Flavour Text: Clearing local cache does nothing. Set/Rarity: Multiverse Feedback None

Server-side Cache won't update

/cardsets/2580/visualspoiler constantly reverts back to one of the earliest iterations. Card updates roll back on that page and don't reflect the hundreds of edits on pages, including but not limited to arturls, card titles, and rules text.

On occasion the visual spoiler WILL reflect the up to date cards, however for some unknown reason when the page is returned to the edits are rolled back.

Clearing local cache does nothing.

Updated on 13 Jan 2023 by HarrisonY

History:

2023-01-09 14:28:40: HarrisonY created the card Server-side Cache won't update

by HarrisonY:

Lets move the cache image issues into here instead of the print format card.

https://drive.google.com/file/d/19EFZRal8oLuTnhvggsn7QOTELNMBJYWa/view?usp=drivesdk

This is a saved pdf of all my 'view by sections' pages. Vitenka, when you view the individual cards do you see art? It's confounding just how inconsistent the data is for my cardset.

I checked the export set and all the info seems to be there when I try exporting, consistent results for each export format. Could you be seeing something different because of the italicized '(unsigned)' after your name?

by Vitenka:

I did not, no. Trying while logged in - I do indeed see a difference between visual spoiler and individual cards. e.g. Migrating Settler demonstrates the issue.
And this card now DOES show an artURL when I export as JSON; which it did not previously (on a machine I wasn't logged in from)

Add your comments: