First of all, I am *loving* this theme. I am currently using it with Panels Everywhere, and am using the Default Layouts in Page Manager. Unfortunately, none of the contributed message modules (Better Messages, JQuery Message Alert, etc.) I have attempted to use will display. I am sure there is a way to invoke these modules in template.php or page.preprocess.inc, but I am too much of a noob to figure this out. Any help with this would be greatly appreciated. Thank you in advance, and thank you for such a powerful, incredible theme.
*UPDATE: After viewing this (https://drupal.org/node/2144405) issue, I have temporarily disabled status-messages.inc in the Omega directory, which has solved the issue. However, I would rather not 'hack' the main code if there is a better solution. If not, no problem. Please advise. Thank you.
Comments
Comment #1
dojorob76 commentedComment #2
fubhy commentedDid you place the messages pane in your Panels Everywhere site layout configuration?
Comment #3
dojorob76 commentedHi fubhy,
Thanks for the quick response. I did, indeed, place the messages pane in my Panels Everywhere site layout configuration. Unfortunately, this simply resulted in the regular (albeit Omega rethemed) status messages appearing in those regions.
Comment #4
fubhy commentedAha, so you want to use a contrib module that does some stuff with the messages based on JS? I would guess that due to us overriding the theme function for the messages there is some incompatibility. I am going to blame those modules for that because of how they attach their JS functionality then. If it breaks by changing some minor stuff in a template or theme function there is something wrong with the JS.
I'd suggest you take a look at the JS provided by the module and see how you can override it, or, alternatively, use status-messages.theme.inc in your theme and invoke theme_status_messages() from there (to override Omega).
Comment #5
dojorob76 commentedThank you for your help, fubhy.
A couple of things... just in case they're relevant now or down the line:
1) All of the contrib status message modules I attempted to use (I tried several) had the exact same result, which was that they simply did not render. They were all overridden by status-messages.theme.inc, and I noticed another comment in the Better Messages module Issue Queue from someone else having the same problem. So, for us noobs (in my case, I can rock the front end, but when it comes to back end, I'm fairly worthless), would it be possible to get some detailed instruction on how, specifically, to override this (invoke theme_status_messages() from copied over status-messages.theme.inc), since it appears that anyone interested in using any contrib status message module will, in fact, need to do this?
2) I had a similar issue with a CAPTCHA contrib module (Fancy Captcha) where the JS was stripped out in Omega. Could this be related and mean that it is not necessarily status-messages.theme.inc, but rather something in the way scripts.inc renders js files or something? I phrase this as a question, because (as I'm sure you can tell) I have absolutely no idea. Just trying to get a better grasp/understanding on these things, so forgive me if I'm being really stupid here.
Again, your help is very much appreciated. Thank you for being so on top of everything. This is such a fantastic theme, and I just want to be able to use it the way the developers intended.
Comment #7
malberts commentedI don't know about the other modules, but Better Messages overrides the theme function (to add markup) which in turn gets overridden by Omega. I couldn't find a simple way to restore the registry's value to before Omega changed it. So for the sake of using just Better Messages, create a file "status-messages.theme.inc" in your sub-theme's "theme" folder and put the following inside (changing MY_THEME to your theme name):
Comment #8
brahimmouhamou commentedI'm using Disable Messages and have the same problem.
Messages that should be disabled are still visible if my Omega theme (but not in Bartik or another theme) is set as default.
I too fixed it by doing this:
Comment #9
imperator_99 commented#7 fixed it for me, thanks malberts!
Comment #10
fubhy commentedI'd suggest #7 over #8 because it does not break the inheritance chain / chain of overrides. Under normal circumstances, #8 is just as good as #7 but it can get ugly if you have other theme registry altering functionality in place. E.g. I am pretty sure that if you wanted to use sth. like devel_themer, the registry altering approach would break it.
Comment #11
steinmb commented