It turned out that the statements that disabled the li elements were in
reset.css that is part of the Sunburst default theme:
* li { display: inline; }
I disabled reset.css in portal_css and all is fine. The reset.css is not part
of the sunburst theme in Plone 4.2.5 at all. So my problem seems to be solved.
But may the disabling of the css have other backdraws?
Am Samstag 04 Mai 2013, 17:33:03 schrieb Steve McMahon:
> You might try the plone-users list, which has more eyes watching it. There
> might be someone interested in helping maintain the theme.
>
> All I can tell you beyond that is that problem is probably quite trivial.
> The theme is probably trying to load a CSS file from a URL that isn't
> available when the style sheet resources are merged in production mode. If
> you can identify the style sheet, you might even be able to fix the problem
> by visiting portal_css in the Zope Management Interface and telling it not
> to merge the particular style sheet you're having trouble with.
>
> On Sat, May 4, 2013 at 12:25 PM, Eggert Ehmke <[email protected]>wrote:
> > When I upgraded my Plone 4.2.5 site to Plone 4.3, I got a problem with
> > unordered lists constructed by <ul> <li> elements. My site uses the plone
> > lite
> > theme. The details of the problem are described here:
> > http://plone.org/products/lite-plone-skin/issues/4
> > Unfortunately, the theme is not supported anymore for recent Plone
> > releases.
> > What would be the best procedure to solve the issue? If there is a theme
> > similar to the lite theme that would work for me, I am happy. If I could
> > modify the lite theme to make it work again, this would be fine too. But
> > my
> > knowledge in this respect is limited. Any suggestions?
> >
> > _______________________________________________
> > Setup mailing list
> > [email protected]
> > https://lists.plone.org/mailman/listinfo/plone-setup_______________________________________________
Setup mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-setup
