Closed (outdated)
Project:
Subscriptions
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jun 2009 at 00:20 UTC
Updated:
27 Sep 2019 at 13:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
salvisThis is a weird message. Please tell us the path (URL) where this message shows up and attach a screen snapshot.
Comment #2
salvisFeel free to reopen if you want to pursue this.
Comment #3
HumanTex commentedNot sure if there's any reason to think there's a real error with this, but the same issue still continues to pop up for me with 6.x-1.4. The last one happened a few minutes ago after a core update to Drupal 6.22 running on my dev server. Screenshot attached.
Comment #4
salvisThanks for the screenshot (update.php running an update of a completely unrelated module).
I don't understand why running the update is doing anything with Subscriptions' block...
Is update.php using its own theme? Or are you running a theme that doesn't have a 'content' region?
Comment #5
HumanTex commentedI'm using a modified version of antsin.com's Fever theme for the front-end (lots of CSS and image changes - not coding), and Rubik for the admin theme... so there's content regions available with them - but - update is using it's default theme. I have no idea why it pops up on unrelated screens, so it still shows occasionally - not only when running an update. That just happened to be the first thing it showed up on when I came looking for a fix and found this post. I still had the window open, and reading you'd asked earlier for a screen grab - it was easy enough to get and post.
I don't know Drupal well enough yet to make any guesses, but thought it might shed some light on the issue that it popped up on an update process that (I assume) never gets modified by any other modules or any of the usual dev hacks. At least I can guarantee that it's always repeatable anytime I run an update, since I've done several lately.
Comment #6
salvisThank you for the additional information.
How are you running the Subscriptions UI? Have you ever activated the block? Are you currently using it?
Comment #7
HumanTex commentedI'm still in dev mode and not live yet. Subscribe is enabled and active, but the block isn't. I haven't done a lot of thorough testing since I'm still tweaking and adding to the site. For now I'm only seeing the occasional error as mentioned, and there's one other issue that seems to be unrelated. I'll add a new thread for that one.
Comment #8
salvisI installed the Rubik theme, but it does have a 'content' region.
I've changed 'content' to 'contentX' in subscriptions_ui.module, but I found that the block shows up nicely under the 'Disabled' region.
I'm unable to pursue this until I get a pointer to a theme that reproduces the problem (probably one without a 'content' region).
You may be able to get rid of the annoyance by assigning the Subscriptions Interface block to some region (and back to Disabled, if that's what you want) for each of your themes.
There are similar issues, like #1172560: The block X was assigned to the invalid region Y and has been disabled. and #1119922: The block Devel Node Access was assigned to the invalid region footer and has been disabled., and even one of my own: #908354: "The block 'MyBlock' was assigned to the invalid region 'footer' and has been disabled.". The latter is a clearly-reproducible core issue, but in D7.
Comment #9
salvisNo follow-up.
Comment #10
vv7 commentedWe also get this error, so we can confirm. It appears at the first page view (any page) after cron.php was invoked. 100% reproducible.
Comment #11
salvisI think this is an issue in your theme and the way that Core handles the case when a module asks for a specific region. Your theme probably does not have a 'content' region.
Comment #12
salvis