Maybe I need some kind of a lock.php function to be able to save individual tiddlers, that aren't locked???
On 2 Mar., 20:09, Måns <[email protected]> wrote: > Hi again Eric > > The TiddlerLock plugin has made it impossible for me to upload the > single tiddlers not tagged with "locked" from my iTW. > When I try to update/create/modify a tiddler I get this errormessage: > <br /> > <b>Warning</b>: fopen(./index.html) [<a > href='function.fopen'>function.fopen</a>]: failed to open stream: > Permission denied in <b>/var/www/xxxx.dk/weekend/storeTiddler.php</b> > on line <b>362</b><br /> > <br /> > <b>Warning</b>: flock() expects parameter 1 to be resource, boolean > given in <b>/var/www/xxxx.dk/weekend/storeTiddler.php</b> on line > <b>363</b><br /> > Error : 'index.html' couldn't be locked - File NOT updated ! > > Should I write a lockfile (txt) on the server to get it to work again > - or should I remove the plugins - and try to do something else? > If you'd like to take a look at it - I will mail the adress and the > password to you.. > But maybe it's just the lockfile and the uploadtiddlersplugin that > don't work together?? > > YS Måns Mårtensson > > On 28 Feb., 15:24, Måns <[email protected]> wrote: > > > I've imported > > # TaggedTemplateTweak > > # TiddlerPasswordPluginConfig > > # TiddlerPasswordPlugin > > # LockedEditTemplate > > and tagged all the fragile tiddlers with "locked" - and it workes > > excactly as I wanted. > > > My lesson learned is: When Mr. Shulman gives You a hint - you'd better > > try it before you reject it... > > I apologize profusely to mr. Shulman - and I will slow down and do the > > testing before I jump to conlusions in the future. > > > Thank you very much mr. Shulman!! > > > As a reference for anyone else having a similar problem - I will > > resume some of my considerations here: > > > I considered using ExternalTiddlersPlugin to be able to restore the > > tiddlers when they break - When someone accidentially edited the > > tiddler > > - or maybe even better > > > - make "alias tiddlers" with <<tiddler TiddlerName>> so people won't > > get to the code by mistake. > > (iTW uses ListByTag - it's a plugin which makes it possible to have a > > Home-list of tiddlers tagged with Home as a "tappable" line (works > > very good on my ppc) - and use the iTW in the sidebar of FF or as a > > programlink from Chrome. Here it really looks well - because Chrome > > simulates iTWs iPhone-look.) > > > I would move the code to other tiddlers and change the FET-code from: > > <<forEachTiddler > > where > > 'tiddler.tags.contains (context.inTiddler.title) > > To: > > <<forEachTiddler > > where > > 'tiddler.tags.contains ("TagName") > > > Now I don't need to.. > > > Thank you very much Eric!! > > > YS Måns Mårtensson > > > On 27 Feb., 02:26, Måns <[email protected]> wrote: > > > > Thank you for answering my question. > > > But - I didn't explain the situation correctly... sorry > > > > I need people to be able to see and use the content of certain > > > tiddlers - not beeing able to edit the specific tiddlers > > > (online).http://groups.google.com/group/TiddlyWiki/browse_thread/thread/e750e6... > > > I've made a table which uses forEachtiddlerplugin to gather > > > information from other tiddlers and uses toggletags to tag those > > > tiddlers. (in a sortable table) > > > The code for this breaks when You save it online... so I don't want > > > anyone (not even myself) to be able to edit the content of these > > > 'preconfigured' tiddlers.(online). They are just there to gather > > > information and toggle tags - not to be edited.. > > > I use BidiX's iTW and his tiddleruploadplugin with great success > > > because of its ability to upload single tiddlers when refreshed. It > > > enables me and my collegues to tag different tiddlers in the same iTW > > > at the same time - and get sortable lists that we print via > > > snapshotPlugin and a normal printer.... Its quite simple - yet > > > effective. > > > > YS Måns Mårtensson > > > > On 27 Feb., 01:16, Eric Shulman <[email protected]> wrote: > > > > > > Is it possible to tag or insert a macro that prevents editing > > > > > capabilities only for certain tiddlers when the TWs online? > > > > > First, install these tiddlers: > > > > http://www.TiddlyTools.com/#TiddlerPasswordPlugin > > > > http://www.TiddlyTools.com/#TiddlerPasswordPluginConfig > > > > http://www.TiddlyTools.com/#TaggedTemplateTweak > > > > http://www.TiddlyTools.com/#LockedEditTemplate > > > > > Then, for any tiddler that you don't want people to edit, simply tag > > > > it with "locked", so it uses the alternative [[LockedEditTemplate]]. > > > > This template invokes the <<getTiddlerPassword>> macro to prompt for > > > > the admin password before rendering the standard EditTemplate. If you > > > > don't enter the correct password, the tiddler is automatically closed, > > > > effectively preventing you from editing the tiddler. > > > > > Note: by default, [[LockedEditTemplate]] is tagged with 'locked', so > > > > that people won't be able to break the lock on other tiddlers just by > > > > editing the template to remove the macro="getTiddlerPassword" > > > > invokation. > > > > > Similarly, [[TiddlerPasswordPluginConfig]] also requires you to enter > > > > an admin password, just to *view* that tiddler, so that the admin > > > > password itself cannot be viewed or modified without knowing the > > > > current password. > > > > > The default password is 'admin'. You should change this once you have > > > > sucessfuly installed the above mentioned plugins, config, and template > > > > tiddlers. > > > > > enjoy, > > > > -e > > > > Eric Shulman > > > > TiddlyTools / ELS Design Studios --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
