Posted - October 10 2005 : 07:26:18
| I think the key thing is that you'd put your own pages inside the vpasp wrapper, rather than include the vpasp panels inside your own pages.
so, you'd change your own pages to be like:
<% ShopPageHeader %>
Your normal contents go here
<% ShopPageTrailer %>
If your normal files are in the same directory as vpasp, then that'd do the job.
If you wanted to use vpasp from non-vpasp directories, then you might find our multiple-directory addon useful:
but you would only need that if your vpasp files are in a different directory to your custom files.
If you wanted to split your vpasp panels into bits, and then only call the relevant bits from your custom files (eg on vpasp use the top+bottom+left+right panels, but on your custom asps only show the top+bottom panels), then you might find our panel-splitter useful as that splits the whole thing into bits which can be called in different ways from different files:
In general, when having custom asp files (and for lots of stuff in general), we often use both of those (multiple-directory and panel-splitter) so that things are nice and flexible.
Web Design, Online Marketing and VPASP addons