Allowing Content Editing - Post ID...

User 2073552 Photo


Registered User
1,625 posts

Well, it is a Church site, and if they want the FTP then they should have it. And that is why I am saying give it to them... If they screw it up and do not know how to fix the problems they create. They will stop asking for Open Sourced content... Because if I were Hilary, I would be furious if they went in and messed with the site I had built for free.
"An Apple doth not fall far from its tree, yet an orange does."

https://lbwebsitedesign.com - Responsive Web Design & Web Hosting Services.
http://helpsite.sirage.com - HTML5, CSS3 and CC Help Video Blog.
User 122279 Photo


Senior Advisor
14,649 posts
Online Now

Hilary Sargeant wrote:
Thanks - I was hoping we could give access to specific pages and/or sections without switching to some other software.


That is exactly what you can do with iframes. If you have one person writing the sermons page, someone else the history page etc etc, get a cheap domain where they can upload their efforts, and you prepare the sermons and history pages with an iframe like this:

<iframe src="http://www.cheapdomain.com/sermons.html" width="800" height="600"></iframe>

and

<iframe src="http://www.cheapdomain.com/history.html" width="800" height="600"></iframe>


Just use the html tool in VSD and paste this code where you want it to appear on the pages, the height and width can be adjusted. Then go to the 'www.cheapdomain.com and place an empty file by the name in question (e.g. sermons.html and history.html), let your colleagues have the ftp details to www.cheapdomain.com and see how they get on with it. ;)
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 122279 Photo


Senior Advisor
14,649 posts
Online Now

SirAGE wrote:
Well, it is a Church site, and if they want the FTP then they should have it. And that is why I am saying give it to them... If they screw it up and do not know how to fix the problems they create. They will stop asking for Open Sourced content... Because if I were Hilary, I would be furious if they went in and messed with the site I had built for free.


They will certainly make a mess out of it. And remember, even if they had VSD and the site's vnu file, which they need to open the site for editing anyway, every time there is a new upload by one of the people, it will overwrite the changes that one of the others has made before them. To have a team (if you can call it so) working on the same site in VSD, you need strict dicipline, knowledge how to use VSD and you'd have to download the vnu file for every comma you want to change.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 539803 Photo


Registered User
2,156 posts

Is it possible for the church to have there own bought and paid for copy of VSD and its 1 free sdrive account 1 free stream, 1 free form.

Upload the main content to that site, (pages not requiring editing)

Then let them pay for a webbie account, putting editable pages on a separate website, and with the same copy of VSD anyone wanting to edit pages could do so at the church pc,just selecting relevant sdrive account to upload to

If someone drops a clanger, and overwrites it will be easy to rectify as its all in one place

Or am i missing the point (its paid for CC get some business & the church have control)

Started using CC VSD in January 2009, I don't do HTML code, Sales from CC site exceeding expectations taken me out of semi-retirement
Hosted FREE on CC S DRIVE www.chauffeurdrivenluxurycars.co.uk
My new VSD & SCCP site Oct 2011 www.deloreanjewellery.co.uk
My friendly window cleaner www.mwcwindowcleaner.co.uk

User 38401 Photo


Senior Advisor
10,951 posts

I too would suggest something like CushyCMS as mentioned above already. This would allow you to give access to specific people in specific areas of the site (content only) so that it doesn't get too messed up. Each person could have their own account for whatever department of the church they are responsible for updating the site for. You can then specify areas of the site they have control of and you can even make it only the content area of a page.

I wouldn't suggest full FTP control for multiple people. I think that would be a bit overkill. Control should be given to at least one other person in the church, but should be given to someone that has good judgement and is responsible enough not to cave in and give it to everyone that wants it. In most cases this is the person in charge of dealing with getting the website taken care of (hired or asked you to work on it). For the rest I'd only give them access to a single folder where they can upload text files for you to put their content into the site. Wouldn't let them do it to be honest.

Should they get very insistent and require you to hand over the info so they can work on it to, then tell them a price (and not a cheap one, no less than $30.00 per hour) for fixing it if they mess it up. Being a VSD site they will be required to purchase VSD for EACH person that will be involved in it. And as already mentioned the mess will be in whether they forget to download the .vnu file from the server and open that one instead of the one they had already saved themselves last time they worked on it. This means nasty overwrites of other people's work etc. It will be a mess. It's hard enough with only 2 people trying to work with VSD sites let alone a group.

Make sure those terms are clear if they insist on it and DO NOT let them trample you just because they are a church. That doesn't give them the right to abuse your time and efforts and most importantly your contribution of doing a free site for them. They've already abused you in condemning you for not using open source software which really is no concern of theirs what you choose to use if they aren't paying for it lol.

Just my 10 cents :)

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.