It is beneficial for users to be able to edit their own topics - but could cause a problem of duplicate user topics if they do a rename/move. Not a very high priority bug - because users will probably understand that they (we) should not mess around with things and expect no consequences. However, there does seem to be a fundamental distinction between an edit and a rename that would benefit from a new permission type.

Solution

Add a RENAME permission alongside CHANGE/VIEW etc.

-- SteveRoe - 03 Jul 2001

Agreed, we need some restrictions on the rename/move feature. On the public TWiki.org site I prefer to restrict this operation to the TWikiAdminGroup since this feature allows to circumvent the "never forget" aspect of a Wiki system.

So, either a new RENAME permission preferences variable or a new configuration flag is needed. A RENAME permission preferences variable is most flexible.

-- PeterThoeny - 06 Jul 2001

I've made coding change and will upload soon. Nature of change is:

• Can use RENAME in same way as CHANGE and VIEW - a trivial change to Access.pm given the way it was written
  • [ PeterThoeny - 18 Jul 2001 ] Access.pm is written generic, no change to that module should be necessary for the new RENAME permission.
• This checked as well as CHANGE before a topic is renamed
  • [ PeterThoeny - 18 Jul 2001 ] Is this an "and" check like this?
    if( ( &TWiki::Access::checkAccessPermission( "rename", ...) && &TWiki::Access::checkAccessPermission( "change", ...) ) { ...
• Changed to referencing topics just check the CHANGE permission

On memory, the %METASEARCH{"topicmoved" from="..."}% can be used on the topic not found page to automatically show moved topics (so long as they're not moved more than once).

Security pages will need to be updated.

-- JohnTalintyre - 19 Jul 2001

Changed to FeatureUnderConstruction...if this is fully documented it can probably be FeatureDone.

-- WalterMundt - 08 Jan 2003