By Jeff Burnz on
For example - look at this: http://www.huliq.com/node/6814
That is supposed to be a node - however, you will see its not, and in fact is returning a list of node teasers, with pager, listing every node in the site.
It is possible that this node was deleted some time ago, I will have to check up on that, however, that wouldn't really explain the current behaviour.
The only clues I have at this stage is a bunch of Watchdog errors:
Type php
Date Wednesday, February 13, 2008 - 01:33
User Anonymous
Location http://www.huliq.com/node/6814?page=3
Referrer
Message Invalid argument supplied for foreach() in /usr/home/websites/content/huliq.com/public_html/includes/common.inc(1342) : eval()'d code on line 5.
Comments
The behaviour would suggest node 6814 no longer exists
The behaviour would suggest node 6814 no longer exists. Drupal when you pass an invalid nid falls back to the path 'node' which appears to be what you are seeing.
/node is the hompage - what
/node is the hompage - what we are seeing here is not the homepage
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
Easy way to check is to...
look at your "nodes" table and see if node 6814 exists.
SELECT * FROM `node` WHERE
SELECT * FROM `node` WHERE `nid` = 6814
Returns an empty set... I pretty much new this node was deleted some time ago. So its confirmed it was deleted, but that still doesn't explain the issue, which you really need to see the url - if /node is the fall back path for deleted nodes, it should show the homepage and not throw an error in doing so.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
Error is probably from a node on that page
Error is probably from a node on that page, my guess is that one of those nodes has the input format set to 'PHP code' and that the code has an error in it. You might visit the 3 page, then click the title of each piece of content and see which one produces the error.
I hear what you are
I hear what you are saying.
I searched the node revisions table and found one node with php input filter, removed that node but that was not the issue (php was just pulling a view we were testing a while back and forgotten about).
The thing is it throws the error no matter what page you are on - doesn't appear to matter if its page 1 or 1101 (I don't really have the time to check 1200 pages). The page 3 was just an example - there are 1197 others the same, which can add up to a shed load of watchdog errors if a bot goes mental on them - but in fact there are way way more since this is not the only URL like this, there are at least 2 others.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.