Infrastructure/fedora-infrastructure

Fork 0

Category problems in Wiki #7412

New issue

Closed

opened 2018-11-29 19:59:16 +00:00 by bcotton · 13 comments

bcotton commented

2018-11-29 19:59:16 +00:00

I've had two separate changes be set to the ChangeReadyForWrangler category in the Wiki but not be shown on the category page. The most recent one did not appear until after I edited it (but left the Category alone). I also created a dummy page and it showed up, so that rules out my short-lived "it only happens if the ChangeReadyForWrangler category is set on page creation theory.

I don't have anything else helpful to provide, but if you can find an explanation, I'd be very grateful. I don't want Change proposals to get lost.

I've had two separate changes be set to the `ChangeReadyForWrangler` category in the Wiki but not be shown on the category page. The [most recent one](https://fedoraproject.org/wiki/Changes/NautilusExtensionsPython3) did not appear until after I edited it (but left the Category alone). I also created a dummy page and it showed up, so that rules out my short-lived "it only happens if the `ChangeReadyForWrangler` category is set on page creation theory. I don't have anything else helpful to provide, but if you can find an explanation, I'd be very grateful. I don't want Change proposals to get lost.

ferdnyc commented

2018-11-30 12:51:17 +00:00

Just wanted to add that the page failed to show in both of the categories it was assigned, so the issue doesn't appear to be anything specific to Category:ChangeReadyForWrangler. Since Ben edited the page, it's now listed in both Category:ChangeReadyForWrangler and Category:SelfContainedChange — the two categories that were always showing (as working links) on the bottom of the page, ever since it was created.

Just wanted to add that the page failed to show in _both_ of the categories it was assigned, so the issue doesn't appear to be anything specific to Category:ChangeReadyForWrangler. Since Ben edited the page, it's now listed in both Category:ChangeReadyForWrangler and Category:SelfContainedChange — the two categories that were always showing (as working links) on the bottom of the page, ever since it was created.

bowlofeggs commented

2018-12-13 21:15:16 +00:00

Metadata Update from @bowlofeggs:

Issue priority set to: Waiting on Assignee (was: Needs Review)
Issue tagged with: wiki

**Metadata Update from @bowlofeggs**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: wiki

codeblock commented

2019-01-29 07:36:14 +00:00

This sounds to me like a caching issue. Next time it happens, can you try purging the cache of the category page (and perhaps the page being added?).

https://www.mediawiki.org/wiki/Manual:Purge explains how, but mainly just go to the page and throw ?action=purge at the end of the URL, then press the button that shows up.

This sounds to me like a caching issue. Next time it happens, can you try purging the cache of the category page (and perhaps the page being added?). https://www.mediawiki.org/wiki/Manual:Purge explains how, but mainly just go to the page and throw `?action=purge` at the end of the URL, then press the button that shows up.

kevin commented

2019-01-31 21:09:46 +00:00

I'm going to close this now, but do reopen or file a new one when/if it happens again and we can make sure it's just a cache issue.

kevin commented

2019-01-31 21:09:46 +00:00

Metadata Update from @kevin:

Issue close_status updated to: Fixed
Issue status updated to: Closed (was: Open)

**Metadata Update from @kevin**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)

bcotton commented

2020-04-03 16:32:02 +00:00

Author

Reopening since it happened again. I did a purge of the category page as suggested, to no effect.

Reopening since [it happened again](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SMGUT5F6XUTNZRS7UEMAZMSEMR7PMHB7/). I did a purge of the category page as suggested, to no effect.

bcotton commented

2020-04-03 16:32:02 +00:00

Author

Metadata Update from @bcotton:

Issue status updated to: Open (was: Closed)

**Metadata Update from @bcotton**: - Issue status updated to: Open (was: Closed)

ferdnyc commented

2020-04-04 04:10:35 +00:00

It seems to be a MediaWiki a parser error, of some sort, rather than a cache issue.

If I go to Special:ExpandTemplates and fill in the following wikitext:

{{:Changes/RemoveGlibcHeaders}}

(which does nothing but transclude the entire article contents), the [[Category:ChangeReadyForWrangler]] link does not appear in the processed output. It's getting dropped for some reason.

If I copy-paste the entire wikitext source of Changes/RemoveGlibcHeaders into the wikitext field, same result: The ChangeReadyForWrangler category is nowhere to be found.

It seems to be a MediaWiki a parser error, of _some_ sort, rather than a cache issue. If I go to [Special:ExpandTemplates](https://fedoraproject.org/wiki/Special:ExpandTemplates) and fill in the following wikitext: ```mediawiki {{:Changes/RemoveGlibcHeaders}} ``` (which does nothing but transclude the entire article contents), the `[[Category:ChangeReadyForWrangler]]` link does _not_ appear in the processed output. It's getting dropped for some reason. If I copy-paste the entire wikitext source of [Changes/RemoveGlibcHeaders](https://fedoraproject.org/w/index.php?title=Changes/RemoveGlibcHeaders) into the wikitext field, same result: The ChangeReadyForWrangler category is nowhere to be found.

ferdnyc commented

2020-04-04 04:11:34 +00:00

Hah! Oh, wait, I see it.

The text preceding that category (line-wrapped for clarity):

<!--- UNCOMMENT only if this Change aims specific product, working group
 (Cloud, Workstation, Server, 

== Current status ==

[[Category:ChangeReadyForWrangler]]

Hah! Oh, wait, I see it. The text preceding that category (line-wrapped for clarity): ```mediawiki <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, == Current status == [[Category:ChangeReadyForWrangler]] ```

ferdnyc commented

2020-04-04 04:12:16 +00:00

So, false alarm. It's a source issue.