I go to content tab, hit configure pane, then enter css id and css class. Neither one gets passed to the page when panel is rendered.

BTW - What is the best way for me to style a block in a panel. I guess I can look for the class that is assigned in the by teh panel and put css to support that in my file, but is there a better way.
Thanks

Comments

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Postponed (maintainer needs more info)

This works fine for me. Is it a problem on every single panel? What type of content pane?

I just use the css classes/ids in my theme's style.css and imagine most people do the same.

gggdrpl’s picture

gggdrpl commented

phazer, there is another Save button at the bottom of the Panel content page. If you don't press this button all changes are lost no matter you hit the Save button on every configure pane pop-up window.

Maybe you've already found out for yourserlf, but the same happened to me and I just thought it would be worth to mention the incident here.

Silly but it's true!

criznach’s picture

criznach commented

Phazer's question about styling a block in a panel is a valid concern. As an example, suppose you have a menu in one block, and a who's new block below it. If you want to redefine the list style so the new users use icons instead of bullets, but not change the menu styling, you are forced to use a content-specific css selector because panels doesn't wrap the blocks in a div with a unique ID like normal blocks. I hope a selector or ID can be added at some point, because I use this to make certain blocks unique.

sdboyer’s picture

sdboyer commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

yes, it's a valid concern - which is why we put it in in the first place. Given that phazer hasn't responded with more information about the problem and that neither catch nor I have the same problem, the only conclusion I can draw is that there was some other problem with what phazer was doing, perhaps along the lines of gggrdpl's suggestion. I'd rather not have to hear arguments for features that, until evidence is offered to the contrary, are already implemented.