Page MenuHomePhabricator

Using Special:Recentchangeslinked more than once on a single page shows an error "Unstrip size limit exceeded (5 000 000)"
Closed, InvalidPublic

Description

Hellow

Multiple special page transclusions using Special:Recentchangeslinked on a single page shows an error "Unstrip size limit exceeded (5 000 000)".

Only the two first uses of Special:Recentchangeslinked are displayed, and the last ones are replaced with the error message "Unstrip size limit exceeded (5 000 000)"

See here for example :
https://fr.wikipedia.org/wiki/Projet:Jeu_vidéo/Suivi_global

This problem only occurs since few days, friday perhaps.

Event Timeline

The wikitext in the link provided calls {{Special:Suivi des liens/Projet:Jeu vidéo/Index|hidebots=0|limit=1000|days=30}}

For a (technical) explanation: unstrip-size-warning is shown when the maximum expansion size for nested parser extension tags is exceeded. "Unstrip" refers to the internal function of the parser, called 'unstrip', which recursively puts the output of parser functions in the place of the parser function call.

This comment was removed by Archimea.

The wikitext in the link provided calls {{Special:Suivi des liens/Projet:Jeu vidéo/Index|hidebots=0|limit=1000|days=30}}

For a (technical) explanation: unstrip-size-warning is shown when the maximum expansion size for nested parser extension tags is exceeded. "Unstrip" refers to the internal function of the parser, called 'unstrip', which recursively puts the output of parser functions in the place of the parser function call.

Too technical for me. i'm really sorry.

It worked fine before, and it's now not working anymore..This feature is usefull ad used...
How to get it back working ? how to fix this ? to get the page work in the same way as before ?

regards

matmarex subscribed.

There is a limit on the amount of content that can be generated by transclusions (the "unstrip post‐expand size"), and this limit is 5 000 000 bytes. If your transclusions are exceeding it, I can only recommend making them smaller (e.g. lowering the number of days for the list of recent changes) or splitting the pagae. While I'm not an authority on this matter, I am pretty sure that we're not going to raise the limit.

(For what it's worth, the page currently displays fine, using 3 177 469 bytes of generated content.)