CMS - what happens to FW site after client editing?

Take a standard scenario, design a site in FW with a CMS like inlay, upload to server, client makes edits on some pages, then asks for some design changes to the original site.

My question is, following client edits, how can that be reflected in the original Freeway file? How can I get the new, edited version back into FW?


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

You don’t. The layout (templates) are designed in Freeway. The ‘Content’ is separated into the CMS. They don’t meet as such.

David

http://www.ineedwebhosting.co.uk

On 13 Nov 2014, at 20:39, Iain Mackenzie email@hidden wrote:

My question is, following client edits, how can that be reflected in the original Freeway file? How can I get the new, edited version back into FW?


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

Thanks David. I get that, but what if the client wants to change the template? How are the changes that he made recoverable? Surely there must be content initially when the site is launched.


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

How are the changes that he made recoverable?

That partly depends on the CMS but if you imagine on your Template there is a placeholder that has an unique identifier. The CMS assigns any created content to that unique ID and as long as that ‘placeholder’ is not removed from the Template then there should be no issues.

A lot of CMS use a MySql database to store the actual content - but not all.

David


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

Do you mean a scenario where the client makes his own changes on the template (directly in the code), outside Freeway, regardless of the content which is saved in a external database?

You’ll loose those changes he made, for they’re not (done) in your Freeway document (yet) and so you’ll have to make these changes yourself within Freeway as well.

Richard


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

When you use a CMS like Inlay, you are creating a template (kind of like a Master Page in Freeway) which the client can then fill in with their content. It’s a rubber stamp for making more like itself, not the finished product.

When your client asks you to change the layout, you can do that – freely – and the CMS will pick up the changes and the site (and any client-entered content) will look exactly the way you want it to. You don’t need to update the placeholder text in your template (it can and should just be Lorem Ipsum) because you updating the template will never erase the content that has been entered.

The only way you can mess this up is if you rename one or another of the editable elements. Inlay uses the name of the HTML box that you apply the Inlay Action to as an identifier in its system. As long as the name remains the same, the content will flow into that container – even if you move it around the page, or change the styling, etc.

Walter

On Nov 14, 2014, at 1:59 AM, Richard van Heukelum email@hidden wrote:

Do you mean a scenario where the client makes his own changes on the template (directly in the code), outside Freeway, regardless of the content which is saved in a external database?

You’ll loose those changes he made, for they’re not (done) in your Freeway document (yet) and so you’ll have to make these changes yourself within Freeway as well.

Richard


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


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

Walter, is there a demo of Inlay?


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

The documentation site http://docs.inlay.io is a made-with-inlay (responsive, FW7) site. Granted, it is not very flashy or anything, but I found it to be a useful exercise to build the documentation in Inlay. It made the documentation more honest (and found a few bugs along the way).

I don’t have any sort of free trial, but if you sign up for a month and don’t like it, you’re only out $5 to see if it works for you.

Walter

On Nov 15, 2014, at 3:16 AM, Iain Mackenzie email@hidden wrote:

Walter, is there a demo of Inlay?


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


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

Thanks Walter. I signed up to try it out, and I send you an email as I am stuck with the testing on my site. Just says ‘could not locate Inlay client’.


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

Have you uploaded the two client files( _inlay.php and _htaccess.txt) to the server (into the same folder as your registered site’s index.html), and renamed _htaccess.txt to .htaccess on the server? Also, if you have done those steps, have you also tried visiting your regular site to ensure that your hosting provider’s server allows you to execute .htaccess commands?

http://docs.inlay.io/setup.html

Walter


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

Yes, I uploaded the files to the folder where the registered index.html file is located for site 1, and yes, I have renamed the _htaccess.txt file.

My site 1 is located in a folder within site 2, and I changed the name of my site on Inlay to it, redownloaded the files and put them onto that site 2.

Now, I can edit the (original) site 1 which is a subfolder, but now all sites from my main site 2 are inaccessible in a normal browser!


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

If you are trying to only affect files in the one subfolder, then ensure that the .htaccess, _inlay.php, and the index page for that subfolder are all together in their subfolder (don’t leave the client files in the site root). Then make sure that the URL you enter in the inlay.io server includes that subfolder. If this represents a change from what you entered when you signed up, then you will want to download the client files again, and replace the files on your server. The entire base URL is encoded in the client file itself.

Walter

On Nov 17, 2014, at 9:44 AM, Iain Mackenzie email@hidden wrote:

Yes, I uploaded the files to the folder where the registered index.html file is located for site 1, and yes, I have renamed the _htaccess.txt file.

My site 1 is located in a folder within site 2, and I changed the name of my site on Inlay to it, redownloaded the files and put them onto that site 2.

Now, I can edit the (original) site 1 which is a subfolder, but now all sites from my main site 2 are inaccessible in a normal browser!


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


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

Walter, I have edited the details on Inlay to show the url as http://www.site2.com/site1 as the main www.site1.co.uk is pointed at site2.com/site1 folder.

If I download the files and install them in site2.com/site1 folder and rename the htaccess file, the site becomes editable in Inlay interface in the HTML box I applied your action to in FW7.

However, the site is inaccessible via a browser. Just get a ‘file you requested is not available’ error in Safari.

Additionally, when I logout from Inlay, I get an error saying ‘The page you were looking for doesn’t exist.
You may have mistyped the address or the page may have moved.’

Whenever I remove the 2 files from Inlay from the site, it is accessible again in a browser.


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