[rosbif]

I've just taken the plunge and upgraded from 9.1.2.1 ro 9.2. All went pretty well except for I few warnings with debugging on.

Ones I have briefly looked at and had no joy with:

Code:

blocks/block-Languages.php
Notice line 107: Undefined variable: content

The variable isn't defined before line 107 where there is a '$content .='. Is it supposed to be a global variable or something?

I also can't for the life of me get my logo to sit on the page properly! Any one give me a clue from the source why this worked before but doesn't now? See here

I also have a few issues with undefined language variables from old modules. Should a module still have a .cfg file?

[Kendle]

The notice is just a notice, you only see it as Admin and it doesn't mean anything, other than PHP being picky because the code should check a variable exists before using it.

[layingback]

Well, no way (now) for me to tell why it worked before, but the issue now appears to be that your logo is too big - tall - for the current header. Guess would be that something has changed in the way the header is placed on the page: margins, something like that, which has reduced its height. So either make header taller, or logo shorter?

You will probably see more Notices under 9.2, simply because more code is using templating. On Pro_News I added code to remove some of these - mostly because I was getting tired of number of users reporting this as a problem - but there are several cases where you either simply can't stop them displaying or, more commonly, where the code to prevent the Notice is bigger than the code it is trying to quieten, so better ignored. Best bet, if you are not a developer or a beta tester is to simply turn off Notice reporting, and leave on just Warnings and Errors.

[Phoenix]

The language block warning is confirmed as a minor bug - please Report Here.

It was also present in 9.1.x versions.

Your theme issues should be handled separately to that with the theme author, and similarly your module issues handled with the module author concerned - both of which are separate topics.

I'm moving this topic to "Problems after Install/Upgrade" and locking it as a bug topic.