Board Thread:Support Requests - Getting Technical/@comment-4189499-20150607233806/@comment-24473195-20150908133258

Imamadmad wrote: When you mentioned the cache, it made me think to purge the page at DWA. That seems to have fixed the problem! It would be a pest, though, if the cache doesn't clear frequently enough for this module to remain accurate. S'pose there isn't much we can do about that. Well, at least it can be confirmed that the module works! Thanks for that.

If, however, you can find a way for the module to be able to be invoked from inside a template, that would be a great benefit. We currently use several non-automated versions of these templates for different messages and it would be good to keep the syntax relatively consistent between them, so the user still only has to type  for the template to work, with all the other details hidden behind the scenes for consistency's sake. It's not vital, as I assume (but have yet to try) that the invocation can still be pushed onto a page via a template subst, but if you do have the time and inclination to make the module work via a template, it would be appreciated! Great. I think only admins can actually purge the cache of the page because for some reason it didn't work when I tried to purge the cache. Maybe one has to be at least a "power user" or make at least one edit. Who knows.

The quickest fix would be to simply create another template, e.g. templatechanger. Copy the whole invoke stuff to it, and transclude templatechanger in "template:clarify" or:

{{#invoke:autochangecat|main|template1={{{template1|stuff}}}|template2={{{template2|stuff}}} | 1={{{reason|{{{1}}}}} |template=true}}

Anyway, that seems overly complex, so I'm thinking of changing the module to automatically use the template's arguments, and if they don't exist try using the page's arguments.

P.S. I think that the date parameter probably won't have problems with the cache.