I have searched the board and cannot find the correct answer, although I'm sure it is very simple.
What is the correct CSS to display as bullets?
In short, when I click the "unordered list" in TinyMCE it does not display bullets in the list. Same with ordered lists; does not display numbers.
This is what I have for my CSS now:
/* LISTS */
/* lists in content need some margins to look nice */
div#main ul,
div#main ol,
div#main dl {
font-size: 1.0em;
line-height: 1.4em;
margin: 0 0 1.5em 0;
}
div#main ul li,
div#main ol li {
background-image: url(eldoradopublicschools/northwest/uploads/images/bullet.gif);
margin: 0 0 0.25em 3em;
}
/* definition lists topics on bold */
div#main dl dt {
font-weight: bold;
margin: 0 0 0 1em;
}
div#main dl dd {
margin: 0 0 1em 1em;
}
div#main dl {
margin-bottom: 2em;
padding-bottom: 1em;
border-bottom: 1px solid #c0c0c0;
}
/* END LISTS */
TinyMCE not displaying <li> as bullets
-
- Forum Members
- Posts: 28
- Joined: Tue Oct 09, 2007 4:33 pm
-
- New Member
- Posts: 7
- Joined: Sat Nov 01, 2008 10:48 am
Re: TinyMCE not displaying <li> as bullets
hi,
it sounds normal as your bullet path background-image: url(eldoradopublicschools/northwest/uploads/images/bullet.gif); prorbably works from your website page but not from the admin. In order to have your css work anywhere you should use a path from the root /your_website_root/ and so on
have swing
it sounds normal as your bullet path background-image: url(eldoradopublicschools/northwest/uploads/images/bullet.gif); prorbably works from your website page but not from the admin. In order to have your css work anywhere you should use a path from the root /your_website_root/ and so on
have swing
Re: TinyMCE not displaying <li> as bullets
Aren't url() relative to the calling HTML URL path ?
Pierre M.
Pierre M.
Re: TinyMCE not displaying <li> as bullets
Indeed, why not try with an absolute URL?
Best
Nils
Best
Nils
-
- New Member
- Posts: 7
- Joined: Sat Nov 01, 2008 10:48 am
Re: TinyMCE not displaying <li> as bullets
Hi,
@ Pierre, actually, the path are relative to the css when it is in a css directory. That's why when you've, for example a css diretory and an img neighbour directory "../img/theimg.jpg" will find the img wherever you link to the css.
now the way cmsms plays with the css when it is in the database
- in the website pages, e.g
http://toto.dev/stylesheet.php?cssid=42&mediatype=all
- in the admin pages, when it comes to the website css for tinyMCE, e.g
http://toto.dev/modules/TinyMCE/stylesh ... 1225786567
changes that all as the css path between those two virtual css and the img directory is not the same.
Then, the path to the img can't be relative to both stylesheets and has to be or absolute, http://toto.dev/img/ but this is not so good an idea as it will probably oblige to change all the img pathes when uploading the web sites on its prod server, or, that's what i would advise, relative to the root of the website, /img/.
The only thing is that obliges to create a virtualhost when working locally if the website directory is not the root of the dev server but it's a good habit, isn't it ?
)
have swing
@ Pierre, actually, the path are relative to the css when it is in a css directory. That's why when you've, for example a css diretory and an img neighbour directory "../img/theimg.jpg" will find the img wherever you link to the css.
now the way cmsms plays with the css when it is in the database
- in the website pages, e.g
http://toto.dev/stylesheet.php?cssid=42&mediatype=all
- in the admin pages, when it comes to the website css for tinyMCE, e.g
http://toto.dev/modules/TinyMCE/stylesh ... 1225786567
changes that all as the css path between those two virtual css and the img directory is not the same.
Then, the path to the img can't be relative to both stylesheets and has to be or absolute, http://toto.dev/img/ but this is not so good an idea as it will probably oblige to change all the img pathes when uploading the web sites on its prod server, or, that's what i would advise, relative to the root of the website, /img/.
The only thing is that obliges to create a virtualhost when working locally if the website directory is not the root of the dev server but it's a good habit, isn't it ?

have swing