Not doubt, I couldn't agree more. My porting is going very well. I have my installer done for vBGarage and the new group permissions integrated. I have to go through the main file now and the templates. My little add in enhancements will be a breeze.
Got a question for you all. I plan to not reinstall a few hacks. When I do upgrade will the changes made by some of the hacks to mysql ruin the upgrade?
This is probably the only time I'll get away with saying, If you can do it, so can I. But I'm still scared. Got more code to port for these darn hacks.
Yeah, I powered through my stuff... turned all the customizations here into 17 plug-ins, and was able to empty most of the phpinclude_start template as well. So I'm pretty happy with it. It's a really nice feeling once you get everything ported to the plug-in architecture. I was able to eliminate touching all source PHP files except for 2, and both of those it's just one line of code being added. I put in 2 requests for new hooks (where I have to hit my 2 files), and I think I might get one of them. Probably 50/50 on the other. Would be REALLY nice to not hit any .php files.
Oh... BTW, here's something nifty I just found with 5,000+ emails in my mailbox... Make sure your database user you use for the forum has access to the LOCK TABLES privilege. I run everything with minimum permissions (for security) and apparently it's new in 3.5. Not a fatal error (I would have noticed if it was), but it looks like it tries to lock the mail queue DB (a good idea) when it's sending email. Anyway... maybe that will save someone else 5,000 emails.
I'm a new to vbulletin, how long do they normally wait to promote the beta unstable version to stable?
Only if they created database fields or tables that are a conflict. The best thing to do would be to check with the specific authors.
I'm still doing vBGarage. I figure that should teach me every aspect of the changes when done. I'm real close. Then I got vBIndex to check into and the Shoutbox hacks. Both pretty darn big addins. I have no clue if the authors are gonna do um. P.S. $gagage is a very very very hard typo to catch for garage, even with it misspelled in 8 places from cut and paste! :/
One nice thing I finally realized towards the end of porting everything to plug-ins is that the exit; function works (it doesn't in phpstart_include) so makes debugging handy. I did a lot of this type of thing with my plug-ins to figure out what objects/variables were available: print_r (get_defined_vars()); exit; PHP:
Thanks for the tip. I used alot of echos with exits to debug. As of now, except for letting someone else try, vBGarage is ported and working as a new install. I have to write the upgrade proceedure. Was a good upgrade, I learned alot.
I just dug into the new ability to send the datastore table to shared memory. Damn is it cool! Especially nice if your web server is separate from your database server. Can send it to a file or shared memory on the web server for fast access. For shared memory, one of the options they support is to utilize Turck MMCache. But I don't use Turck because it's outdated (I use eAccelerator). Anyway... long story short, is I simply added an eAccelerator sub-class to the datastore class, and viola! works like magic. I hope vBulletin adds an eAccelerator sub-class to the distribution so I don't have to add it each time. Either way... the local datastore stuff is awesome. Now they just need to do that with the template database.
That is very nice. Large installations will appreciate it. I may have to use it if all 10 of my users logon at once, but for now, I'm ok.
Another cool thing about the shared memory stuff is now I can actually see how easy it is with eAccelerator... so I'm probably going to do something similar for the ad network ad server.
Now that's cool news. Though having very small installations currently, I would think at first those things would be of no real benefit to me, however a little can mean alot sometimes. Is this dedicated server stuff only? I know the mmcache stuff is from when I had an actual server last year, but now I'm on shared hosting. I ask because I am considering sharing a dedicated which of course I'll get to tweak or perhaps my own Virtual Private Server. Thanks for the replies, you find interesing things.
No offense or anything, but I think the new method of getting quick reply to work really sucks and is non-intuitive (especially for brand new visitors to the forum and those non-techie types). Why not just keep it the way it was before.. (if it aint broke, don't fix it) People will have to guess what the hell a quick reply button is. Very confusing and low usability factor IMO.