Regions disappearing after cron run [#1951206]

Every time I run cron, my navigation region gets disabled. When that happens and I go to the blocks page, I get this error:

The block Main menu was assigned to the invalid region navigation and has been disabled.

The region comes back when I clean cache. I'm using the simple layout, and all I've changed in the code is where the region prints (I need it to be above the site's branding). After running into this problem, I've changed the order of the regions in the layout's info file, but that didn't change a thing.

Comments

Comment #1

msmithcti CreditAttribution: msmithcti commented 20 July 2013 at 15:18

Status:

Active

» Postponed (maintainer needs more info)

I and many others have been using Omega 4 for a while now with no problems when running cron. I assume that this is happening with a particular module/modules or other factors. Are you able to narrow this problem down any more?

Comment #2

fubhy CreditAttribution: fubhy commented 21 July 2013 at 12:05

Status:

Postponed (maintainer needs more info)

» Closed (duplicate)

This problem was probably related to #2042349: Race Condition: Theme Registry Cache Clear during Page Render can cause corrupt Registry which has been resolved.

Comment #3

a.ross CreditAttribution: a.ross commented 31 July 2013 at 12:28

Status:

Closed (duplicate)

» Active

I applied the patch from that issue and it doesn't solve my problem. Could it, however, have something to do with Git deploy? I had another issue as well that involved the version definition in the .info file (which is missing when using Git deploy).

Comment #4

fubhy CreditAttribution: fubhy commented 17 August 2013 at 21:49

Version:	7.x-4.0-beta1	» 7.x-4.x-dev
Status:	Active	» Fixed

Can you try to upgrade to 4.x-dev and see if that solves your issue?

I can't reproduce this so I am closing this issue for now. Please re-open if the issue persists. At this point I am pretty sure though that it's not Omega related as I did a massive amount of theme registry (and related) re-iterations today and everything is working nicely...

Comment #5

a.ross CreditAttribution: a.ross commented 18 August 2013 at 00:17

I don't think I'll be able to upgrade in the short term but once I get around to upgrading I'll report back here.

Anyway like I said I'm using git deploy which means version metadata is missing from project .info files and I was wondering if that might have some negative side effect in the case of omega.
shouldn't this be set to "cannot reproduce" though?