• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item4473: check that we have a testable can_edit state

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
Engine   Enhancement Closed   minor 4.2.0

Edit Form Data

Summary:
Reported By:
Codebase:
Applies To:
Component:
Priority:
Current State:
Waiting For:
Target Release:
Released In:
 

Detail

and make sure its doccoed

I'm not sure if there is a contecxt that was not doccoed, or if this fell though the cracks

-- TWiki:Main/SvenDowideit - 21 Aug 2007

Depends on what you mean. Authorised to edit? No-one else holds a lease? Topic exists? There's a 'r' in the month?

-- TWiki:Main.CrawfordCurrie - 21 Aug 2007

I was thinking something to make the Edit, attach etc buttons only display if the user has the relevant permissions...

-- TWiki:Main.SvenDowideit - 25 Aug 2007

This is a good idea. Regraded as Enhancement. it would be really neat to have.

Another approach would be to add a checkpermission function to %IF. This would take two parameters, the name of the topic and the access mode to be checked e.g.

%<nop>IF{"checkpermission('Item4473','change')" then="do your best" else="do nothing"}%

CC

By coincidence I discovered that this is critical for a TWiki application I am working on for a client. I also need istopic and isweb existance checks. i know I could probably use %CALC, but there are other good reasons for not wanting to do that. All three operators implemented with unit tests.

CC

With the danger of stepping on someone's toes I will yet again reclassify this bug item. I am OK with seeing it as a bug fix but not a release blocker. So by all means fix it, but let us not discuss it at release meeting. So I simply just downgrade it to normal.

Additionally I interpret CC's statement as CC working on it. So changing the Waiting For field.

KJL

ItemTemplate
Summary check that we have a testable can_edit state
ReportedBy TWiki:Main.SvenDowideit
Codebase ~twiki4
SVN Range TWiki-4.2.0, Mon, 20 Aug 2007, build 14555
AppliesTo Engine
Component

Priority Enhancement
CurrentState Closed
WaitingFor

Checkins TWikirev:14639
TargetRelease minor
ReleasedIn 4.2.0
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r13 - 2008-01-22 - KennethLavrsen
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback