Get this on many page loads, not sure what the error exactly means or what gets broken, anyone get the same error or know how to solve this?

Comments

dwees’s picture

dwees commented

I am having the same error. I have exactly 1 panel page at the moment, but it's my front page so fixing this error is important. It does seem to affect the functionality of my site in anyway however.

The error appears to show up whenever I navigate to my front page.

I also noticed that when I had panels node enabled, I had 2 new tabs on all of my nodes (not just nodes of the type panels), "Panels layout settings" and "Panels content", both of which seemed like they were showing up because of the error in question, which is why I mention it. Oh and access permissions to these tabs were non-existent, they were available to anonymous users despite the permissions in admin/user/access.

I think this 2nd error is related to the problem mentioned here.

Christopher Herberte’s picture

Christopher Herberte commented

I'm getting lots of these too. Not effecting the panels page borks on empty $menu in panels_page.menu.inc any clues?

cpelham’s picture

cpelham commented

same here.

lega’s picture

lega commented

same here!

However i noticed that on the recent log entries when i couldn't access my modules page after installing CCK - text field!

Well I have no clue whats going on..

cheers

sdboyer’s picture

sdboyer commented
Category: bug » support
Status: Active » Closed (won't fix)

So, some clarification at least - this error occurs when _something_ goes wrong with the creation of the fallback routers (the mechanism we currently use to allow you to have, for example, some node types on node/% be rendered by panels, and some by the normal node rendering process). Unfortunately, the code is copied more or less verbatim from the menu system itself, and the way they do it, that watchdog error occurs at a point where it's impossible to tell WHAT routers have actually caused the error. I could rewrite it so that the error message was more informative...but that's six hours of grok, coding, and testing time that's really much better spent elsewhere. What I CAN say is that this the underlying issues this watchdog entry points to are indeed the ones that are being raised in other issues in the queue right now. Consequently, isn't a 'bug report' so much as a 'what does this watchdog error mean?' question - so I'm changing it to support request and marking it by won't fix.

I may beef out this error message simply so that it has the names of the router items that it's trying to store, but I still really only put this in because I wanted basically a binary indicator saying "panels menu rebuild iz borkered!", or not.

prodosh’s picture

prodosh commented

Does this mean that site admins should ignore this message and not worry about it?
TIA

andyboutte’s picture

andyboutte commented
Version: 6.x-2.0-alpha2 » 6.x-2.0-alpha3

I am also getting this a lot. Anybody know if this is something to worry about?

lacitpo’s picture

lacitpo commented

Would be interested to know as well if this is something it's ok to ignore.

natrio’s picture

natrio commented

subscribing

Steel Rat’s picture

Steel Rat commented

Ditto on these errors. No apparent effect on the site, but annoying to have so many cluttering up the log.

asak’s picture

asak commented

same here. subscribing.

virtualgirl’s picture

virtualgirl commented

specialized Panels menu router rebuild failed
this is disturbing
it messes up the panel you build with different views, it doesnt port out
i cant figure it out
I uninstalled mods and cla\eaned database thought it was from the upgrade but this is a cryin shame wher is th elil blue drupal smurf?

sonicthoughts’s picture

sonicthoughts commented

me too... no idea why...

asak’s picture

asak commented

This is driving me crazy...

ligius’s picture

ligius commented

I am getting the same error and it happens after running the cron.

spangaroo’s picture

spangaroo commented

I just built my first Panel + Views combo today and saw this message as well. It showed up after I upgraded Imageapi and Imagecache. Doesn't seem to affect the site right now because my panel is just 2 columns...but if a fix is released I'll upgrade asap.

ligius’s picture

ligius commented

Yeap, after upgrading all gone.

stompersly’s picture

stompersly commented

ligius, Are you saying you no longer get this error. I am wondering what you upgraded to fix the problem can you please explain so others can benefit.

I am using the following and I still get these errors:
Drupal 6.10
Views 6.x-2.5
6.x-2.0-alpha3

Thanks for your help, StomperSly

dhingchak’s picture

dhingchak commented

i am getting the same error.

drupal_jon’s picture

drupal_jon commented

subscribing.

marcoBauli’s picture

marcoBauli commented

in the queue too :)

nestor.mata’s picture

nestor.mata commented
Priority: Minor » Critical
Status: Closed (won't fix) » Active

Why you set it to don't fix if many people is getting the error?
Let us find a way to solve this, please and not just run away from us.

Thanks

sdboyer’s picture

sdboyer commented
Status: Active » Closed (won't fix)

@nestor.mata: my above comment in #5 explains why this is won't fix, and why I'm won't fixing again - please don't change the status again.

Here's a two-bullet summary:

  1. This error showing up in watchdog could point to one of any of a dozen, maybe two dozen, maybe even more problems. It is _impossible_ to know simply from the error itself, and is therefore a waste of time to have people report "I also have this problem." Odds are that no more than two people who've posted in this thread ACTUALLY have the same problem.
  2. More importantly, the Panels 2 branch is dead in D6. Switch to Panels3, which uses a totally different mechanism.