Joeychgo 07-30-2007, 08:30 AM Unfortunately, as of this post, the 3.6.8 package in the members' area has been updated to provide fixes for several 3.6.8 specific issues. See below for a list of issues addressed.
The following files were updated:
admincp/modlog.php
includes/functions.php
install/vbulletin-style.xmlSimply re-download the package and manually upload those 3 files over top of the existing ones. You should then re-import the master style to gain the fixes to 2 affected templates. To do this, log in to your admin control panel, go to Styles & Templates -> Download / Upload Styles -> Import Style XML File -> "Import".
Alternatively, you can manually apply the fixes for each issue by viewing the appropriate bug report:
Moderator log viewer database error (http://www.vbulletin.com/forum/project.php?issueid=22777) (Affected file: admincp/modlog.php)
URLs in custom BB codes broken by word wrap (http://www.vbulletin.com/forum/project.php?issueid=22752) (Affected file: includes/functions.php)
Editor size shrunk by large smilies box (http://www.vbulletin.com/forum/project.php?issueid=22747&page=2) (Affected template: editor_toolbar_on)
Quick reply editor overflows containing box in Internet Explorer 6 (http://www.vbulletin.com/forum/project.php?issueid=22745) (Affected template: showthread_quickreply)We apologize for any inconvenience caused.
More information might be posted at vBulletin.com: http://www.vbulletin.com/forum/showt...28#post1399028 (http://www.vbulletin.com/forum/showthread.php?p=1399028#post1399028)
Discussion of the vBulletin 3.6.8 release on vbulletin.org: vBulletin 3.6.8 Released (http://www.vbulletin.org/forum/showthread.php?t=153466)
This thread closed for further discusion.
More... (http://www.vbulletin.org/forum/showthread.php?t=153794&goto=newpost)
Peggy 07-30-2007, 08:39 AM aww geeeeeeeze...
Joeychgo 07-30-2007, 09:31 AM Just uploading 3 files - no biggie.
I wish they would have more updates that didnt require template changes.
Peggy 07-30-2007, 09:49 AM are there template edits in this package update?
DieselMinded 07-30-2007, 10:11 AM WHEW !!!!!!! Glad i waited ..AGAIN !
DM
redraider 07-30-2007, 10:41 AM AAAAAAH! My whole Sunday went in dumps ... ... :moods: :groan:
Oh well the swimsuit advertisement (above quickreply) helps :p
Swerve1000 07-30-2007, 02:45 PM WHEW !!!!!!! Glad i waited ..AGAIN !
DM
I know! Just made it by 5 hours! this would of been the end of sanity for sure.
Peggy 07-30-2007, 02:56 PM naw - the fix released today took all of about 3 mins to do. No template edits
Big Dan 07-30-2007, 04:53 PM I guess back to back updates are the norm now. :(
Peggy 07-30-2007, 04:55 PM this is really nothing tho. Just uploading three files, not the whole package, and importing the main style's xml file.
Big Dan 07-30-2007, 09:07 PM this is really nothing tho. Just uploading three files, not the whole package, and importing the main style's xml file.
I know that. :) The past two upgrades have offered no new features to the end user.. Basically they were to add template hooks for the new paid addons system.
Lets see you release an update, make us edit our templates to accommodate something that most of us aren't going to use. Not once, but twice.
Then after you release the first update, you release a patch with in the next couple of days to fix something that was supposedly the fixed with the update we just did.
Second time around you release an update with bugs.
Today's update wasn't that bad the hardest part was reimporting the default template. The update for 3.6.7 to 3.6.7PL1 wasn't bad either.
It just makes updates seem very rushed. Perhaps instead forcing everyone to update and waste time with useless template edits, they should compile two versions. 1 for people who are going to use addons and one for those of us who could careless about the addons. It would make life a lot easier for the majority of admins, most of which aren't going to bother with the addons.
Hell³ 07-30-2007, 09:26 PM Considering the template hooks will be there for any dev to use, I don't think it's feasible to support two separate products, instead I think a more rigorous quality assurance process is due.
Granted, the upgrade process in vbulletin is unmatched by any of the other forum dev softwares I've had the chance to use, but that doesn't mean the process is not time consuming and at times really frustrating. Specially for the modified forums, and even for the ones with "just" a style change.
I learned about this upgrade while i was away from home, so i thought, "well, at least it's not a critical upgrade, so I'll wait a week to see what cooks in the meantime", and it seems I was right.
Peggy 07-30-2007, 09:36 PM I know that. :) The past two upgrades have offered no new features to the end user.. Basically they were to add template hooks for the new paid addons system.
Lets see you release an update, make us edit our templates to accommodate something that most of us aren't going to use. Not once, but twice.
Then after you release the first update, you release a patch with in the next couple of days to fix something that was supposedly the fixed with the update we just did.
Second time around you release an update with bugs.
Today's update wasn't that bad the hardest part was reimporting the default template. The update for 3.6.7 to 3.6.7PL1 wasn't bad either.
It just makes updates seem very rushed. Perhaps instead forcing everyone to update and waste time with useless template edits, they should compile two versions. 1 for people who are going to use addons and one for those of us who could careless about the addons. It would make life a lot easier for the majority of admins, most of which aren't going to bother with the addons.
yep yep I get where you're coming from hun. ;)
popowich 07-30-2007, 10:37 PM EEK! :eek: I agree, please don't fork vBulletin into 2 separate projects.
-Raymond
Big Dan 07-30-2007, 11:36 PM Considering the template hooks will be there for any dev to use, I don't think it's feasible to support two separate products, instead I think a more rigorous quality assurance process is due.
True the template hooks are for use by anyone, some of the mods on the .org are already utilizing them. It's probably for the better, although I already moved one of the hooks to make a hack work like it did before template hooks.
On the other hand, what about those of use who've already made template edits for hacks? It sure makes for a lot of confusion for those who don't realize some hacks auto-edit templates and you have to go in and remove the old code.
Once everything gets ironed out and everyone moves over to the new system, everything will be a lot smoother but in the mean time we're stuck with upgrades just for the sake of upgrading.
EEK! :eek: I agree, please don't fork vBulletin into 2 separate projects.
-Raymond
Don't worry no one's listening to a rambling DJ. :D
|
|
