I'd guess you're closer than you think. If pulling in the Twitter Bootstrap makes it work, then there must be some overriding CSS in Elegance that's affecting things.
But I can't tell from your description what that might be, a screenshot might help. But otherwise I'd use the browser tools to examine the parts of the structure one at a time and see which rules are causing the trouble, then overrule them.
Though, it's not clear if you realize that it'll almost certainly look different from on the Bootsnipps site, the Bootsnipps site is plain, vanilla, ordinary Bootstrap. Elegance is a Bootstrap-based theme, so things are supposed to look different. Sometimes that's a good thing, sometimes it causes trouble.
David Scotson
المواضيع التي نشرها David Scotson
Elegance is a Bootstrap 3 theme, and Clean is a Bootstrap 2.3 theme, so make sure that you're using the correct code. They're often the same but there are small differences. The one you link to is Bootstrap 3 code for example.
The nav-pill class is actually the nav-pills (with an s on the end) class so that might be the issue, and you probably need to pair it with "nav nav-pills" on a ul or ol tag with li tags within it for it to have the intended effect.
But in general, I would expect any Bootstrap 3 HTML to work in Elegance, so if it's not, check for typos.
The nav-pill class is actually the nav-pills (with an s on the end) class so that might be the issue, and you probably need to pair it with "nav nav-pills" on a ul or ol tag with li tags within it for it to have the intended effect.
But in general, I would expect any Bootstrap 3 HTML to work in Elegance, so if it's not, check for typos.
The main reason is speed:
1. If they already visited another site that uses the same font, they don't need to download it again, so your site seems faster, and your server needs to do less work, pay less for bandwidth.
2. If they don't then they get the file from the CDN. The CDN has servers at key points all around the globe, the machines are set up to do one thing and one thing only so no PHP is involved, no session variables need to get sent to the server before it figures out what it needs to send, just a straightforward file download. Unless your users are all located near your server, and you're both in a remote location with poor connectivity to the wider internet (in which case, change the setting and host them locally), the files will arrive faster, and your server will do less work.
1. If they already visited another site that uses the same font, they don't need to download it again, so your site seems faster, and your server needs to do less work, pay less for bandwidth.
2. If they don't then they get the file from the CDN. The CDN has servers at key points all around the globe, the machines are set up to do one thing and one thing only so no PHP is involved, no session variables need to get sent to the server before it figures out what it needs to send, just a straightforward file download. Unless your users are all located near your server, and you're both in a remote location with poor connectivity to the wider internet (in which case, change the setting and host them locally), the files will arrive faster, and your server will do less work.
I noticed that the font wasn't serving correctly when I forced my site to SSL, but I think there's already a fix for that issue.
Moodle in English -> Themes -> Theme Designer issue -> Re: Theme Designer issue
بواسطة - David Scotson
Are you all using Windows Servers by any chance?
edit: Bitnami looks like it's Linux, so never mind, just a red herring.
edit: Bitnami looks like it's Linux, so never mind, just a red herring.