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.
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
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.
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.
believe it or not, C5's highlighter (which allows you to click blocks to edit them), the z-index is only set to 5!!!
Make sure to add this to your CSS:
#ccm-highlighter { z-index: 50 !important; }
and the way most image sliders work, is they add z-index value for each slide. So once you get more than 5 slides, the slider loses it's click-ability because the highlighter was only set to 5.
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.
As the owner of power slider lite, I can say that it definitely works with 5.5+. But since power slider uses jquery.cycle - it was probably conflicting with the other jquery cycle include you had.
Do you have a link to your website? That'd be helpful in debugging your JS issues.
I tried the z-index tip, it didn't solve the issues but is definitely something I'm going to implement anyways - seems wise.
My edit bar problem is only on pages that have powerslider lite. I see the white bar but there are no buttons on it. And I have that problem only when I don't include my own jquery.cycle file, which is very strange.
Still also not getting the edit pop-out. I've dug through a lot of code, but no progress.
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.
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.
Code
Post Reply
Delete Post
You are allowed to delete your post for 5 minutes after it's posted.
Hopefully that will solve your problem.