Ticket #966 (closed enhancement: duplicate)

Opened 3 years ago

Last modified 2 years ago

Feature Request: Unlimited Article-Names (and sef-urls AND a <title> in one stroke)

Reported by: tnt Owned by: BrianKoontz
Priority: normal Milestone: 1.3.1
Component: unspecified Version: 1.2
Severity: normal Keywords:
Cc:

Description (last modified by BrianKoontz) (diff)

Hello all

I'm quiet new to Wikka but I like it for its simpleness and for doing everything I need through very simple concepts. But there is one thing (or two) I really don't like: these camelcase-names.

When I type an url in my browser like " http://my.wikka-install.tld/hello world" the browser automatically turns it into  http://my.wikka-install.tld/hello%20world and wikka (or is it apache?) in turn converts %20 back to a space and asks me:

This page doesn't exist yet. Maybe you want to create it?

And 'create' is linked to  http://my.wikka-install.tld/hello%20world/edit. This is half of the thing I wish! When the edit link is clicked the 'hello world' is checked for being a valid wikiname and that fails of course.

If spaces, lowercase-only words, and maybe some more characters would be allowed in article names, we had search-engine-friendly urls and there would be no need to parse a title from a heading within the article. Links could look like this:

[[ 'hello world' ]], [[ 'Nice %27WikiNames%27' ]] (the latter would render as <a href=" http://my.wikka-install.tld/Nice%32%27WikiNames%27">Nice &apos;WikiNames&apos;</a>), [['hello world' Hallo Welt]], ...

The old links could work as always without a need to change anything.

What do you think? Wouldn't be these improvements (advantages? - please excuse my english) be worth the efforts neccesary to make this possible?

Regards, T.

See also

Change History

Changed 3 years ago by tnt

I hacked my installed 1.2 to do what I suggested above. It works for me now and here but I would of course prefer to have it integrated in future versions (in a more defined and reliable way).

Would anybody be interested in that I suggest some patches for 1.3 (or 1.4)? I would of course be more careful and of course we had first to discuss what exactly should be allowed (and in which way 'normalized' the names should be stored). I suggest at least the following characters to be allowed in article names:

'"%-_!§$%&()=?+*.:,;|

Changed 3 years ago by BrianKoontz

  • milestone set to 1.4

Please do continue with your bug reports...since no more new features are slated for 1.3 (we're trying to get it out of the door by clearing up the existing tickets), make sure you designate a milestone of 1.4 or later.

Changed 3 years ago by BrianKoontz

  • version changed from 1.3 to 1.2

Changed 3 years ago by BrianKoontz

  • description modified (diff)

Changed 3 years ago by BrianKoontz

  • milestone changed from 1.4 to 1.3

Changed 3 years ago by BrianKoontz

  • owner changed from unassigned to BrianKoontz
  • status changed from new to assigned

(In [1630]) Removed CamelCase requirements for page names. Refs #431.

Changed 3 years ago by BrianKoontz

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

Closing as duplicate with #191, but cross-referencing with #191 for reference.

Changed 2 years ago by BrianKoontz

  • milestone changed from 1.3 to 1.3.1

Changed milestone to 1.3.1

Note: See TracTickets for help on using tickets.