hell-o
some things you can look at to see how they work.
store/admin_files/agora_user_lib.pl
Code:
$sc_product_display_headerif you remove or replace "center" you can manipulate things that way. whether or not it's restored to default when saving in the manager i don't know. would be easy to check. not the best way though.
store/library/agora_html_lib.pl
sub product_page_header
this is not the same as the store header. this is the top portion of the ppinc you can't find in the productPage.inc files
some things can be customized here but changes would be global and not easily overcome in some cases. however, rather than adding table structure to your store header and footer you can introduce more table structure here and in the
sub product_page_footer (same file). added table structure would be introduced after the &storeHeader; and before the &StoreFooter;. this will keep your header and footer inc files clean.
you could do something like...
change these lines in the
sub product_page_header...
Code:
&StoreHeader;
if ($prod_message ne "") {
print "$prod_message\n";
}
to...
Code:
&StoreHeader;
print "<table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" width=\"599\"> \n";
print "<tr> \n";
print "<td valign=top align=right width=\"599\"> \n";
if ($prod_message ne "") {
print "$prod_message\n";
}
change the 599 to whatever the difference is between the overall width of the page and the width of the left nav. so if your page is 780 and the left nav is 180 then change 599 to 600 in both the table and the cell.
then you need to close the table the row and the cell in the
sub product_page_footer...
change this...
Code:
&codehook("product_page_footer_top");
print $zmessage;
&StoreFooter;
to this...
Code:
&codehook("product_page_footer_top");
print $zmessage;
print "</td> \n";
print "</tr> \n";
print "<\table> \n";
&StoreFooter;
this is off the top of my head. besure to back up your file before editing!!
you will then have to log into your store manager then go to the store layout and mess with the productpage width a little. sometimes it's best to set a few pixels smaller than apparently needed. so if the hardcoded width above is 600 then in the manager it may only need 590 (especially if using borders in your ppinc).
another thing is screen resolutions. if you code to one resolution with css then it can explode or collapse in others when using tables and css.
this all maybe an excersize in futility or not.
you may also be able to control that ppinc table by replacing the tables as shown above with some positioning style or class.
anyway you approach this you must check on different computers and screen resolutions to be sure of readability.
there is a css hack in the yahoo free forum files section by martin van marion. this was done several years ago and i still haven't gotten around to seeing what it's all about.

i don't know how intense he went with the css. whether or not it was fully tableless css or just the introduction of more control over table content with classes and styles.
regards,
dan