Installation, Configuration, & Upgrades  :: 
Why upgrade from .726 to .750?
 Top

  • What has changed in .750? I see a lot of posts about problems with .750. I have a working site at this point, will upgrading to .750 create any problems? Will not upgrading at this point create problems?

    After upgrading will I find a problem that 'everyone' knows about except me but has screwed up my site, etc?

    Any surprises? Is there a list of features or changes I can look at?

    I apprecitate any comments.

    Joe Dunn
  • ..I'd suggest you create a test site w/.726 install your favorite mods..make sure they're all working and then do the upgrade to .750 (on the test server)..

    ..the only problems I've had is with global variables used in a few modules.

    ex: $GLOBALS['bgcolor1']; should be pnThemeGetVar('bgcolor1');

    ..the removal of global variables and DB optimization (including the persistant connections option) are probably the key elements of .750.. at least in my mind.. others may have certain features they consider key.. but I think these 2 elements add a significant amount of security and performance.

    -IR

    PS: there has never been a release that people didn't have problems with.. even .726.. .750 is an RC.. it is not to be used on a live site.. but merely for testing purposes until a stable version is released..

    --
    http://www.invalidresponse.com
  • InvalidResponse

    ...750 is an RC.. it is not to be used on a live site.. but merely for testing purposes until a stable version is released..


    But every geek like me tend to upgrade all his sites pnconcept, pnf, etc... icon_lol

    The problems I had with core modules were mostly with the Downloads, I had to add some lines.

    I had to go for the PNphpBB2 cause my XForum on PNF wouldn't work anymore (thank god my conversion script)... but it is still not fully repaired, the admin is broken but the next PNphpBB2 will correct this...

    and other little things like that.

    Those problems may have occur because I wasn't really on a fresh install in the first place so I can't say it will happen to all.

    Most lines I had to add were the pnVarCleanFromInput type...

    ;)

    --
    Chestnut !
    Support via Private message won't be answered...
    http://dev.pnconcept.com
    http://www.postnuke-france.org
  • Chestnut

    InvalidResponse

    ...750 is an RC.. it is not to be used on a live site.. but merely for testing purposes until a stable version is released..


    But every geek like me tend to upgrade all his sites pnconcept, pnf, etc... icon_lol


    ..you have "diplomatic immunity".. hahaha..

    ..there are probably a few mods that call pnconfig as a global variable too. as they say though.. "it'll all come out in the wash".. I figured Xforum wouldn't survive the transition..your convert mod couldn't have been timed better.. I did a test run and it works excellent..

    ..okay, I should sleep tonight. ;)

    --
    http://www.invalidresponse.com
  • The key differences in .750 are (from the release announcement)

    1) improved database connection method for reduced resource usage
    2) removal of globals extraction for improved securty and reduced resoure usage
    3) full HTML strict compliance and XHTML compatability
    4) xte bundled
    5) mailer module (allows external smtp servers to be used)
    6) typetool module (updated visual editor)

    Number two is the change that is cuasing the main problems with some modules. Some modules have been developed is a way that assumes the input variable (from the URL) is going to exist. This is bad practice and opens the application to many potential security issues.

    With this release (and moving forwards) modules have to properly obtain thier input using pnVarCleanFromInput. While this change has caused some problems it's vital that this hole was plugged and that the coding standards used in PostNuke modules improve across the board.

    -Mark
This list is based on the users active over the last 60 minutes.