Pbsouthwood added a comment.
Fine, that is now clear to me. Thanks for clarifying
Is my question now sufficiently clear to get an answer?
{I dont know how {{DISPLAYTITLE}} and {{SORTKEY}} work, or what noerror and noreplace do)TASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL
Pbsouthwood added a comment.
If there are more than one short descriptions on the page the API call gets the last one. It would be far better if it got the first one, as there are a large number of pages where there is a default short description generated from a template or infobox, but for some
Pbsouthwood added a comment.
OK, got it. So the problem is that the last one is stored, where it would be more useful if the first one was stored. It would seem that there is a routine that runs through the whole page, changing the value each time an instance is found, instead of stopping as soon
Pbsouthwood added a comment.
It does not look like I am going to get a reply, so will have to open a task to have it fixed without knowing how practicable it isTASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences
Pbsouthwood added a comment.
The magic word SHORRTDESC stores the last instance found on the page. This is problematic and it would be preferable to store the first instance. Please fix
Short descriptions are automatically produced by several templates, Some produce a generic short description
Pbsouthwood added a comment.
a) What side effect?
b) How do you suggest we make this thing work?TASK DETAILhttps://phabricator.wikimedia.org/T184000EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Tgr, PbsouthwoodCc: Pbsouthwood, Deskana, Catrope, RexxS
Pbsouthwood added a comment.
This is worse if people use a bare magic word (not encased in the short description template, so the short description does not show using css as it has allocated class. The upside is that these have mostly been added at the bottom of articles, the downside
Pbsouthwood added a comment.
Sounds like a practical plan.TASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: PbsouthwoodCc: Tgr, RexxS, JJMC89, Aklapper, Liuxinyu970226, Pbsouthwood, Lahi, Gq86
Pbsouthwood added a comment.
Suddenly it is clear! Thanks for that explanation. Like a figure and ground problem, it depends on how you first look at it..TASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Tgr
Pbsouthwood added a comment.
If we were to add noreplace to all template inclusions, will it have any adverse effect. or should this wait until you are done?TASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences
Pbsouthwood added a comment.
Fair enough.TASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Tgr, PbsouthwoodCc: gerritbot, Alsee, Tgr, RexxS, JJMC89, Aklapper, Liuxinyu970226, Pbsouthwood, Versusxo
Pbsouthwood added a comment.
I am happy to see some action here. Is there an explanation somewhere of how this will work, so we can plan ahead? cheersTASK DETAILhttps://phabricator.wikimedia.org/T193857EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Tgr
Pbsouthwood added a comment.
"if there is an invocation without noreplace, that takes precedence over the noreplace ones."
If I understand this correctly, we must add noreplace to any magic word that can be replaced, and leave it out for the one which must not be replaced, whic
Pbsouthwood added a comment.
As far as I can see no-one has answered RexxS's question. Is it likely that
anyone here can actually do that?
TASK DETAIL
https://phabricator.wikimedia.org/T184000
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tgr
14 matches
Mail list logo
