Version 1.5.4 Is Released

[David]

Hi,
 I was using 1.4.x to drive other bits and pieces on a website, and I have just upgraded to 1.5.4 which seems to have broken a bunch of stuff, not least with the change to $username handling the ID_MEMBER and not the username of the user (which presented a bug I had to handle elsewhere)..

Also, is there now some code which meddles with the cookies if the site is run on http://localhost?

Is there a mailing list, or somewhere where the technical details are discussed for changes like this, so that I know what I am getting myself into when I go to upgrade?

Thanks for any information.

There have been a few discussions but all of this was changed in 1.5.0 and 1.5.1.  Take a look in the php scripting board.

[coaxfun]

I am sooo confused.
Trying to figure this out, if you want to *upgrade* to 1.5.4 from 1.5.1 you use the yabbse_1-5-4_upgrade file, correct?
But then, the post says, don't run upgrade.php.... so how do you upgrade?

[PotatoPeeler]

1.5.1 RC1 -> 1.5.1 (update) -> 1.5.4 (upgrade; don't execute upgrade.php)

I am upgrading from 1.5.1 RC1 to 1.5.4 and I have a few questions.  The first is why are there no read me instructions in the 1.5.1 update?  The second is what's the advantages/disadvantages of going through all the updates as opposed to using the upgrade from 1.5.1 to 1.5.4 and vice versa.  Also, what do you mean by (upgrade; don't execute upgrade.php)?

Thanks in advance for your reply.

[Compuart]

The first is why are there no read me instructions in the 1.5.1 update?

probably because no instructions have been written for that specific update version.  

The second is what's the advantages/disadvantages of going through all the updates as opposed to using the upgrade from 1.5.1 to 1.5.4 and vice versa.  

The advantage of the updates is that the changes are relatively small (most updates can be done using boardmod). So modifications made to the original version can (in most cases) be preserved. Upgrade overwrites a lot of files and requires all modifications to be redone.

Also, what do you mean by (upgrade; don't execute upgrade.php)?

Overwrite the current files with the files of the upgrade package. But you don't need to run upgrade.php, as there are no modifications needed for the database (in that specific upgrade path).

[Compuart]

I am sooo confused.
Trying to figure this out, if you want to *upgrade* to 1.5.4 from 1.5.1 you use the yabbse_1-5-4_upgrade file, correct?
But then, the post says, don't run upgrade.php.... so how do you upgrade?

Just overwriting the files with the ones from the upgrade package is sufficient.

[PotatoPeeler]

The advantage of the updates is that the changes are relatively small (most updates can be done using boardmod). So modifications made to the original version can (in most cases) be preserved. Upgrade overwrites a lot of files and requires all modifications to be redone.

Thanks for your reply, Compuart.

I figured that was it but just wanted to be sure.  The next question I have is how do I install an update using board mod if there is not a .mod file included?

[Compuart]

The next question I have is how do I install an update using board mod if there is not a .mod file included?

There's no .mod file for the update to 1.5.1 because there have been published a lot of builds under RC1. For 1.5.2, 1.5.3, and 1.5.4 there is a .mod file (either on the sourceforge download page or in the specific topics in this news board).

[PotatoPeeler]

There's no .mod file for the update to 1.5.1 because there have been published a lot of builds under RC1. For 1.5.2, 1.5.3, and 1.5.4 there is a .mod file (either on the sourceforge download page or in the specific topics in this news board).

Doesn't look like there is a .mod file for 1.5.2 either.  So what do I need to do to update from 1.5.1 RC1 to 1.5.1 and from 1.5.1 to 1.5.2 if there is no mod file?  Just overwrite all the files?

[Compuart]

the 1.5.2 mod is in here. For updating to 1.5.1, an overwrite is indeed necessary (a lot of files too  ) as well as running upgrade.php which is packed with the update package.

[PotatoPeeler]

the 1.5.2 mod is in here. For updating to 1.5.1, an overwrite is indeed necessary (a lot of files too  ) as well as running upgrade.php which is packed with the update package.

Okay, I understand now.  I'll probably just update to 1.5.1 and then upgrade to the newest version of SuperMod.  Thanks for your help!

[Delirium]

do not forget to update this...

Current version:

[[Unknown]]

do not forget to update this...

Current version:

That says YaBB SE 1.5.4 for me.  If it doesn't for you, clear your cache.

I updated that personally before this topic was even started.

-[Unknown]

[PotatoPeeler]

Is this in reference to to my post, you guys totally lost me.

[Meriadoc]

For those of you worried about your heavily modded boards, here's a tip that I hope will help you. I started doing this a while ago when I didn't want to lose modding I'd done.

I keep a log file of all my modifications. Each time a change the code I make an input into this file like this:


---------------------------
My mod name
A comment about what it does
The file(s) changed
the exact or ~rough line numbers

The original information or exact code

changed to

the new code
---------------------------

That's the rough layout. It contains any info I need so next time I update that file I simple go into my mod log, find what I did, get the line number and change the code. Easy-as

hope to have helped,
merry

[charlottezweb]

I just finished manually installing the upgrade with the help of boardmod for two forums...I attribute this to two mods I know conflict with steps 15 and 17:

the IM indicator mod
and
the Hide Sig Images mod

If you have those two mods, I believe you will need to mod by hand.

Also, I had problems with the stats.php file, so I just used the file provided in the update zip instead of using the one I was unsuccessfully modding myself.

Don't know if that will help anyone, but that's my 2 cents.

Overall not a big deal...definitely worth it to be secure