pulishing bv page in php as opposed to publishing in html

[AWS]

Quick question.......

would publishing you page in php make for faster download of page then publishing in html?

[navaldesign]

Re: pulishing bv page in php as opposed to publishing in html

No. It is the same amount of bits to download in either way.

[AWS]

Re: pulishing bv page in php as opposed to publishing in html

No. It is the same amount of bits to download in either way.

Hi Naval,
Thanks.

Whats the benifit to a php page over html assuming that their must be some benefit due to BV giving you the choice in publishing?

[Bethers]

Re: pulishing bv page in php as opposed to publishing in html

It depends on what you might want the page to do. I will use php for all my new sites, because by doing so, I can make my navigation, header and footer (and any other page parts I want) in pages as an include - which then allows you to make global changes on all pages. That alone makes it worth it for me.

You can read about that here:

http://www.vodahost.com/vodatalk/bluevoda-tips-tricks-shortcuts/15764-single-menu-page-bv-php.html

[navaldesign]

Re: pulishing bv page in php as opposed to publishing in html

BV is giving you the chance to publish the page as php in order for you to be able to put php code in it. PHP can be from a simple form processing script (look at BV Forms Tutorial Part 1) or complex scripts. Typical case: password protected pages, and, as Beth said, inclusion of the menu / headers / footers. Other scripts can be shopping cart scripts embedded in the BV pages, etc.

[Watdaflip]

Re: pulishing bv page in php as opposed to publishing in html

Its best to put all your pages in php just incase later on you want to include some sort of script. That way you don't have to go back through and republish as php and change your links, etc.