5.5.1 Update - No pop-up menus

Permalink
I just updated to 5.5.1 today, and now I can no longer edit any blocks on my site. I am using a custom theme. Whenever I click on a block while in edit mode I see a thin black strip that looks like it is the beginning of the pop-up box, but the rest of the box never appears.

I have tried this on multiple browsers and computers, so I'm fairly certain it is an issue with my theme. Any suggestions? Thank you in advance for any help given.

 
adajad replied on at Permalink Reply
adajad
Have a look at your template and make sure you have the following code in the end (before /body)

<?php Loader::element('footer_required'); ?>


Hopefully that will solve your problem.
scotty1212 replied on at Permalink Reply
Thank you for the reply,

I checked that and it is there in the correct place. Any other suggestions?
splashby replied on at Permalink Reply
splashby
Hello Scott,

I had same issue. I overcame it by going doing this
enter:
Dashboard >
Systems & Settings>
Interface Settings>
select: Disable Quick Navigation bar -
that sorted it for me...
Good luck.
Michael
splashby replied on at Permalink Reply
splashby
i lied....:-)
I just went back and the issue has not gone...I'll come back if I figure it out...
VidalThemes replied on at Permalink Reply
VidalThemes
Hi, do you have elements on your site with a very high z-index? it may be they are covering up the TinyMCE editor when it appears.
splashby replied on at Permalink Reply
splashby
Thank you Vidall - in the end it became clear to me that it was only happening on product pages and was some kind of js conflict (core_commerce) and was resolved by updating the plugin to latest (2.5)
Thanks again for bringing my attention to z-index.
scotty1212 replied on at Permalink Reply
I have checked my theme's css and the only z-index values are low ones, like 10 or so. Does anyone know where I can find what the z-index values are for concrete's gui elements?

Another note, I have several javascript files included in my header. I have tried to simply note include any of the files, when I do this it creates another problem - I am no longer able to see any of the elements in the header bar. The white bar is there, but there are no buttons on it. Including my javascript files fixes this - but I'm still having the issue of not being able to see the pop-up menu's while in edit mode.
splashby replied on at Permalink Reply
splashby
Hi Scott - are you using ecommerce? or other add-ons?
scotty1212 replied on at Permalink Reply
No I am not using ecommerce or any other addons like that. Just some basic blocks like Vimeo and Powerslider Lite.

I am starting to think it may be a javascript conflict somewhere. My theme is one that I purchased from themeforest.net, and I adjusted it to work with Concrete5. It came with a lot of javascript files, some of which I have stripped out. One in particular seems to be causing issues - jquery.cycle.all.latest.js. It is a slideshow thing that came with the theme that I no longer use. For some reason, if I leave this file out then I am no longer able to see any buttons on the edit bar.

Still not sure what the problem is with the pop-out menus. I'll keep chucking away at it till I find something. Thanks for all the help so far.
scotty1212 replied on at Permalink Reply
Update: I figured out the top edit bar problem. Apparently Power Slider Lite is not compatible with 5.5. And it was causing issues.

Still having the issue with the pop-out menu not showing up.
scotty1212 replied on at Permalink Reply
Both issues solved.

The issue with Power Slider Lite was because of my misunderstanding of the way Concrete works. I had created a copy of the block in the /blocks folder (because I didn't want to use templates) and I assumed that anything I didn't put in the new folder would be taken out of the original package folder, which apparently is not entirely true. Once I placed the js file in the new folder it worked perfectly.

The pop-out menu was a little more tricky. I ended up comparing my site with a working concrete site using Google Chrome's "Inspect Element" option, which is very handy. I found that the inner div of the pop-out menu has the css class name "content", which is obviously not a very unique name. I ended up having a div.content class in my theme's stylesheet that had display:none set.

I assumed that concrete's core styles would take precedence over any of a theme's, but I guess that's not the case. It would be nice if there was a list of reserved class names so this kind of thing can be better avoided. Also it would be nice if the core elements used a little more unique class names.
jccshoe replied on at Permalink Reply
I have the same problem. I have a content div for the jquery slideshow that is set to display:none. What did you end up doing to correct that?
scotty1212 replied on at Permalink Reply
You can either change the class name of that div, or use a wrapping div to
separate your theme from core concrete styles. Then in your stylesheet you
would need to put the id of that wrapping div in front of everything.