Invision Community 5: A video walkthrough creating a custom theme and homepage By Matt Thursday at 04:02 PM
ellawella Posted June 6, 2006 Posted June 6, 2006 First suggestion: Table prefixes :P IBF is surely long deprecated, isn't it? Short for IBforums. Wouldn't the database tables make a whole lot more sense if they were prefixed ipb_ instead? Second suggestion: admin.php says "No administration session found" when you first access it with no session and not having logged in. Well duh! What are we supposed to do about that? :lol: It should only give that error if you actually provide some $_GET variables, not if you've just accessed the file normally. Actually, a bonus suggestion, can we have the username auto-focus on the admin CP back like it was in 2.0.x? :)
Logan Posted June 6, 2006 Posted June 6, 2006 Tiny suggestion yes, but new installations should be ipb_ I agree :P
Michael Posted June 6, 2006 Posted June 6, 2006 I would say making a change to the table prefix is something that won't have any benefit (it'll still work exactly the same way it does now) but could potentially have a lot of problems to change (upgrade scripts having to change all of the table names, timing out, and thus causing errors on the board). Too much risk for no reward if you ask me, thus not something I would bother messing with.Actually, a bonus suggestion, can we have the username auto-focus on the admin CP back like it was in 2.0.x? You mean having the user name fill automatically when you click the link? It still does for me.
Stewart Posted June 6, 2006 Posted June 6, 2006 I believe the default table prefix will be changed in 2.2 or 3.0, but there would be no need for it to apply on upgrades :)
Logan Posted June 6, 2006 Posted June 6, 2006 No there wouldn't be any benefit, FuSoYa. But like Stewart said, there would be no need to change table prefix for the upgrade, only new installations. The suggester is correct though, ibf_ really should be changed to ipb_ as the default table prefix for new installations since IBF is no longer used as an abbreviation for Invision Power Board :P
Quillz Posted June 6, 2006 Posted June 6, 2006 I've found that the conversion scripts only work if you use the ibf_ table prefix.
Stewart Posted June 6, 2006 Posted June 6, 2006 I've found that the conversion scripts only work if you use the ibf_ table prefix. In most cases they work with any prefix, there are a couple of incorrect prefixes left, which will be fixed with the next update :)
Luke Posted June 7, 2006 Posted June 7, 2006 Um... Bad idea! Most manual queries use ibf_ infront of the table name... Then when the query is executed IPB automatically converts ibf_ to the assigned prefix. Changing it would be BAD because it would break any scripts using that. And if im not mistaken, there are some areas even in ipb that do the same thing. The only way I see this happening is if it was the default just in the installer and the scripts use ibf_ and it would simply convert it to ipb_ (as a custom prefix). That way no scripts would have to change. I dont really see the big deal anyway. "Invision Board Forums". Dont remember it every being called that, and changing the default prefix really makes 0 difference in performance... It's just a back side thing anyway... Plus most forum admins, if they care, would change it themselves :) The other idea you have, not sure what you mean exactly :). And as far as I know, AdminCP has been significantly overhauled anyway. It no longer uses session id in the url, and many other changes. So I'm willing to say that was something already on the menu :)
Keith J. Kacin Posted June 7, 2006 Posted June 7, 2006 I would really prefer it not being changed. Just for the simple fact I am used to writing queries with "ibf" in them. :P
Guest Posted June 7, 2006 Posted June 7, 2006 you should write all your queries with the SQL_PREFIX constant then you have no problems if the prefix changes. I think it would be logical to have ipb_ as prefix, although we would have to get used to it. :)
bfarber Posted June 7, 2006 Posted June 7, 2006 The queries with ibf_ hardcoded have been updated (I think mohamed pointed out most of them, and I did a mass search to find the rest in a bug report). I see no point to changing the prefix personally. Maybe in 3.0, but not 2.2. Too much work with no gain.... The 2.2 ACP uses cookies, so the "No session found" does make sense when you first visit it - because you could be auto logged in via a cookie.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.