Installation, Configuration, & Upgrades  :: 
PostNuke administration panel (0.7.6.0-RC4) - Error! Sorry!
 Top

  • Error! Sorry! A problem was encountered while loading items

    That's the message - upgraded .750 to .760 went about activating the modules, however now they are all activated, I click on "Administration" and all I get is a "blank" page with that error message and the usual:-

    Programmed articles
    There are no programmed articles
    Last 20 Articles
    Current poll: What do you think of PostNuke?

    at the bottom.

    Any clues?
  • Have you got any categories configured for the admin module?

    --
    Regards,
    Simon

    itbegins.co.uk - Zikula Consulting

    Please read the Support Guide
  • No - I haven't - the installation documentation is a bit vaugue in this area - I take it this is a required step?
  • Initialisation of the categories module should create the categories for you. Try accessing the modules module directly (index.php?module=Modules&type=admin), deactivate, remove, regenerate, initialise and activate the admin module.

    Do you have the NS-Admin directory still in your modules directory? You'll need to remove it if so.

    --
    Regards,
    Simon

    itbegins.co.uk - Zikula Consulting

    Please read the Support Guide
  • No go in that direction - I can't inialize the admin module now, so I am getting "Module Admin not available".

    I can see why it isn't recommended to use RC's on production sites.

    Just as well this is a new site, which we were setting up as a "family" site and we thought it would make a good test bed for our other sites to see any problems we are likely to have with .76, I will suggest that someone look seriously at the documentation that comes with .76, as it's very vague when it comes to upgrading from .75.

    I will hang off and see if there are any other suggestions otherwise I'll toss a coin and either roll back to .750 or delete the database and try a fresh install of .76
  • Are you sure the module is activated? Did you remove the NS- prefixed modules?

    --
    Regards,
    Simon

    itbegins.co.uk - Zikula Consulting

    Please read the Support Guide
  • Quote

    Are you sure the module is activated? Did you remove the NS- prefixed modules?


    The modules/Modules is active still can't intilize the Admin module, and i have removed all NS-prefixed modules.

    Seems a shame to give up on it but a fresh install is looking better all the time.

    Just makes one wonder what I missed in the original upgrade from .750?

    Is there a dummies guide version of upgrade from .750 to .760?

    Would you recommend moving the .750 directory or overwriting - I renamed the .750 directory and then ran install.php however i did notice it didn't give an upgrade from .750 option - is this where i made my error?
  • Quick Update

    Deleted the Database and did a fresh install - no issues this time.

    Still be interested to know what went wrong for future reference, as I have 5 other sites that will need upgrading once .760 becomes official.

    Now to find out which modules don't work.... icon_rolleyes
  • tastiger

    Still be interested to know what went wrong for future reference, as I have 5 other sites that will need upgrading once .760 becomes official.


    Did you read the upgrade instructions in the manual.txt that comes with the RC4?

    --
    "He is not dangerous, he just wants to play...."
  • Quote

    Did you read the upgrade instructions in the manual.txt that comes with the RC4?


    Yes I did - but they aren't exactly the most detailed instructions I have read as you can see:-

    Quote

    9) If upgrading from versions earlier than .723 Run install.php from your browser to start the installation process. The exact URL depends on your site, but for example if your site is www.foo.com
    and PostNuke is installed in the 'bar' directory then the URL will be

    http://www.foo.com/bar/install.php

    Follow the instructions in the installation script and when prompted for
    either a new install or an upgrade select 'upgrade', then pick the version of
    PostNuke (or another Nuke variant) which you wish to upgrade from. The rest of
    the procedure should be automatic.

    10) Once installation is complete you will need to re-add your custom modules and
    regenerate from the modules admin. Due to .760 upgrading the admin module it is likely that
    you will need to go directly to your modules module bypassing the main admin panel - i.e. put the
    URL http://www.foo.com/bar/index.php?module=Modules&type=admin. This is a one-off requirement
    until the admin module is upgraded.

    As part of the upgrade some modules may be ugraded. From the modules admin Upgrade and re-activate
    any modules require it.


    A little line saying something about upgrading .726 and above would be quite handy - as far as I can see this doucument has hardly changed since .075........
  • Just for information sake the following is the exact steps I followed:-

    Quote

    4) Take a copy of your config.php file and store it somewhere safe;
    you'll need it in a minute.

    5) If your uprgrading from a earlier release containing the Xanthia and pnRender modules
    ensure that all cache and compile directories in pnTemp are emptied.

    6) Remove all of the files in your PostNuke distribution. All of them.
    Again a backup of the files would be a good idea, or just move the old
    directory out of the way and install the new one in place of this one.

    7) Take your config.php that you saved a couple of steps ago and copy
    it to the PostNuke base directory (the one with config.php and config-old.php).
    This will be used in the upgrade process


    Which are exactly the same steps that I used to upgrade 5 sites to .750

    I really was looking for more helpful comments than "did you read the instructions"

    Maybe if the instructions were rewritten we wouldn't have nitwits like myself coming to this forum asking why our installations didn't work.

    As it stands I have now found that it was easier in this case to do a fresh install as the module compatability so far leaves a lot to be desired.

    Which was the point of the exercise - as until the modules catch up there is no way my other sites can be upgraded to .760
This list is based on the users active over the last 60 minutes.