CSS help for Firefox - Left & Right Sidebars

I’ve got a site built thats looking great in IE7 and IE6,
looking 90% great in Safari and Chrome,

and looking like hell in Firefox.   The sidebars are showing up under the main column instead of where they are supposed to be.


There’s nothing major showing up on the W3 validator.    Small things, but nothing that should be causing this.

Take a look if you have time, and have any suggestions.  Thanks.

Here is the site:

http://tinyurl.com/5pgjzq

We decided to bid this out.

If you’re interested, here’s the link: http://modxcms.com/forums/index.php/topic,29951.new.html#new

Looking at this you still have a <p>wrapping your CSS. In your document you should go to the HTML view and remove it. It could cause problems down the road that you can’t predict. As I said browsers should fail on pages with invalid markup in css but they seem to just ignore but you may come across a circumstance where it affects it.

Cheers,

Jay

Jay, thanks for pointing that out. I finally figured out how to solve this thanks to your reminder.

I’ll explain here in case someone comes across this thread and its useful to them.

The problem is: I have that CSS in a document. The document is /css.php or /72.php and its contents are {{css}}

Then the actual CSS I edit is in a chunk.

And --- the text editor is on by default, because the client needs it that way for the majority of his documents.
Its the text editor that is wrapping the chunk so the output instead of {{css}} is <p>{{css}}</p>.

I tried turning off the text editor using the little drop down underneath the content box, and that got me nowhere -- it reverted back to the RTE every time. I just recalled now that there’s a tick-box in page settings where I can turn off the RTE for the document.

And that solved everything

Thanks again -

John

Can I ask why your css is as php if you are placing it in a chunk? wouldn’t have been easier to make it just a file in your assets dir somewhere? Are you parsing it somehow? Applying conditional etc?

I’ve been editing the css every day for the past week, about three times a day.  So for it to be a file would be a major pain.  This use of a chunk for the css is ingenious (someone had it as an example in the wiki I believe) and has saved me so much time and frustration, because it is so easy editing it from the Manager.  This has actually become one of my favorite features of MODx.


for clarity -- the default naming protocol for furl’s is .php... but I believe for the .css document MODx did automatically change it to *.css.

Ahh. See for me I don’t edit anything but content in the manager unless this is a case where you don’t have FTP access. There is nothing wrong in what you are doing. If it works for you, great.


Ahh, I forgot about the alias extensions. That is no problem at all with a php extension so long as its got the right settings.

Cool

Since I tend to stumble through css with trial and error, more often than not, its great to just have it open in a spare browser window with the "on save Continue Editing" button checked.  Then I can tweak it over and over with just one click to save.


Thanks for the conversation!

John

You can edit files within the filemanager on the second tab.
I always use that to change css files the quick way, so there is no need for a chunk to edit the file fast without loading a ftp client or something.