It depends on the depths of the edit. Examples:
User needs to edit the entire HTML
Options:
1) Allow edit of ASPX page - chance of destroying code
2) Create an HTML page for content and allow edit. Use that page to build
the ASPX page dynamically (can be cached to avoid remake every trip - some
risk of blow up, but it is low if the user does not get into JavaScript (for
example)
3) Create a tool that places HTML in a database and pull from there - also
some risk, esp. with JavaScript
User needs to edit pieces, like calendar events
Best option: Find a calendar piece (open source?) or build one
As much as possible, if you can create a situation where the user is merely
changing "data", it is better.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
"Neil Steventon" <Ne***********@discussions.microsoft.comwrote in message
news:14**********************************@microsof t.com...
Hi,
Im after some advise on how to go about this problem.
I have a master page with nice header and side bar setup. I then have
various aspx pages that use this master page. I want one of the aspx pages
to
be editable by a user. This saves me having to doing any of the changes.
Should I give them access to a public folder for an HTML page that I then
include in the website. What are the best ways to tackle this kind of
scenario.
Thanks
Neil