I was testing an upgrade from fusion-7.x-2.0-beta2 to the newly released fusion-7.x-2.0 and encountered the following two error messages:
(1) Notice: Undefined variable: node_top in include() (line 101 of (my web site)/sites/all/themes/fusion/fusion_core/node.tpl.php).
if ($node_top && !$teaser):
(2) Notice: Undefined variable: node_bottom in include() (line 120 of (my web site)/sites/all/themes/fusion/fusion_core/node.tpl.php).
if ($node_bottom && !$teaser):
Additional information:
- Drupal 7.31 - all other software is current
- Site hosted at Siteground.com
- It only happens the first time through and only on a full page (does not happen on the home page)
- I do not have any blocks in either node_top or node_bottom
- Using a sub-theme but only made style.css changes and added a local.css (not using responsive layouts)
- The beta version does not have the additional tests for $node_top and $node_bottom and it works fine
Thanks, Rich
Comments
Comment #1
Poieo commentedCan you enable Fusion Starter 7.x-2.0 and see if you still get the errors? There may be an incompatibility between the new release and old sub-themes that needs to be resolved.
Comment #2
Poieo commentedCan you verify that this is happening on a full node page? I think I found the issue where the error would occur if you were viewing a list of teasers, but not viewing an actual node.
Comment #3
speretz commentedThis is happening for me on the front page but I''m not using the default front page. For me this is not an issue with any of my full node pages, just my front page...
Comment #4
speretz commentedAlso, I have replaced my .info file and migrated all my css into local.css so all of the sub theme files should be 100% new from the updated version of the starter template.
Comment #6
speretz commentedSorry to spam you with comments... I tried as an experiment to enable the default front page and it kept happening on the front page, the page I originally had set as the front page when I browsed to it manually AND on the configuration pages! When I set my default front page back to the node that it was originally it went away from the config pages but stayed on the front. Unfortunately I did it in production so I am simply suppressing the errors for now.
Comment #7
Poieo commentedOk. Basically this code in template.php was only making the $node_top and $node_bottom variables available to full nodes:
So, the extra checks in node.tpl.php were failing. I don't think they are necessary so I've pulled them out of the latest dev release which should be available now.
If you could check that release and mark this issue as RTBC, I'll push a 2.1 release.
Comment #8
rchew commentedI enabled the starter theme and it still has the same problem. The test web site is http://svpta.chewdawg.com/. The only page that I have with teasers is the home page and it works fine. If you go to any page node from the main menu, it gets the error on the first time but not after that. New info - if you go from one of the teasers on the home page, it gets the error on the article node every time. To compare, the production site is http://svpta.org/.
I created a new sub-theme (did not just use the old one) and the only changes are to the style.css and adding a local.css. I used the new info file - only changing the description and style.css name.
Thanks for your quick response, Rich
Comment #9
rchew commentedI did a quick test on various platforms (Win, Mac and Ubuntu) and various browsers and it works fine.
Again thanks, Rich
Comment #10
rchew commentedComment #11
Poieo commentedCommitted.