I'm still using Omega 3 as I find it so easy to theme.
On a production website that has been live for over a year, I recently added a new region to my subtheme by following the documentation (i.e. editing the .info file and then editing the zone configuration). The new region appeared in the correct zone in the way I wanted.
However, I find that whenever I 'flush all caches', the newly created region disappears. On further investigation, I find that the region is still present and visible on the configuration page, however is reverts to an 'Unassigned Region'.
How can this be? Any ideas very welcome.
I get around this by only flushing CSS and Javascript, but sometimes I have to flush all caches which sends the new region back into the unassigned area.

Further info that may or may not be relevant:

  • I use Domain Access, however the changes I make to the subtheme are on the primary domain settings and therefore are applied to all sub-domains automatically. This has always worked well and I don't think it's related to this issue
  • All other configuration settings on the theme appearance to do with zone and region configuration were applied before uploading to the server. This is the first change to the zone and region configuration that I have applied on the production site

Comments

justinchev’s picture

justinchev CreditAttribution: justinchev commented

I've got a similar issue except mine is reversed. If I disable some regions so that they become 'unassigned' they sometimes become reassigned to their region for some reason. I too am using the 'Domain Access', and have checked that the same region setup is used when viewing the theme settings from the different URL's.

BTW this doesn't seem to happen on every cache clear, and I can't actually say it's down to this as it only happens every couple of weeks and the cache cron runs hourly.