Freeway Pro and Perch CMS

Hello,

I’m new to the whole setting up web pages etc, but the experience has been a positive one so far. Am having one issue that I could use some advice on;

Have set up and published the website using Freeway Pro and it appears to be working fine. The pages are .html

Looking to inject some Perch CMS content and this is where the issues have started. Perch is set up and functioning. The problems arise when I try to get pages into a .php format as advised on the Perch support site.

adding the .htaccess file
AddHandler application/x-httpd-php5 .html .htm
causes the Perch management pages to download to my ‘downloads’ folder instead of in the browser window (Safari).

I have raised tickets with both Perch and the Host provider and am tick-tacking between the two without a resolution so far.

Is one way around the issue to rename all the page files in Freeway to the .php extension before publishing and uploading the website?
If I do this, does this mean I then have both .html files (from a previous upload) and .php files in the host website folders? How would this affect search engines?

I have not proceeded as far as inserting the bits of Perch code into the Freeway generated pages, but imagined this is just done using the crowbar action (which I have used to embed other mailing list form code, youtube video code etc). Is this the way Perch is used with Freeway Pro? That is, use Freeway Pro code as the master website template, always adding the Perch code to the Freeway website file at a local level, then uploading the website through FTP to get the framework in place? Then using the Perch pages to add dynamic content? Seems to be the logical way that the two pieces would work nicely together (without one getting out of step with the other).

Looking forward to some feedback.

Regards,
Shane.


dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yes, but name the page files in Freeway (in the inspector palette). Freeway will manage all files on the server for you on upload

David

On 22 May 2012, at 02:50, Shane Baker email@hidden wrote:

Is one way around the issue to rename all the page files in Freeway to the .php extension before publishing


dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks David.

Have done as you suggested.

Regards,
Shane.

On 22/05/2012, at 5:24 PM, David Owen wrote:

Yes, but name the page files in Freeway (in the inspector palette). Freeway will manage all files on the server for you on upload

David

On 22 May 2012, at 02:50, Shane Baker email@hidden wrote:

Is one way around the issue to rename all the page files in Freeway to the .php extension before publishing


dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Have done as you suggested.

Just make sure that you only use the .php extension on pages where you are going to utilise Perch content. Otherwise you will lose the ability to preview any of your FW pages locally.

David


dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options