|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #55201 markup markup
Submitted: 2011-07-13 10:28 UTC Modified: 2013-02-18 00:34 UTC
From: Assigned: yannick (profile)
Status: No Feedback Package: Online Doc Editor problem
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
New email:
PHP Version: OS:


 [2011-07-13 10:28 UTC]
The editor has a "markup" option that inserts markup for roles such as "examples" and "errors" but the current markup only 
applies to a refentry, which is not applicable outside of our reference/ area.

Example: Two days ago someone inappropriately inserted an example refsect1 into a chapter, so this broke the build.

I'm not sure the best way to handle this, but the following may (or may not) work:

- When inside refentry, append the current refsect1 info
- Otherwise, remove it and &reftitle.*; but leave the <para>

If that's too much magic, then we could adjust the "markup" button to offer multiple options per type so, for example, have 
"seealso refsect1" and "seealso standard" options. Something like that.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-07-21 19:17 UTC]
-Status: Open +Status: Feedback -Assigned To: +Assigned To: yannick
 [2011-07-21 19:17 UTC]
The first proposal is effectively too magic...

For the second, could you propose me what you thinks about ? witch content ?
You can view what is actually used here :
About line 178, you can view the "text" properties used in the list into the panel, and line 186, the beginning of the content.

Could you please make a proposal to implement ?

 [2013-02-18 00:34 UTC] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Fri Sep 29 00:01:24 2023 UTC