category-visibility when using multiple installs in 1 database
-
Hi – I searched around to see if someone had asked this before, with no luck, so hopefully this isn’t a waste of time and space … Anyway, my question/problem is with the category-visibility plug-in, which I have been trying to use; however, I keep running into bugs. The good news is that I think I know what the problem is, (BIG disclaimer here that I may be very very wrong indeed) – BUT, I’ve no idea how to fix it – and I was hoping one the many gifted PHP sages might help me out.
Anyway, the problem, I think, is happening because the category-visibility plugin doesn’t add the pre-defined table prefix that can be set during the installation process … it instead just creates the table “category visibility,” with no wp_ or whatever it is set for. That is all good and fine, unless you are using multiple installs in one database, like I am – and I think that is where I am getting the problems. SO – if it isn’t obvious by now – I was wondering what would I need to add to the code to make it find that prefix, then insert it in front of the table name when it creates it? …. also, would I use the same code further in the code, for each call to the table? I can always fixs that part manually, if I have to, but I was guessing that there is probably just a little snippet of code I could use instead ….….On a similar note, should this be a suggestion worthy of sending to the plug-in contest bunch? Perhaps suggesting that ontop of the “guidelines,” if the plugin needs to create a table, that it keep in mind multiple installs in one db, and make sure to query the table prefix if the table will contain data that will “bug-up” multiple installs in one database? Just curious…
The topic ‘category-visibility when using multiple installs in 1 database’ is closed to new replies.