Last modified: 2014-11-10 18:57:56 UTC
The PAGESIZE parser function should also work as a magic word with no parameters, {{PAGESIZE}}. In such a case, it should not count as an expensive parser function, and it should return the size of the page that is currently saved, not the size as it was before. The current workaround {{PAGESIZE:{{FULLPAGENAME}}}} is expensive and retrieves the old pagesize from the db, which will usually not be the intended functionality, and needs a purge to return the current size. It would be perfect if the parser function behaved like that, too, when applied to {{FULLPAGENAME}}, for consistency at least, but I think one could live with the current behaviour there.
Updating summary a bit. Also (per r49575 and such) please consider renaming this to {{REVISIONSIZE}} (variable) and {{REVISIONSIZE:}} (parserfunction) with {{PAGESIZE:}} (parserfunction) as a legacy alias.
A variable {{REVISIONSIZE}} was added with Gerrit change #82650
Functionality is now as requested, but what Splarka wrote in comment #1 is still valid: REVISIONUSER (for example) works as both a magic word and an (expensive) parser function, but for page size you need to use REVISIONSIZE for the current page and PAGESIZE as the (expensive) parser function. That should be straightened out at some point.
