Ticket #199 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

Valid Wikinames differ in page creation and page cloning

Reported by: WazoO Owned by: DarTar
Priority: low Milestone: 1.1.6.2
Component: core Version: 1.1.6.0
Severity: minor Keywords: validation wikiname camelcase
Cc:

Description

Version 1.1.6.2.Alpha (dropdown box doesn't offer this selection) OE6SecureHandling isn't seen as a Wiki name. This was going to be a page cloned (copied) from an existing 1.1.6.1 install, but the title was acceptable. Just reporting now, as I can't recall if this is something I "fixed" in my 1.1.6.1 intall or not ....

Change History

Changed 6 years ago by DarTar

  • keywords validation wikiname camelcase added
  • summary changed from OE6SecureHandling not seen as a Wiki name to OE6SecureHandling not seen as a WikiName
  • version changed from 1.1.6.1 to 1.1.6.0
  • milestone set to 1.1.6.2

WazoO, this is as expected: it's true that at the moment you can create pages that are not necessarily CamelCase, whereas the clone handler enforces CamelCase compliance. You'll obtain the same (negative) result if you try to use OE6SecureHandling as a username. There was an enhancement request to allow wikinames starting with digits or containing digits in the first WikiWord, this requires changing the regex patterns for wikiname validation.

Obviously, making page creation consistent with page cloning should be a priority, but this is not a new issue in 1.1.6.2 since it applies at least since 1.1.6.0.

Changed 6 years ago by DarTar

  • owner changed from unassigned to DarTar
  • status changed from new to assigned
  • summary changed from OE6SecureHandling not seen as a WikiName to Valid Wikinames differ in page creation and page cloning

Changed 6 years ago by DarTar

  • status changed from assigned to closed
  • resolution set to fixed

[111] fixes this issue - the validation pattern used by the clone handler is now the same as the one used for creating pages in the edit handler.

In the long run, this will be dealt with by a central regex library - #34

Changed 5 years ago by JavaWoman

  • status changed from reopened to closed
  • resolution set to fixed

Seems to have been reopened by spam removal; closing again...

Note: See TracTickets for help on using tickets.