Last modified: 2011-04-14 15:11:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7005 - Show full template call, rather than a link to the template page, when the expansion size limit is tripped
Show full template call, rather than a link to the template page, when the ex...
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
unspecified
All All
: Low normal with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://fr.wikipedia.org/wiki/Utilisat...
:
: 7007 7009 7017 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-14 09:49 UTC by folengo
Modified: 2011-04-14 15:11 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description folengo 2006-08-14 09:49:55 UTC
On the following test page :

:fr:Utilisateur:Teofilo/test1

http://tinyurl.com/mhedy

I call ten times the same template {{D-2 MONTHNAME}} which is a template
displaying (in French) the month name of two days ago.

You can notice that the first 5 template calls are OK, while the following 5
calls result in errors. 

The French Wikipedia's village pump ("Le Bistro")'s main page which uses several
templates is currently brokendown, and I guess this failure is linked to the
above mentioned problem.
Comment 1 Rob Church 2006-08-14 10:12:44 UTC
Take a look at the source; several instances of "<!-- WARNING: template omitted,
pre-expand include size too large -->". Your template length is tripping the
parser's detection of mass-inclusion.
Comment 2 folengo 2006-08-14 10:30:11 UTC
What do you mean by "the source" ? Could you give me the URL please ? 

When I click on the "edit" tab, I cannot see any warning such as that which you
are quoting.

How comes that everything has been OK for 2 months, not to say 6 months, until
today or yesterday, and suddenly these templates can no longer be used properly?

Have some new restrictions been enacted today or yesterday ? 

Comment 3 Rotem Liss 2006-08-14 10:31:37 UTC
(In reply to comment #2)
> What do you mean by "the source" ? Could you give me the URL please ? 
> 

The source of the HTML page.
Comment 4 folengo 2006-08-14 10:40:26 UTC
This is just to say that I have found the warnings (in the HTML source as you
said, not in the edit tab, because the template is not "substed")(Thanks Rotem
Liss for the explanation).

So my only question remains : have some new restrictions been implemented
recently, because apparently everything was OK on the French village pump until
yesterday or this morning.
Comment 5 Rob Church 2006-08-14 12:31:18 UTC
*** Bug 7007 has been marked as a duplicate of this bug. ***
Comment 6 Rob Church 2006-08-14 13:05:56 UTC
*** Bug 7007 has been marked as a duplicate of this bug. ***
Comment 7 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-08-14 16:34:24 UTC
(In reply to comment #4)
> So my only question remains : have some new restrictions been implemented
> recently

Yes.  Tim said on IRC that some of the really large templates were causing
ten-second latency in some cases; things were getting out of hand with
ParserFunctions being used in insanely complicated configurations for stuff like
date functions.
Comment 8 folengo 2006-08-14 16:38:29 UTC
Is living in a time zone different from that of London (Greenwich Meridian Time)
an "insanely complicated configuration" ? 

Or can you tell me how to implement easily a template providing a {{CURRENTDAY}}
variable changing at midnight not GMT, but CEST (Central European Summer Time) ?
Comment 9 Daniel Kinzler 2006-08-14 16:43:36 UTC
see bug 366 for {{CURRENTDAY}} and time zones.
Comment 10 Brion Vibber 2006-08-14 19:15:52 UTC
That would be {{LOCALTIME}}, which is not yet implemented I 
think.
Comment 11 Daniel Kinzler 2006-08-14 21:02:42 UTC
*** Bug 7009 has been marked as a duplicate of this bug. ***
Comment 12 Daniel Kinzler 2006-08-14 21:22:22 UTC
*** Bug 7009 has been marked as a duplicate of this bug. ***
Comment 13 Tim Starling 2006-08-14 23:00:07 UTC
Fixed Le Bistro, fixed [[:fr:Utilisateur:Teofilo/test1]]. Mostly fixed 
through the introduction of {{CURRENTHOUR}}, to replace that huge #switch 
statement to extract the hour from {{CURRENTTIME}}. Moving template 
documentation to a subpage also helps a bit. 
Comment 14 Tim Starling 2006-08-15 03:16:11 UTC
(In reply to comment #7)
> (In reply to comment #4)
> > So my only question remains : have some new restrictions been implemented
> > recently
> 
> Yes.  Tim said on IRC that some of the really large templates were causing
> ten-second latency in some cases; things were getting out of hand with
> ParserFunctions being used in insanely complicated configurations for stuff like
> date functions.

I don't mind ParserFunctions being used for dates, that was one of the motivating 
applications. The applications I've seen today which I object to are:

1. using templates as huge pseudo-databases, e.g. with #switch. MediaWiki is not a 
DBMS. Maybe some day it will be, with with Wikidata, but currently it is extremely 
inefficient to use it in this way. Sorry, but you'll just have to update every page 
that uses the data, every time the data is changed.

2. Using MediaWiki as a scripting language to generate repetitive content on a 
single page. Since MediaWiki is not a scripting language, the templates used tend to 
be very esoteric. Thus, the generated content is very hard for non-technical users 
to edit. [[:ksh:Wikipedia:Babel]] was a prime example of this. In addition to 
incomprehensibility, it was also inefficient. It expanded to thousands of HTML 
comments, megabytes of redundant and useless text which the parser had to process on 
every cache miss.

I expect that most broken articles can be fixed by applying 
[[Special:ExpandTemplates]].
Comment 15 folengo 2006-08-15 05:55:42 UTC
Tim Starling, you are wonderful !
Comment 16 Rob Church 2006-08-15 13:33:50 UTC
*** Bug 7009 has been marked as a duplicate of this bug. ***
Comment 17 Rob Church 2006-08-15 13:33:56 UTC
*** Bug 7017 has been marked as a duplicate of this bug. ***
Comment 18 Rob Church 2006-08-15 13:34:57 UTC
Reopening this and duping all the others here; reopening in case something
further needs doing in bulk, although from comments here and elsewhere, I doubt
it. These issues will need to be corrected on a case-by-case basis.
Comment 19 Daniel Kinzler 2006-08-19 18:36:51 UTC
It seems "skipped" template expansions are now rendered as links - i.e. {{Foo}}
renders like [[Foo]]. This makes no sense at all. At *least* it should render
like [[Template:Foo]], but I don't think the link is helpful anyway.

Someone suggested that the fully unexpanded text should be show, including all
parameters. I agree with that - itwould be much more obvious what's going on,
and the result would still be intelligable, if not pretty.
Comment 20 Jeff G. 2010-10-30 09:22:14 UTC
I also think the fully unexpanded text should be shown, including all parameters.  This would aid greatly in troubleshooting.
Comment 21 Jeff G. 2010-12-13 01:46:09 UTC
Perhaps there could be a preference "Format links to non-existent templates {{like this|first|second|third}} (alternative: {{like this}})" under "Appearance / Advanced options" that defaults to unchecked (and can be checked for those of us who wish to fix templates and calls to them).

Also, perhaps there could be a preference "Prompt me when entering a redlink" under "Editing / Advanced options" that defaults to checked (and can be unchecked for those who regularly add redlinks).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links