Page MenuHomePhabricator

Poem extension exposes strip markers with long Chinese texts
Closed, DeclinedPublic

Description

Author: Coiby.Xu

Description:
When wrap long Chinese texts, the texts become: "UNIQ5cdcc5dd4cb4e01e-poem-00000000-QINU".


Version: unspecified
Severity: major

Details

Reference
bz38087

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:50 AM
bzimport set Reference to bz38087.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #0)

When wrap long Chinese texts, the texts become:
"UNIQ5cdcc5dd4cb4e01e-poem-00000000-QINU".

Can you paste some example text? Or can you paste a link to where you see this problem?

This bug could be a duplicate of bug 35291, but it's impossible to know without further information.

Coiby.Xu wrote:

(In reply to comment #1)

(In reply to comment #0)

When wrap long Chinese texts, the texts become:
"UNIQ5cdcc5dd4cb4e01e-poem-00000000-QINU".

Can you paste some example text? Or can you paste a link to where you see this
problem?

I'm sorry it's in the local network which can't be visited from outside.

It seems it's because I use Extension:LiquidThreads.

Coiby: Could you tell us pled which version of MediaWiki you use?
Which extensions are deployed? And is this still an issue?

Coiby.Xu wrote:

Hi
I'm using 1.18.1 and the installed extensions are Poem and Liquid Threads 2.0.
Yes, it's still an issue.

Coiby: Could you tell us pled which version of MediaWiki you use?
Which extensions are deployed? And is this still an issue?

1.18.x is not supported anymore and 1.18.1 is an old 1.18.x release.
Testing with 1.20.x or latest 1.19 is highly welcome.

I put some "long Chinese text" inside <poem>, and it worked fine. See [[testwiki:Poem]] (edit 2018-04-06 - moved to [[testwiki:Poem1]]). I even tried it inside LiquidThreads ([[testwiki:Talk:Poem]]), and that worked fine too.

The only way forward here is to provide an example of a <poem> tag that fails, or else to re-test with a newer version of MediaWiki and see whether the bug has gone away.

Closing this. If you are still encountering this issue, feel free to reopen this bug or comment below.