CMS Made Simple Forums

Greetings All,

Encountered a problem this morning with CMS 1.2.3 -- standard install -- nothing fancy. Loaded my graphics, templates, and css just fine last week. Build out my information architecture, added subpages, applied additional sub-templates and more css. Everything was up and running with only a few development things left to improve (CSS tweaks, old browser support, subpage graphics, etc.)

However, this morning, something strange happened. When I added a new sub-page -- It would render perfectly in the PREVIEW pane inside CMS admin... but when I view it in the browser, the CSS was no applied -- Same link reference as the other pages, same build as the other pages... just NO CSS!

I ran a few tests, turned the CSS off for all pages... they rendered without CSS. Re-added the CSS to the templates -- the pages I created last week all returned to normal... however, the new pages STILL would not display with CSS styles. It was as if I had NEVER applied a CSS to the page... Any new pages added all have this problem (Since I built new templates and new stylesheets and the problem will not go away!)

Very frustrating! Does anyone have any ideas on even where to begin?? I'm thinking a database problem? Any help would be appreciated!

Thank you in advance!

Cheers,
Kyle

Are the new pages using the same template as the old?
Do you have many mods installed?
Can you provide a link to the site?

Nullig

Greetings Nullig,

I used the same templates as the pages that work -- I simply selected the "Add New Content" link, selected the same template, gave it a title, entered the menu text, selected the parent (same as the page that works) -- everything identical to the working pages... then clicked SUBMIT. If I go the browser -- No CSS.

If I go back to the Admin -> Content -> Pages -> Select Broken Page -> (Edit Content) and select the PREVIEW tab... it works just FINE! Grrrr....

Greetings Nullig,

Solved it!

Apparently, you can specify metadata to automatically fill in the OPTION tab default field when setting up the templates. However, for some reason, I had a "closing" HTML tag in my default metadata field that was shorting out the CSS include statement. So every new page that was created replicated this error and caused the CSS to fail...

Just more proof that computers do what you tell them to do, not what you want them to do!!!

Thanks for the sounding board!!

Cheers,
Kyle

Don't you just hate when that happens???

Glad you got it sorted.

Nullig