Would it make sense to decouple preferences from authentication? Currently, the prefs are pulled from the authentication dns. In my set up, I'm authentication against an existing database of user credentials. I don't want to "pollute" that database with wiki related data. Wiki has it's own db where it stores session info and such. The preferences should be kept there as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is already decoupled, you only have to define it.
Simple omit the two PREF SQL statements, then it will be stored in the users homepages.
I don't really want to add another switch to force prefs to be forced into DATABASE_DSN now, maybe later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would it make sense to decouple preferences from authentication? Currently, the prefs are pulled from the authentication dns. In my set up, I'm authentication against an existing database of user credentials. I don't want to "pollute" that database with wiki related data. Wiki has it's own db where it stores session info and such. The preferences should be kept there as well.
It is already decoupled, you only have to define it.
Simple omit the two PREF SQL statements, then it will be stored in the users homepages.
I don't really want to add another switch to force prefs to be forced into DATABASE_DSN now, maybe later.