Posted by jebbushell on September 27, 2011 at 8:28pm
I have newly installed Omega and it works. Unfortunately a black triangle appears at bottom right of each page. The triangle contains the text "RESIZE ME". This disappears when I re-enable Garland so it would appear to be Omega-related and not a browser "feature". It has to go. Can anyone please let me know how? There are also a couple of tag-like objects far right that also need to go.
I'm hoping to find that this was a blunder on my part but, whatever, it's a show stopper.
Comments
It's a debugging setting
The triangle is part of the debugging settings in Omega. It's the second tab on the configuration page, there you can switch it off, together with the grids and placeholder blocks.
edit: it's the third tab
Go into the debugging
Go into the debugging settings in your Omega subthemetheme and disable the box entirely or disable the grid and block debugging and they won't show up anymore. You can also disable based on role so you can leave it on for admins and off for everyone else.
Drupaler and Mobile Ninja
Cellar Door Media - Beautiful Mobile Solutions
Navigate to
Navigate to admin/appearance/settings/yoursubthemename. Then click the "debugging" tab. Then uncheck "anonymous" and authenticated" user roles under "Roles that may use the grid overlay and debugging blocks." Now only administrators will see the debugging tools.
There are theme settings for everything. It just takes a little time to learn where things are.
Thank you all so much
It's gone. Or it's back! Whatever I like. Thanks!
Shows for non-authenticated user
I have only administrator user checked, but the "Resize me" and the tab to show block regions still show, even for anonymous user. Is there some other setting? D7, latest version; tried running cron, clearing caches, rebuilding permissions, etc. Thanks!
Have you tried disabling
Have you tried disabling administrator? I have them all disabled with the intent to re-enable when necessary.
P.S. If you're a noob like me then you may find it handy to install Cacheflusher. It makes it a lot easier to flush the cache and thus slows down the rate at which you go nuts.
Disabling administrator
I did try that -- but it didn't work, either, so I re-checked it, thinking maybe having none checked would default to ON for everyone, as it sometimes does for other features (although probably not, for this one). I suspect I just have something else set up incorrectly, but I can't figure it out. Seems like everything is off.
Even tried manually emptying the database cache tables, just to make sure it's not a cache problem.
I may be getting out of my
I may be getting out of my depth here, but are you subtheming? If so you might want to make sure that it's set off everywhere. So if for example you have two subthemes, it means that you have three places to look. [My understanding is that the override facility is not currently operational so I nail everything down.]
I find disabling the 'grid
I find disabling the 'grid overlay' to be the only way to remove the resize corner icon. The permissions do work for me.
A note if you are using Delta
One note about toggling on/off the debugging features that may not be obvious: If you are using Delta and the Context module to set up layouts for specific sections of a site, and you have it set to override, then you need to adjust the toggle settings in each Delta layout. When I realized this , I also realized I needed to pay more attention to how the Delta layouts were overriding the base layouts.
this fixed my problem
could not figure out why grid overlay would not disappear until I unset them in Delta layouts
Delta settings ... Aha!
Arne -- Thanks! That was the issue, in my case: Never thought of per-Delta settings, and I did have a customized layout for the home page. Thanks for the notes, everyone.
One other issue with Debugging settings to be aware of
I just had one other issue come up with the use of the debugging controls I should share. I had set up and developed a site with the debugging settings set to show all of the time for any level of user, and then also later for users to be able to turn on/off the grid and debugging blocks using the check boxes seen on the upper right side of the browser window. No problem.
But when I switched off these settings, by checking off all of the boxes in the debugging section for my layouts, as they were going to be for the production site, my layout was broken.
It took me a bit to figure out what was going on. Under the configuration settings for the layout, I had added a zone/region that only had a background image in it and no other content. Removing the debugging grid/blocks totally removed the region, thus breaking the layout. Then I realized I needed to check the box in the zone/region settings to force rendering of the region. This fixed my issue.
This might be something to include in the documentation regarding setup, or maybe posted as an issue, as it seems to be unpredictable behavior. What do others think?
Thanks for documenting your steps
Thabks for documenting your steps for anyone to use in a similar situation. We've had this issue come up quite often in the IRC and we tried to document as best we can on the debug settings page in the docs http://drupal.org/node/1298690 . Let us know if you have any edits to this and we'll make sure to put them in.
As a best practice, I recommend using debug blocks and grid settings only during the initial wife framing but once any code begins I turn them off never to be used again. They are a great tool to visualize what's going on but definitely get in the way of theming if used past the wireframe. The reason being is they are blocks put in through CSS and toggled with display: none. The only way to get around it would be a push pull of the entire CSS block through JS rather than just being toggled.
Glad you were able to figure it out!
Drupaler and Mobile Ninja
Cellar Door Media - Beautiful Mobile Solutions
Thanks for the information
Thanks for the information. I hadn't really read through the latest debug settings page in the docs until you pointed it out. The notes there about their use seem pretty clear.
I can see now that it makes sense to turn off the debugging blocks past initial stages of site development as they are implemented through CSS settings.
I've found the grid is nice to have available as an option during development to help visualize sizing of some page elements. In this regard, I'm assuming that only the debugging blocks effect region rendering in the CSS, so it would be relatively unproblematic to use the grid during development. Does the grid get in the way in any known ways during theming?
@arnemaine, I stick the grid
@arnemaine, I stick the grid on now and again to work out image widths etc and have found no problems with layouts breaking. I never use the debugging blocks. Can I also call attention to your region with no content and only a background image, why not use an actual inline image? I find that odd to force render a region with no html content other than a css background image.
Sam.
Why to use bg image
I needed to use a background image in that region that would fill the browser window regardless of the width, something I couldn't do with an inline image.
Hi Arne, Can I see it in
Hi Arne,
Can I see it in action? Just curious.
Sam.
Here's the example
Sam,
Here's the site I have under dev. I had to display/not display a header wrapper to make the mobile layout version different than the narrow, normal and wide versions. The difference is in the graphics used above the main menu area. One bg image is used for the background behind the figures for the nar, norm and wide layouts. The zone/region in question is used to show the grass as a bg image for the mobile layout only. Being able to configure different zone/region displays, to be able to customize the zones and regions right in the Omega UI, then set up Delta/Contexts was really helpful.
http://temp.dianalogan.com/
As I'm sure you know, you'll need to either change your browser width to see the various layouts or look at it on an iPhone, tablet, etc to see the different layouts.
Very nice design, and the
Very nice design, and the responsiveness is great!
Sam.
Can't disable the debugging blocks or grid
I'm having an issue where--I've finished using the debugging blocks and grid, and went to intake them to turn them off. But even with them un-checked, the widgets are still there.
I'd like to get rid of them, because they are rendering regions that I'm not using in my theme.
Has anyone else run into this?
Roger
_________________
Art has gone to the dogs
GoodeGallery.com
you could try clearing the
you could try clearing the cache or if your using the delta module, double check that you have the debugging blocks disabled in each of your delta's also.
Thank you. I hadn't thought
Thank you. I hadn't thought of Delta. It was enabled there also, as you suggested.
However, when I tried to disable it there, I got the following error:
Recoverable fatal error: Argument 2 passed to delta_reduce() must be an array, null given, called in /Users/rggoode/Dropbox/websites/htdocs/goodegallery-v2/sites/all/modules/contrib/delta/plugins/delta/delta_injection.inc on line 100 and defined in delta_reduce() (line 256 of /Users/rggoode/Dropbox/websites/htdocs/goodegallery-v2/sites/all/modules/contrib/delta/delta.module).
Not sure how to interpret that...
Roger
_________________
Art has gone to the dogs
GoodeGallery.com
Fixed...
Disregard the last comment. I checked on the status of my Delta Module, and it was due for an update. I disabled the debugging items successfully after the update.
Thank you so much for your help.
Roger
_________________
Art has gone to the dogs
GoodeGallery.com