Is it this parsing issue or a similar rendering issue that also is the cause
for the book
tool not working on transcluded pages at Wikisource?
As per https://bugzilla.wikimedia.org/show_bug.cgi?id=21653
Regards, Andrew
On 19 Dec 2010 at 19:27, Platonides wrote:
Billinghurst wrote:
I am
Billinghurst wrote:
Is it this parsing issue or a similar rendering issue that also is the cause
for the book
tool not working on transcluded pages at Wikisource?
As per https://bugzilla.wikimedia.org/show_bug.cgi?id=21653
Regards, Andrew
No. It's a problem with the collection
Billinghurst wrote:
I am guessing that the search engine does not transclude pages before it
undertakes it
indexing function. Is someone able to confirm that for me?
Is there any fix that anyone can suggest, or even know where such an issue
can be raised
beyong Bugzilla? Would a fix
This would fix it for the default mysql search, although I'm not sure at
what level of overhead. The Lucene backend is using OAIRepository for
incremental updates, and builds whole indexes from XML dumps. Thus, the
expanded articles need to be present in *both* of those.
Cheers, r.
This
2010/12/19 Platonides platoni...@gmail.com:
That operation should be fast, as it should be hitting the cache from
having just rendered it.
Calling $wgParser-preprocess() won't hit the parser cache, I don't
think. I also don't think preprocessed wikitext is cached at all, just
the HTML output.
At bugzilla:18861
https://bugzilla.wikimedia.org/show_bug.cgi?id=18861
there is a discussion about how transcluded pages are not seen by the search
engine, and I
have made an assumption that is Wikisource's issue where its pages that are
transcluded
across from the Page: namespace don't
