Thread

Hey I just upgraded a site from 1.6.2 to 1.6.9 and i am getting multiple errors.  Odd thing is the site displays fine except for the error messages. Any ideas as to how to track down the problem.  I have double checked that the weblog module was updated.  Here are the errors i am getting.  I removed the first part of the path in the errors for security reasons.

Notice: Undefined index: uris in /modules/weblog/mod.weblog.php on line 1537

Warning: array_flip() [function.array-flip]: The argument should be an array in /modules/weblog/mod.weblog.php on line 1537

Warning: implode() [function.implode]: Bad arguments. in /modules/weblog/mod.weblog.php on line 1537

Notice: Undefined index: uris in /modules/weblog/mod.weblog.php on line 1537

Warning: array_flip() [function.array-flip]: The argument should be an array in /modules/weblog/mod.weblog.php on line 1537

Warning: implode() [function.implode]: Bad arguments. in /modules/weblog/mod.weblog.php on line 1537

Notice: Undefined index: uris in /modules/weblog/mod.weblog.php on line 1537

Warning: array_flip() [function.array-flip]: The argument should be an array in /modules/weblog/mod.weblog.php on line 1537

Warning: implode() [function.implode]: Bad arguments. in /modules/weblog/mod.weblog.php on line 1537

Notice: Undefined index: uris in /modules/weblog/mod.weblog.php on line 1537

Warning: array_flip() [function.array-flip]: The argument should be an array in /modules/weblog/mod.weblog.php on line 1537

Warning: implode() [function.implode]: Bad arguments. in /modules/weblog/mod.weblog.php on line 1537

Any help with this would be greatly appreciated and obviously this is fairly urgent as the site is currently offline.

PhilBrienesse,

Take a look at the version notes for 1.6.9
http://expressionengine.com/legacy_docs/installation/version_notes_1.6.9.html

Are you using any of the Add-ons listed? Structure, LG Better Meta or the Nested Menu Plugin.
Be sure to update there if you do.

No I don’t have any of those installed and i did try disabling all extensions which are limited.  Upgraded fieldframe and wygwam but those are only used in one limited area. 

Only thing that seems to help is to uninstall the actual pages module then i get no errors.  Only problem is this site relies on it heavily (i didn’t build the site btw) so that is not a sollution.  I double checked that it has the version of pages from the 1.6.9 install.

Site is back up online now as it only shows errors to super admins and everything else works perfectly fine as far as anyone viewing the site goes they would never know there was a problem.

Still i would like to get it fixed.  Any other ideas?

PhilBrienesse,

Can you confirm whether these errors were on the front or back end?

Do you have LG .htaccess generator installed?

Do you have a value for URL to the root directory of your site under CP Home ›  Admin ›  System Preferences ›  General Configuration

Also please confirm that you did a version update as opposed to a build update

Hey John,

They are front end errors.  I am not using lghtaccess but I am replacing index.php using my own htaccess file which I have never had a problem with on any other site.  Just to see i removed that and switched to using index.php and still get the error.

Yes this was a version update not a build update.  Went from 1.6.2 to 1.6.9 (big jump i know).

I am going to try replacing the themes folder as well and see if that does anything although i can’t see how it would be related but i am realising it is one of the things i didn’t do as the instructions simply say to back it up.

If that fails I’m going to let this go as is.  People visiting the site don’t see any errors and I have just been told there are plans to redesign this site and switch to 2.x within a month or two so its probably not worth my or your time to track it down any further. 

Thanks for your help.

Hi PhilBrienesse,

Have you you resaved the Pages module configuration since doing the upgrade? If not, please try doing that and also please try resaving one of the affected weblog entries that has a Pages URI assigned to it.

Cheers

Greg

Tried both of those already and just did again to double check.  Still same errors.  Very baffling for sure.  Like I said in my last post not going to spend a whole lot more time tracking this down since the plan is now to upgrade to 2.x with a complete redesign.

Thanks for the help and suggestion though.

OK. If you want to revisit this issue at some point, or run into any other problems please do not hesitate to start a new thread.