Page MenuHomePhabricator

Anons w/o edit permissions have problem with references if gallery tag is used.
Closed, ResolvedPublic

Description

Author: dan

Description:
This bug is applied only for anonymous without edit permissions, registered users don't have problems with references

For example anons have problem with items 3,4,5

1. Anons can see references

*A<ref name=ref1>All is Good</ref>
*B<ref name=ref2>Anons can see references</ref>
<references/>

2. Anons can see multiple references

*A<ref name=ref3>Anons can see multiple uses of refs</ref>
*B<ref name=ref3/>
<references/>

3. But if multiple refs and gallery are used together Anons will get problem

*A<ref name=ref4>Multiple uses of the refs and gallery tag after all refs. Anons are not able to see it.</ref>
*B<ref name=ref4/>
<gallery>Image:Sample.jpg</gallery>
<references/>

4. Anons are not able to see ref before gallery

*A<ref name=ref5>Oops. Anons are not able to see this message.</ref>
<gallery>Image:Sample.jpg</gallery>
*B<ref name=ref6>... but can see this one.</ref>
<references/>

5. 'Cite error references no test' error msg for Anons

*A<ref name=ref7>Gallery between ref tags and multiple uses of refs cause 'cite_error_references_no_text' error.</ref>
<gallery>Image:Sample.jpg</gallery>
*B<ref name=ref7/>
<references/>


Version: unspecified
Severity: normal

Details

Reference
bz16767

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:28 PM
bzimport added a project: Cite.
bzimport set Reference to bz16767.
bzimport added a subscriber: Unknown Object (MLST).

dan wrote:

severity is critical due to item#5 -- all anonymous users have good-visible red error message on the screen.

dan wrote:

It seems anons w/o edit permissions can't see references *before* gallery

May be related to [[bugzilla:6164]]

Funky... can confirm this locally. Likely similar to bug 6164, something's clearing parsing state.

Adding dependency to bug 15819, as both bugs have the same cause and bug 15819 has a patch attached.

costellojp wrote:

Bug 11224 seems to be the same. Obviously this issue still exists.

*** This bug has been marked as a duplicate of bug 11224 ***

Are you sure this is a duplicate of bug 11224. It looks like a different issue and is not fixed by the patch on that bug (although it does seem to have been fixed independently at some point between 1.13.3 and 1.15). It seems more likely that this bug and bug 15819 are the same. The patch over there *does* fix this bug.