Jump to content

Saving member settings for modules. Best practice?


Recommended Posts

I have some settings for certain modules where each member will be able to define their own. 

In IPS 3.4 I usually saved these in members_cache, but that's no longer used in IPS 4. 

I'm hesitant to add my own database columns to the members table, since it eventually might become quite a lot of them. So what's your suggested approach for this? Should I create my own settings table? And what about member settings I wish to be more globally available? (And not just in a certain area)

I would love your input on the best practice on this. 

Link to comment
Share on other sites

Are these on/off (1/0) settings, or do you need to store textual values?  You could add a bitwise column (you could also use an existing one, but there's always the possibility we will end up needing to use the bitwise flag you choose if you try to use an existing column) which would allow you to store multiple 1/0 settings in a single column.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...