Upgrade Advice

Client Joined: Oct 07, 2003 Posts: 735 Location: Ohio

This isn't a post for installation help but just a request for advice. I am running a 7.3 site with about 5-6 mods that I really don't want to re-install.

Categories Heirarchy
Attachments
FNA 2.0
bbCode

A few more but I can't remember off the top of my head.

If I wanted to go from 7.3 to 7.7 what would be the best upgrade path?
Are the upgrades inclusive or am I stuck making all the changes to all the files each time I upgrade a version: then run upgrade73-74

rinse and repeat: change files run upgrade74-75, change files run upgrade75-76

etc.

What a pain in the behind that would be!

Posted: Wed Jun 15, 2005 2:33 pm

What features in 7.7 are you wanting or needing that aren't already in the current version you are using?

Posted: Wed Jun 15, 2005 2:42 pm

I am assuming that 7.6 and up (whenever they get 7.7 and 7.8 fixed) are more secure than 7.3

Sentinal 2.1 protects my site along with what security fixes I find posted.

If I just want to keep my forums in 7.3 secure then do I really need to upgrade?

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Donovan wrote:

I am assuming that 7.6 and up (whenever they get 7.7 and 7.8 fixed) are more secure than 7.3

Sentinal 2.1 protects my site along with what security fixes I find posted.

If I just want to keep my forums in 7.3 secure then do I really need to upgrade?

- Just apply the v3.0b fixes from Chat and you are more secure than you will ever be with 7.7 and 7.8.

Posted: Wed Jun 15, 2005 3:01 pm

My understanding is that if your site has the most current patch level from Chatserv and the newest version of Sentinel then you are just as secure as someone running a newer version with the same patch level and Sentinel version, and maybe even more secure as the older versions have been out long enough for more security exploits to have been found and fixed.

Definately upgrade the Forums if you are not already running 2.0.15 BBtoNuke

Posted: Wed Jun 15, 2005 3:02 pm

Dang...Raven beat me to the punch again. *LOL*

Posted: Thu Jun 16, 2005 9:15 am

The thing to remember is that for every version past (Raven, help me out here...I'm guessing since 6.5) every time you see the term, "New Feature" from the PHP-Nuke author, you need to substitute that phrase to be what it actually means which is, "New Bug and Security Hole".

Later version numbers in Nuke mean very little most of the time.

In the latest cases, versions 7.7 and 7.8 equate to extreme risk and much poorer security to the user.

Posted: Thu Jun 16, 2005 9:22 am

- I started with 6.0 and have been patching ever since ROTFL

New Member Joined: Nov 11, 2004 Posts: 16

So just to re-iterate, if Im at a 7.5 "Final" I would be better off just applying the 7.5 level 3.0 set rather than trying to upgrade everything to 7.6/7.7/7.8? Should I also apply the RC1 db performance stuff?

Thank you!

Posted: Thu Jun 16, 2005 10:39 pm

If you are at 7.5, you merely need to update to the latest "Patched" revision unless for some reason you wanted to go to 7.6, in which case you would update, then again load the latest patched revision for 7.6.

Finally, regardless, you should peform the BBtoNuke updates to get to 2.0.15 (Incrementally, in order) which you would also get from NukeResources.com. You should apply the "Patched" revisions AFTER updating to 2.0.15 BBtoNuke.

Posted: Thu Jun 16, 2005 11:10 pm

64bitguy wrote:

If you are at 7.5, you merely need to update to the latest "Patched" revision unless for some reason you wanted to go to 7.6, in which case you would update, then again load the latest patched revision for 7.6.

Finally, regardless, you should peform the BBtoNuke updates to get to 2.0.15 (Incrementally, in order) which you would also get from NukeResources.com. You should apply the "Patched" revisions AFTER updating to 2.0.15 BBtoNuke.

Hi!

Thanks for the response, however it has confused me.
I guess I assumed that the b3 patch for 7.5 included 2.0.15. You are saying I need to go find 2.0.[12,13,14,15] and apply each BEFORE applying the 7.5b3 patch set, correct?

Thanks!

Just to re-confirm, I should grab this: [ Only registered users can see links on this board! Get registered or login! ]
which is the link listed for 7.5 3.0b + BBtoNuke 2.0.15 - 05/13/05

NOT this: [ Only registered users can see links on this board! Get registered or login! ]

and then also apply this:
(Well, I was going to put the link to the RC1 db tuning addon which was here 30 minutes ago and which I downloaded but is now gone. The text blurb said the same as this fix pack only it was for 7.5 not 7.6. The number of new donloads for nuke has also decremented from 16 to 15.:
[ Only registered users can see links on this board! Get registered or login! ]

Acceleration 25% Of Base De PHP-Nuke increase of the speed 30x compared in PHP-Nuke reduction of 30% in low code Global functions (that can be reused for any module) Acceleration 20% Of Base of data Of PHPNuke It replaced all $$dbi called to $$db Applications 50% Little Data base Page Generation: 0,013 Seconds Generation of Header 0.005 eliminated errors (tedious) advanced of the question of the data base Substitution of script for the best operation in hostings gratuitous

but the 7.5 links is now missing. Let me know if you would like me to upload it again.

EAK.

Posted: Thu Jun 16, 2005 11:17 pm

The link was deleted because I am getting about 6 reports a day that the link was broken.

Posted: Thu Jun 16, 2005 11:25 pm

Raven wrote:

The link was deleted because I am getting about 6 reports a day that the link was broken.

You are correct. I actually just reported it as well. Although I don't speak/read italian it looks like they site the link was pointing to has removed all 7.5 related downloads and they are now only 7.6/7.7/7.8.

Thats pretty much a bummer drag.

Other than the db performance tweaks, I should grab the .zip from the link on the ravenscripts home page and apply it AFTER I have manually upgraded my bbtonuke from 2.0.11 to 2.0.15, correct?

Posted: Fri Jun 17, 2005 6:49 am

Okay, I've described this many times before, but I'll do it 1 more time.

The latest "PATCHED" update include BBtoNuke 2.0.15 files; however, it is that way because it ASSUMES that you have already incrementally done the BBtoNuke Updates as they have been released over the past year.

In other words, the FILES of the latest Version of "Patched" will always (unless otherwise noted) be based on the LATEST version of BBtoNuke. The reason for this should be obvious... I mean, you wouldn't want your patched FILES to use an OLDER version of BBtoNuke, especially if your Database tables and fields are already modified for a later version of BBtoNuke... that wouldn't make much sense.

So... To go back to what I said before.

You MUST FIRST install the BBtoNuke updates INCREMENTALLY (in order, 1 at a time) BEFORE updating to the latest Version of "Patched".

If your BBtoNuke is 2.0.10, then you need to get and run BBtoNuke 2.0.10 to 2.0.11: [ Only registered users can see links on this board! Get registered or login! ]

Then 2.0.11 to 2.0.12: [ Only registered users can see links on this board! Get registered or login! ]

Then 2.0.12 to 2.0.13: [ Only registered users can see links on this board! Get registered or login! ]

NOW... When you get to 2.0.13, you need to know if you are running Patched 2.9 or later or not.

If you are NOT running Patched 2.9 or Later then you would download and install
BBtoNuke 2.0.13 to 2.0.14 - For Any Patched Or Unpatched Version of Nuke: [ Only registered users can see links on this board! Get registered or login! ]

If you ARE running Patched 2.9 or Later then you would download and install
BBtoNuke 2.0.13 to 2.0.14 - For Nuke With Patched 2.9 or Later ONLY: [ Only registered users can see links on this board! Get registered or login! ]

Then you would run:
BBtoNuke 2.0.14 to 2.0.15: [ Only registered users can see links on this board! Get registered or login! ]

Remember to upload the files and run the updatedb.php function FOR EACH ABOVE UPDATE in order.

THEN, you are ready to upgrade to the latest patched revision for your version of PHP-Nuke.

Posted: Fri Jun 17, 2005 8:35 pm

How can you tell if you are running Patched 2.9 or later?

Posted: Fri Jun 17, 2005 8:41 pm

Check the readme file that came with the patch, it will list the release dates of versions. If in doubt, run the non-patched 2.9 update and immediately proceed to the next update.

Then when you run the latest "Patched" update, everything will sort itself out because it includes all of the latest files that go with the latest version of BBtoNuke.

Posted: Sun Jun 19, 2005 3:49 am

Thanks for the 'idiots guide' 64bit - I thought I had updated my forums but I hadnt when I checked, was still on a *much* earlier version <cough>.

Like an idiot I just fired off 4 forum upgrades including the DB updates and find I have the much sought after (not!) blank forum admin page - no errors, just white!

So I guees I have to try and backtrack through them now and revert to my older forum and hope the Db changes are not irrevocable.

Posted: Sun Jun 19, 2005 10:30 am

OK found the problem.
The update sequence as posted above is correct however, users should be aware than the final update to phBB 2.1.5 will break any nuke not having the lasted 'patches'.
The culprit is in modules/Forus/admin/pagetart.php
The old pagestart.php starts;

Code:

if (!defined('IN_PHPBB'))


{


        die("Hacking attempt");


}





define('IN_ADMIN', true);


$forum_admin = 1;


include("../../../mainfile.php");


include($phpbb_root_path.'common.'.$phpEx);

and the new pagestart which I assume incorporates some of the latest patched series code says;

Code:

if (!defined('IN_PHPBB'))


{


        die("Hacking attempt");


}





define('IN_ADMIN', true);


define('FORUM_ADMIN', true);


define("PHPBB_ROOT_PATH", $phpbb_root_path);


define("PHPBB_PHPEX", $phpEx);


include("../../../mainfile.php");


$phpbb_root_path = PHPBB_ROOT_PATH;


$phpEx = PHPBB_PHPEX;


include($phpbb_root_path.'common.'.$phpEx);

Posted: Tue Sep 13, 2005 9:08 am

Yup, that would do it.

I should note at this point however that while this problem exists, it does not stop you from performing the updates.

Sure, your forums will stop functioning; however, this is a temporary situation since if you continue the upgrade process to the latest version of BBtoNuke (again, incrementally continuing on, even after this situation where your forums would effectively not work after applying the 2.0.15 patch) you are merely altering the database tables and files to accurately reflect the "state" of each version.

THEN, after that, if you immediately follow up the last BBtoNuke update (at this point 2.0.17) with the latest all-inclusive "Patched" update, THAT Patched update would fix your forums so they once again functioned correctly and would be using the right database revisions.

Again, as "Patched" includes the latest file versions all-inclusively, that last step in the upgrade process would resolve any outstanding issues.

IE... The BBtoNuke updates reach 2.0.15 where they require a certain new level of "Patched" to have the forums run, but that requirement does not prevent or otherwise impact the upgrade process UNLESS you do not intend to run the latest patched revision.

-------------------------------------

Now...In the meantime, I have also posted a suggestion at nukeresources.com that they consider having an alternate set of BBtoNuke updates for Post 2.0.14 versions of BBtoNuke updates that would allow forums to run with lesser patched revisions for those that would want to see forums running before continuining on with updates.

Personally, I think it is a minor issue, but I agree that as it exists, it should be addressed. If nothing else, there could be a comment in 2.0.15 or later (on the downloads screen) that identifies this issue; however, again, as you need to do this BEFORE patched, I would worry that some people might try to update to the latest patched AND THEN run these revisions which would be bass-ackwards and would create problems.

Client Joined: Jul 18, 2003 Posts: 977

Thanks 64bitguy. I think I have it now. Good Guide. These instructuions should be a sticky.