Re: [Phpwiki-talk] can't unlock pages in CVS build and much more

[Stefan <son...@ba...>]

Hello i have to be more speciffic sorry

Reini Urban schrieb:

> Stefan schrieb:
>
>> in the cvs version it is not possible to unlock pages.
>
> I already said that current pagadata cache is unstable and needs some 
> more days to stabilize. This was also reported three days ago by 
> Charles Corrigan.

oh thats fine thanks

>> I've also tried to use the acl to set page permissions. does anyone 
>> know how to handle this tool? i can change what i want but nothing 
>> really happens. the right managment is much to difficult and buggy to 
>> use it.
>
>
> I see no other bugs than the current pagadata cache problem. I'd be 
> happy to receive bugreports.

have a look at this please: try to change the settings of a page that 
only authentificated users can see the page
maybe i did'nt understand the syntax.  i have tried it more than one 
hour on every way i found but it happens nothing that works.

>> sorry that i tell you this, but in my opinion there are to much 
>> plugins and features in this wiki but the base and the usefull 
>> plugins are to buggy to use them at all. you should first fix bugs in 
>> the base system before makeing anything else. i read about new 
>> features and themes but the really usefull things are not present or 
>> do nut function correct.
>
> The current bug list is pretty empty.
> I only have some outstanding php5 and apache2/IIS issues.
> See my TODO list which I mailed 2004-12-04.
> Subject: "browse page and plugin/WikiAdminSelect.php show different ..."
>
>> -Rightmanagement
>
> There are only outstanding issues with http auth.

see problem bevor. did'nt meen user auth

>> -Changing a lot of pages with sql and update cached versions
>
> This has to be done. Some changes are still pending.
> The original architecture was okay for big servers and small wikis:
> < 500 pages.
> I have to fine-tune the caching system now,
>   too much wasted memory <=> too much unneeded db queries.
> You reported 2 Gig RAM for a big request. This must be fixed.


Yes i know it is fixed ! Very very good job! The wiki is very fast also 
thank you

I often have to change 4000 pages at once. This can be done making an 
sql to change all pages in the "version" table.
But it's useless because the "page" table  always do have the unchanged 
versions until i open and save every page again.
To clear the cache is useless. i have to rebuild the hole "page" table 
again but how?

>> -Backlinks did'nt work when link is part of a plugin
>
>
> This is an architectural problem. Links created by plugins must be 
> known at save-time and are only saved at save-time.
> We don't want such dynamic WikiDB hooks yet. It will cost more time 
> and more memory with little benefits.
>
> Most plugins are simple and just store normal pages, which are of 
> course correctly backlinked.
> The only exceptions are Calendar and CalendarList, and I fixed a part 
> of the problem yesterday.

RichTable Plugin

Page Test1

<?plugin RichTable
*border=0, cellpadding=1, bgcolor=#ffffff, align=center, width=99%
-
|[OtherPage]
?>

when you save this page the link [OtherPage] is known. If you to page 
OtherPage ans press backlinks, the page Test1 is not shown in the backlinks.

>> -Seperate database for auth and data (only partially there)
>
> This is fully implemented.

the prefs tables has to be at the same db as the auth table. Maybe 
sometimes usefull but not when verifying against an external userstore.

>
>> -HTML Dump stops when plugin needs to much time
>
> Thanks for the report. We will extend the timeout to 20 secs per page. 
> and not 240 secs per request.
>
>> -Users homedir is always his userid why there is no subpage like 
>> /users/userid to move them from root
>
>
> Sorry, we will not be able to fulfill this feature request until the 
> next major release. You can hack it by yourself. It will be very easy.

You are right this is a feature with less priority
Can you tell me where i have to change it? I've tried it but im not so 
familiar with the code nad it would be a good feature for the users.

Thanks for your help and information, sometimes it's to much to do for a 
lone <se?p=/Mn4k.&search=lone> fighter <se?p=/Mn4k.&search=fighter>.

Regards Stefan