On Tue, 2005-10-04 at 16:39 -0500, Zed Pobre wrote: > Well, for starters, you might want to put out a guide on how to run > the upgrade script manually, since the upgrade path doesn't even > attempt to find any wikis you might have running in parallel. One > thing to note there is that for some strange reason the locales > directory cannot be a symlink to /usr/share/phpwiki/locales for > additional PHPWiki locations. The system throws a nasty error if it > is, and I have absolutely no idea why, since if you cp -a the > directory, it works perfectly fine without change.
Good point on the parallel installs. It is a use case I had completely overlooked, I've only recently adopted the package so I hope you'll forgive some initial omissions like this :) The script is installed to /usr/share/phpwiki/migrate-phpwiki-config if you haven't found it already. Run it without arguments for usage help. A configuration template for use with it can be found at /usr/share/phpwiki/config/config-template.ini Needless to say it's added to the TODO list of things to tidy up. Did the migration script work correctly for you other than these issues? I'm particularly interested in whether it managed to get the majority of your settings across to the new config file without problems. > I've attached config files for both wikis, which both work to read, > but both fail in different ways when trying to auth. I've also > attached my apache.conf. Please don't mind all the commented-out > stuff and things related to the coh wiki -- those are the results of > quite a bit of testing trying to find something that would work Hmm, I think the problem is that you do not have php4-imap and php4-ldap installed on your system. Can you verify this is true? I'll need to think a little about how to handle this, I don't particularly want to make the package depend on these as I imagine that the external IMAP / LDAP auth functions are not used by the majority of users. Would you consider a Recommends: php4-imap and php4-ldap plus enhanced documentation in the config file etc to be sufficient to address this bug? This would be a similar situation to how we currently handle other extensions such as mysql and postgres that require user modifications. Regards -- Matt Brown [EMAIL PROTECTED] Mob +64 275 611 544 www.mattb.net.nz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
