Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /home5/lovetess/public_html/robertbarrington.com/includes/menu.inc).

I'm not sure what module caused this error, but if I let it go it grows an eventually destroys the site.

Comments

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented
Status: Active » Postponed (maintainer needs more info)

Please explain at what point during the Drupal installation process this message first appeared.

(It seems likely it was due to incorrect code in a contrib module or install profile, but to find out which one it will be necessary to understand exactly what you were doing when it occurred.)

barbank’s picture

barbank CreditAttribution: barbank commented

Eureka, I found it. In the first situations I had no ctools enabled and I was trying to update pathauto with the token module enabled and installed, disabling the token module, updating pathauto (it re-enables the token module itself) the problem disappeared. Now I have a new issue with the same message when I try to enable panels. So, it just sits there and anything that depends on is sitting idle. Panels-2 is a monster. I can't make head or tails of the documentation on the developer's site.

Perfect, I had uploaded some added functionality via contributed modules and when I checked the boxes and tried to save, I got this error. Furthermore, about half the new modules I tried to activate at that time, about five or six, ended up unchecked after the save. If I uninstall the installed contributed modules one at a time will that make the issue worse? If not, I can uninstall the modules one at the time and check each one.

I hope you don't mind another question, but on my 6.2 installs I have a developer profile site set up where I check each new module or update before I use it on a live site. My introduction to Drupal, or even the concept of a CMS began last September. I'm not an expert. Any idea where I can get the same developer profile for 7.0?

Thank you for taking the time.
Robert

PS As soon as things smooth over for me here, I'd like to help document some of code, any code. That would a big teaching aid for me and a way to pay back something at the same time.

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented

Hm, I could not reproduce any problem with Ctools and Panels when using the latest Drupal 7 versions of those modules... However, when I tried it with a Drupal 6 version of Ctools (but the correct Drupal 7 version of Panels), I was still able to start the installation of Panels, but things exploded. Is that what happened to you? (I can't really tell from your description what versions of each module you tried to install and in what order.)

In any case, that seems like a bug in Drupal core. If Module A requires Module B, having a D6 version of module B around shouldn't be enough to allow you to even try installing Module A. We should fix that, regardless of whether it's the bug you experienced or not :)

I hope you don't mind another question, but on my 6.2 installs I have a developer profile site set up where I check each new module or update before I use it on a live site. My introduction to Drupal, or even the concept of a CMS began last September. I'm not an expert. Any idea where I can get the same developer profile for 7.0?

Where did you get the Drupal 6 version of this profile from - did you download it from somewhere? It should be possible to update the code for that profile so that it works with D7, but depending on what it does that may be hard or easy.

PS As soon as things smooth over for me here, I'd like to help document some of code, any code. That would a big teaching aid for me and a way to pay back something at the same time.

That would be great - thanks!! http://drupal.org/contribute/documentation is the place to start to look for ideas on what to work on. Feel free to ask me if you have any questions.

barbank’s picture

barbank CreditAttribution: barbank commented

I downloaded it from the Drupal site. I see strange 6.20 to 6.9 are we moving six to 7? Anyway the install is solid otherwise. One more question, if I may. Is the difference between the 6 and 7 only the API? If I write a module withe 6.2 and using 7 API is that all it would take?

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented

If you downloaded the profile from drupal.org, then you can check the profile's issue queue to see if there is any work being done on porting it to Drupal 7.

The differences between Drupal 6 and Drupal 7 include the API, user interface changes, coding standards, etc. If you develop a module using the Drupal 7 API, then the module is for Drupal 7... The same exact code is very unlikely to work in Drupal 6.

barbank’s picture

barbank CreditAttribution: barbank commented

Good to know, and David, I would probably opt to document the API, but I'll not be ready for two or three months, unless I can do small items that I could squeeze in from time to time. Unless I know how small is small, I can't say. I've been cleaning up the documentation on the development modules, just so I can understand the Doxygen rules and I have to tell you that in cases of @see and some other things, I could not understand how to do int right. I still can't fix it so it does not generate the little "minor" button and the code segment.

Thanks for the quick answer.

PS. I have an old broken down 6.19 install that today I discovered someone installed and published fetchgals on. It definitely was not not me. No one can get into the site, even me, unless they jump directly to administration. I left it running because I wanted to see how they did it. Anyway there is nothing on that host but a junkyard of broken sites. Am I being foolish? Besides, I like pretty girls.

Geijutsuka’s picture

Geijutsuka CreditAttribution: Geijutsuka commented

This may be a duplicate of this issue:
http://drupal.org/node/972536

barbank’s picture

barbank CreditAttribution: barbank commented

Same error message. I don't know how we got switched, but I looked at my notes and it was a Drupal 7.0 install. The error was gone after I disabled panels. I still have it disabled. Nodequeue is alive and well.

Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /home5/lovetess/public_html/robertbarrington.com/includes/menu.inc).

when I tried to enable views contact panes. I get two more errors when I disabled it, and they went away when I uninstalled it.

fndtn357’s picture

fndtn357 CreditAttribution: fndtn357 commented

I developed this issue after I disabled the Forum module. Yes, the Forum module was set to be a menu item under Home. I did not think to unset this before I disabled the module.

Using: CTools - 7.x-1.0-alpha2, Date, Coder - 7.x-1.0-beta6, NodeQueue - 7.x-2.x-dev, Entity - 7.x-1.0-beta6, Node Privacy by Role - 7.x-1.x-dev, Rules - 7.x-2.0-alpha4, and Views - 7.x-3.0-alpha1.

This message occurs after saving any View changes:
Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /../../../../includes/menu.inc).

After enabling a new module this message appears twice:
Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /../../../../includes/menu.inc).
Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /../../../../includes/menu.inc).

It appears that this message occurs after every write to the database. Maybe I am stating the obvious but I am a newbie and just documenting what I see.

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

Let's mark this as a duplicate of #972536: Object of class stdClass could not be converted to int in _menu_router_build() - line 3370 (the issue linked to above) and continue any discussion there.

@fndtn357: Your report sounds interesting. I could imagine this having something to do with a disabled module's menu items not being disabled correctly. Please post on the other issue if you can come up with an exact set of steps to reproduce (starting with a fresh Drupal installation) - I tried to reproduce this with disabling the Forum module after having customized the Forum menu item in various ways, but I wasn't able to trigger the bug.

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented

By the way, the side issue I noted in #3:

If Module A requires Module B, having a D6 version of module B around shouldn't be enough to allow you to even try installing Module A. We should fix that, regardless of whether it's the bug you experienced or not :)

looks like it already has its own issue at #1002258: D6 modules satisfy D7 module dependencies.