Thorsten Scherler wrote: > Hi all, > > I will now merge back the ac branch into the trunk. This means all > custom pubs need an update!
grmbl. as much as i appreciate your work, i think you could have asked first. what's the problem of letting the users decide when to do a svn switch? for the first time since mid-june, i've been able to get my project in a state where it will work well enough to allow basic debugging, and here goes the next big source of instability. i'd have loved to try the stuff over the weekend *without* being forced to... > When we had > <world> > <role id="visit"/> > </world> > > https://svn.apache.org/repos/asf/lenya/sandbox/ac-restricted-1.4-src/pubs/default/config/ac/policies/authoring/index/url-policy.acml > This would mean now that the access is denied. > > So you need to update the subtree-/url-policy.acml to grant the access > @method="grant". > See http://svn.apache.org/viewvc?rev=438944&view=rev how I did it for our > pubs. > > Sorry for any inconvenience. ~X-[ me, too. > I will add some documentation after the merge. and how am i supposed to survive in the mean time? guys, your pace is amazing, but i just can't keep up. and it's really not good engineering practice to drop in a new, totally unreviewed security-critical subsystem weeks before a planned release. why can't this be 1.4.1 stuff in trunk? users who feel adventurous can always svn switch. -- "I don't need backups. I need restore!" - Trad. -- Jörn Nettingsmeier, EDV-Administrator Institut für Politikwissenschaft Universität Duisburg-Essen, Standort Duisburg Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
