Jump to content

disappearing columns and footer


Recommended Posts

I have a strange problem that is just driving me nuts. I have a custom page called newpage.php and newpahe.tpl in my default theme. These pages work fine, even worked out how to pull data from the database. Here's the issue I'm having, if friendly URLs is not enabled, the page displays fine. I get the header, left column, content, right page and the footer.

 

However if I enable friendly URLs, it shows the header and the content but no left column, right column or footer. The html is there, I can see it in the view source but it just won't show in the browser window. Anyone got any ideas?

Link to comment
Share on other sites

thanks for the reply vekia. Unfortunately I'm working on a localhost test environment. So, you would tend to lean to a CSS issue? It's weird because the source has all the code present but it just doesn't render in the browser. Tried Chrome, Firefox and both the same. Having to learn Smarty, prestashop to get this project finished.

 

Just noticed this line in header.tpl

{if isset($page_name)}id="{$page_name|escape:'htmlall':'UTF-8'}"{/if} class="{if $hide_left_column}hide-left-column{/if} {if $hide_right_column}hide-right-column{/if} {if $content_only} content_only {/if}">

Will this have anything to do with it. maybe $page_name is not set. Not sure why it would only not set if friendly URLs are set to true.

Edited by freakystreak (see edit history)
Link to comment
Share on other sites

well, it looks like css issue. especially because you said that you see contents of columns in page body, but in browser window these columns arent visible.

 

can you inspect code with firebug? or developer tools in chrome? with these features you can easily check css styles for hidden elements

Link to comment
Share on other sites

OK, just looked in chrome inspector and it seems to be defaulting display:none for the #left_column, #right_column and #footer. It may be something to do with my custom .htaccess file. I think, it's only a guess mind, that it's using the class for #pagenotfound. Looking deeper into this. Thanks for the help.

Link to comment
Share on other sites

×
×
  • Create New...