Hello,
I’m trying to figure out how I can set a master page to output pages with a .php extension.
I’m using web yep to build pages for a client, who is selling real estate (small parcels of land). The client wants to be able to add pictures and descriptions for each lot. I’m going to have 200-300 .php pages with the web yep action applied to them.
Is there way to make this happen? Or will I have to individually change each page that is created to .php?
Hi Rich,
Rather than rename all of the pages simply instruct the server to
process html pages for php using an htaccess file;
You can now keep all of your pages as .html and let the server run php
in them as if there were .php files. Easy.
Regards,
Tim.
On 14 Jan 2010, at 15:39, Rich Gannon wrote:
Hello,
I’m trying to figure out how I can set a master page to output pages
with a .php extension.
I’m using web yep to build pages for a client, who is selling real
estate (small parcels of land). The client wants to be able to add
pictures and descriptions for each lot. I’m going to have
200-300 .php pages with the web yep action applied to them.
Is there way to make this happen? Or will I have to individually
change each page that is created to .php?
Thanks for the link Tim,
I know I should figure this out…but it everything I mess with htaccess something goes awry. For now I will just do the trained monkey thing and change the file to .php in the inspector palette.
Of course you could let WebYep take some of the load by using the
WebYep menu action. The client can create his own pages and you get
away with create a handful rather than the 300 you mention
David
On 14 Jan 2010, at 21:15, “Rich Gannon” email@hidden wrote:
Thanks for the link Tim,
I know I should figure this out…but it everything I mess with
htaccess something goes awry. For now I will just do the trained
monkey thing and change the file to .php in the inspector palette.
How is this done? I’ve been clicking through the Ob.Dev. site and can’t find anything about it. I also can’t download the manual on Max’s page for the web yep actions. Might be time to call it a day.
Click in an empty HTML box and apply the WebYep menu action. Add the
WebYep page action, change the page to php. Add a short text item
alongside on the same page and publish the page to a server.
Log into the WebYep page in a browser and start creating extra pages
by editing the menu. The fiddly bit is styling the menu.
David
On 14 Jan 2010, at 22:02, “Rich Gannon” email@hidden wrote:
Sometime around 14/1/10 (at 22:23 +0000) David Owen said:
Log into the WebYep page in a browser and start creating extra pages
by editing the menu. The fiddly bit is styling the menu.
Yep, it is a bit similar to the CSS Menu action but not the same - it
takes a bit of trial and error.
The thing to understand is that this doesn’t actually make actual
new pages, it uses a template page (which you design in Freeway) and
populates the template with the right bits when a link to a
particular pseudo-page is clicked in the browser. Making a ‘new page’
is a matter of logging in, using the WebYep controls to create a new
link, then going to the custom template page view that this link
produces and adding the content to that ‘new’ page.
This isn’t anything particularly weird or non-standard - in fact this
is essentially how all database-driven page template solutions work.
But if you’ve not worked in this way before it is something you
should play with before launching into the real thing.
Thanks for all of the help. It is obvious to me that I need to take some time to learn what all of the functions of web yep and associated actions do. Especially the menu and loop actions. Going to be doing some studying today.