Fork me on GitHub

News Module upgrade gone bad  Bottom

  • I wanted to upgrade the news module from 2.4.1 to current so I did. I did not catch the fact that I must upgrade Zukila from 1.2.3 to 1.2.4 first so now I have a broken news module that the whole site is based on.

    Any ideas on how to fix this without doing a total restore from backup?

    The errors I get at the moment are

    Sorry! Could not find the page you wanted on : '/index.php'.

    The 'News' module is not currently accessible.

    Can I simply restore the old news module files or did the module upgrade make modifications to the database?
  • Yes there are modifications to the database and module variables. I think the most straight forward solution would be to put back the backed-up news table and the 241 files and go from there.
    There is even a rename of the database table from prefix_stories to prefix_news. And a permission scheme update from Stories::Story to News:: and several other things.

    News 262 should work also in zikula 123 I think. I have not tested it as such, but I think it should work. So why you get the errors seems a bit strange.

    --
    campertoday.nl, Module development, Dutch Zikula Community
  • I restored the 241 files and database table, all is well.

    To upgrade the new module you simply copy the new files, regenerate modules list, then activate the news module?
    Joe......

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