Welcome, Guest. Please login or register.
Did you miss your activation email?
May 27, 2012, 03:12:05 AM

Login with username, password and session length
Search:     Advanced search
Wollen Sie dem WebsiteBaker Team beitreten?
Nähere Informationen finden Sie unter hier und auf unserer neuen Webseite.
155555 Posts in 21715 Topics by 7737 Members
Latest Member: gx-world
* Home Help Search Login Register
Pages: [1]   Go Down
Print
Author Topic: Adding a form section destroys my template  (Read 1027 times)
Lotus

Offline Offline

Posts: 184


« on: May 05, 2008, 04:28:22 PM »

I recently finished a WB-template. All CSS and no tables. Currently it is not accessible outside the office.
Adding content to the site right now and that includer cunfiguring form module. But the form module destroys the template and I dont know why. Thougt it was a CSS conflict and renamed all my classes and id:s with a tail. Looking att form moduel frontend.css i cant find any conflicting code. Is there any other CSS code involved other than frontend.css when using form?

When i say destroy i mean that my divs gets a different width (smaller) and some divs get strage formating of the text inside.
« Last Edit: May 06, 2008, 07:51:26 AM by Lotus » Logged
aldus

Offline Offline

Posts: 1238


« Reply #1 on: May 05, 2008, 04:33:08 PM »

Quote
But the form module destroys the template ...
Maybe i missunderstood - but the "form-modul" use his own css inside the "modules/form/" folder.

Have you looked at the code in the browser?

Regards
Aldus
Logged
Lotus

Offline Offline

Posts: 184


« Reply #2 on: May 06, 2008, 07:50:51 AM »

Thanx for the tip Aldus..
I use wb 2.7 and i had a look at forms own CSS (frontend.css) but i could not find anything..

Edit: Found the code that made the faulty. It is a snippet written by someone in this forum. It is a great snippet but as  I dont need it in this template I won't investigate further.

Code:
<?php ob_start(); // Start the outputbuffer
            
page_content(1); // Next call the block
            
$content1=ob_get_contents();  // Now fetch the output into a variable
            
ob_end_clean(); // Clean up old mess and stop buffering
?>
   
<?php if ($content1<>"") { // Next test $content1 2 to see if there is something in it
            
echo "<div id=\"divname\">\n";
            echo 
$content1;
            echo 
"\n</div><!-- close div#divname -->\n";
}
?>
« Last Edit: May 06, 2008, 08:34:43 AM by Lotus » Logged
Pages: [1]   Go Up
Print
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!