-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
It would be perfect if it were possible to include () in a page title, when it comes do documenting methods/functions.
For example, I have a class with a method called .fooBar(), it would be great for the page title to be ".fooBar()"
When the brackets are at the end of the page tile, I am unable to save or even preview the page - clicking either button takes me back to the edit view.
Should the "()" be in the middle of the title, the following error is given:
---------------------------
The title you have entered contains invalid characters (:, @, /, \, &, !, |, #, $, *, ;, ~, [, ], (, ),
, <, >).
---------------------------
I usually create new pages by placing links to them from an existing page, then clicking the link to automatically go to the "add page" screen.
For example, [.fooBar()] <-- I click the resulting link and it goes to the "add page" screen, allows me to choose a template, enter herds of info in to the page and then, only when I come to preview or save, does it thorw a wobbler.
If () are never going to be allowed in a page title (as your error message above suggests) I would at least like to:
a) have a proper error message when trying to save or preview the page so I don't end up there wondering what is going on and eventually starting to question my own sanity (did I just click that button? pheraps I do have the memory retention of a goldfish?)
b) not be allowed to create a new page from a link that has () in it thus alerting me to the fact that () are not valid page title characters 2 hours before finally doing a test with () in the middle of a title and seeing the error message
If you could allow () in a page title, even if only as the last 2 characters, it would be a huge dream IMHO Failing that, see
CONF-885 for an alternate solution to the problem
- relates to
-
CONFSERVER-810 Page(link) creation process & the invalid characters in page title!
-
- Closed
-
[CONFSERVER-898] Cannot create pages with () in title
Workflow | Original: JAC Bug Workflow v3 [ 2896180 ] | New: CONFSERVER Bug Workflow v4 [ 2988783 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2787249 ] | New: JAC Bug Workflow v3 [ 2896180 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2717918 ] | New: JAC Bug Workflow v2 [ 2787249 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2379033 ] | New: JAC Bug Workflow [ 2717918 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2264233 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2379033 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2208022 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2264233 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2187304 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2208022 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1913610 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2187304 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1721561 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1913610 ] |
This seems like it might still be an issue in Confluence 5.10.3 (at least). Namely, where I can create a page title, that I then have to go into the database to get the page id to delete it... (reference: https://confluence.atlassian.com/confkb/unable-to-view-page-due-to-invalid-page-title-261752448.html)
I would think the better approach would be to not allow me to create pages with invalid titles in the first place...