DIV inside of <?php page_content(); ?>

[amiracle]

I cannot seem to get DIV tags to work correctly when entered via the backend on a page. 

For example...

on a page, within the backend, I put in:

Code:

<div class="banquet_flowers">
<img src="/media/images/banquet_flowers.png" alt="Flowers" />
</div>
<div class="banquet_text">
<p>We serve noodles and rice; they are good.</p>
</div>
<div class="banquet_champagne">
<img src="/media/images/banquet_champagne.png" alt="Champagne" />
</div>

I then style this with CSS... but the styling doesn't work.  All other DIV tags within the template work, I use Website Developer Toolbar to edit CSS in realtime and cannot seem to figure out why it doesn't work; the source as outputted looks correct.

[ruebenwurzel]

Hello,

I use Website Developer Toolbar to edit CSS in realtime

Better try it with our Template Edit Modul.

Matthias

[amiracle]

Thanks for the reply; could you elaborate on how that would help in my situation (I did look up the module).

To be honest, I don't use the template .css file as my true css file - it is just a dummy one.  My real css file lives in the /css/ directory so that I can edit it at my whim without having to uninstall and reinstall a template for every minor change.

Is the problem I'm experiencing normal? Should I not expect DIV tags to work when they are coming from the generation of the <?php page_content(); ?> tag?

[marathoner]

Are you using FCKEditor? It will preserve DIV tags. Then you would simply modify the CSS file that you use to display the page.

Also, if you alter the permissions, you can modify the template CSS using a desktop tool and then FTP it so you don't have to uninstall/reinstall the template each time you make a change.

[ruebenwurzel]

Hello,

To be honest, I don't use the template .css file as my true css file - it is just a dummy one.  My real css file lives in the /css/ directory so that I can edit it at my whim without having to uninstall and reinstall a template for every minor change.

where did you have the /css direktory? In the templates folder, in the template dir itself or even in the WB root? Culd it be that you simply have a path problem?

And with the Template edit modul you an also edit all template text files without the need of uninstalling and reinstalling a template.

If you use FCKEditor you can define <div> for every block (when hiting "enter" in the textarea field). In combination with user defined styles in the dropdown list you shoul get the result you wanna have.

Matthias

[amiracle]

Thanks for the replies.

My css directory is in the WB root; that is how I code all my sites and staying with my usual I dismissed the idea of having my css part of a template package.  I suppose I could modify the permissions on the template directory and then just FTP the files instead of using the WB backend... I hit the permission error during an unrelated event within the template directory and never again thought about FTPing those files directly... I didn't want to bork anything not knowing if WB would be mad at me changing those permissions (some frameworks can get grumpy).

The css file I use is the site-wide css and every other ID and class within the css file works just fine... it's only when my markup, which I write in the WB back end, that doesn't show - but the markup that is part of the template that accesses the same css file works fine; I don't use any editor in the WB backend... just straight markup.

[hrioo]

Have you tried <div id> instead of <div class>? Why not just ftp the css file and see if that will work? I put my main css files on root directory and don't have any problems, just make sure they're referenced properly in your template's index.php file.

[amiracle]

Well... I solved it.  Came down to a parsing error; coincidentally I had a ) instead of a } closing the last css attribute within my document. This error caused anything after that attribute to not work and I had added a quick class at the end of this css while I was finishing up. So the hundreds of attributes that made up my template and other functions came before that last attribute which is whey everything else worked.

I'll remember to validate my css before I ask a question next time.