-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi all-

I recently updated several wikis from MoinMoin 1.5.7 to MoinMoin 1.6.3 
on RHEL 5.1, Python 2.4.3. At the request of our security guy, I also 
changed user authentication so that instead of using their MoinMoin 
CamelCase wiki account usernames, wiki users are authenticated using 
their ActiveDirectory usernames and passwords. So typically, usernames 
like GregButler are now gbutler.

However, I now have some user complaints that they are having error 
messages when they log in, such as:

AttributeError: User instance has no attribute 'aliasname'

...and that when they edit and then save changes to a page, when the 
page refreshes, their edits are lost.

I'd like to make a clean break between the old account names & profiles 
and the new info, if possible. I am wondering if any of these problems 
could be caused by users who are logging in with their old wikiname 
accounts, even after we have set up the new AD accounts for them. Is it 
possible that there are conflicts between cached old usernames and 
profile info in various places? If so, are there old cache items I can 
remove that Moin will re-create automatically? For instance, can I 
remove the:
/data/event-log file
name2id file
entire contents of /data/cache?
any other files?

Thanks for any help in understanding this!

Greg


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
 
iD8DBQFIc9gY8IR34NeP2BwRAhs9AJ45slwqcSZRek5XXL1f1PtRpewQ/ACggvd9
wKbZpxS3Txx4DzWfcsD6J6Y=
=7Zgg
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Moin-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/moin-user

Reply via email to