Location: PHPKode > projects > Edit-Point > edit-point/README.txt
########################################################################
# Edit-Point 4.01 Beta - Simple Content Management System
# Copyright (c)2005-2009 Todd Strattman
# hide@address.com
# http://covertheweb.com/edit-point/
# License: LGPL
#
# TinyMCE WYSIWYG Editor
# Copyright (c)2007 Moxiecode Systems AB
# http://tinymce.moxiecode.com/
# License: LGPL
#
# TinyBrowser
# (C) 2008-2009 Bryn Jones
# http://www.lunarvis.com - http://groups.google.com/group/tinybrowser
# License: GPL
#
# MD5.js Copyright (c)1998-2005, Paul Johnston, distributed under the BSD License:
# http://pajhome.org.uk/crypt/md5/
#
# sha256.js Copyright (c)2003-2004, Angel Marin, distributed under the BSD License:
# http://anmar.eu.org/projects/jssha2/
#
# German Translation by:
# Beat Beer
# www.stardesign.ch
#
# Dutch Translation by:
# Tjerk Plantenberg
# www.tjerkhelpt.nl
#
# Icons from: http://tango.freedesktop.org/Tango_Desktop_Project
# Released under the Creative Commons Attribution Share-Alike license
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2.1 of the License, or (at your option) any later version.
# 
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
#
########################################################################

CONTENTS:

About
Credits
Requirements
Usage
Security
Setup Basic
Setup Advanced
Upgrading
TinyMCE WYSIWYG
Customizing
Notes/Bugs
Todo


-----------------------------------------------------------------------
About:
-----------------------------------------------------------------------
***NOTE*** PLEASE READ IMPORTANT UPGRADE INSTRUCTIONS FOR 4.01 BETA !!!!!!!

The script is available in English/Duetsch/Espanol/Nederlands.

This script lets a webdesigner place designated editable areas throughout a new or existing "php" or "html" website. These are called "Edit-Points". This allows users to "simply" edit content throughout the site without touching the design or having to know any HTML.

The script is run by using an Administration page(admin.php) for adding Edit-Points, a User/Editor page(index.php) for editing points, and a web-based configuration page Options(options.php). There is a basic file upload/delete option available File Upload(upload.php) and a Setup Utility(setup.php) to automatically set the permissions of your directories and files. There is also advanced password protection available.

The only changes that need to be made are to configure your file upload options and your image directory options. Other than that, just upload the script directory (edit-point) and the script should work fine.

To review and change options in the script go to the "Options" page: http://YOURDOMAIN.com/edit-point/options.php or edit "config.php" by hand. You can revisit "Options" at any point without causing any harm.

I use the script like this:

1) Design the website without any real content.
2) Upload the script directory (edit-point).
3) Visit http://YOURDOMAIN.COM/edit-point/options.php and add the password and other options that I need.
4) Create Edit-Points wherever needed.
5) Give the user the password and the address: http://YOURDOMAIN.COM/edit-point/

Please feel free to email if you need help or if you have comments, suggestions, or complaints: hide@address.com

-----------------------------------------------------------------------
Credits:
-----------------------------------------------------------------------
The WYSIWYG editor is TinyMCE
http://tinymce.moxiecode.com/
TinyMCE works on Linux, Mac, and Windows with Opera 9+(mostly), Firefox, Mozilla, Internet Explorer, and Safari(partially).

TinyBrowser is developed and copyrighted by Bryn Jones
http://www.lunarvis.com
http://groups.google.com/group/tinybrowser

The Filemanager plugin was authored by Al Rashid and Xiang Wei ZHUO
http://alrashid.klokan.sk/insFile/

MD5.js Copyright (c)1998-2005, Paul Johnston, distributed under the BSD License:
http://pajhome.org.uk/crypt/md5/

sha256.js Copyright (c)2003-2004, Angel Marin, distributed under the BSD License:
http://anmar.eu.org/projects/jssha2/

German translation by:
Beat Beer
www.stardesign.ch

Dutch Translation by:
Tjerk Plantenberg
www.tjerkhelpt.nl

Icons from: http://tango.freedesktop.org/Tango_Desktop_Project
Released under the Creative Commons Attribution Share-Alike license


-----------------------------------------------------------------------
Requirements:
-----------------------------------------------------------------------
1) Linux Server with php 4+ (safe_mode = off). A shared server using phpsuexec is recommended as other security methods do not have php running as the user and this makes file creation and shell commands (in the script) difficult. Windows has been reported to work.
2) Javascript enabled browser for the WYSIWYG editor(TinyMCE). TinyMCE works on Linux, Mac, and Windows with Opera 9+, Firefox, Mozilla, Internet Explorer, and Safari(partially).
3) A website.

NOTE!!! You will have varying degrees of success with the WYSIWYG editor depending on your browser, local OS, and server OS.


-----------------------------------------------------------------------
Usage
-----------------------------------------------------------------------
The following is an explanation of the "less documented/questioned" parts of Edit-Point.

You're first step, after uploading the script to your server, should be to go to options.php and set your passwords. Then go to the bottom of the page and hit "Edit". After this is done, login and browse options.php to see what options you want to add or change.

Next, go to admin.php and create some Edit-Points. When adding an Edit-Point in your existing html, you may want to do it between <p></p> or <div></div> tags just as you would if you were adding text to the page.

The following is a brief description of the workings and options in the Edit-Point script pages.

1) Admininstration (admin.php):
This page lets you: a) add Edit-Points, b) edit the raw html of the list of Edit-Points, c) edit the raw code of a file, d) delete Edit-Points, and e) Edit points like the end user.

	a) Choose a name for the Edit-Point, choose the webpage to add the Edit-Point to, and click "Create Edit-Point".

	b) Choose this option to get to the list of Edit-Points, that the "user" sees, to rearrange, add html, delete, etc. This list is a php "include" on the index.php page, so there is no header, footer, or any other formatting.

	c) Choose any "allowed" file to open in a textarea so that the raw code can be edited.

	d) Choose an Edit-Point to delete. After choosing the Edit-Point, you will be taken to a page to select the webpage that you want the Edit-Point deleted from.

	e) This is only shown if chosen in options.php(default=on) and just lists the Edit-Points the same as index.php.


2) Editor (index.php):
This is just a list of the Edit-Points that the end user sees.


3) Options (options.php):
This page lets you customize (add and remove options) your Edit-Point installation. You can add or remove options whenever you want. It's best to just visit this page and take a good look at all of the options, but a few of the unique ones will be described here.

	a) "Option to be create Edit-Points in *.html files. ?"
	This only works correctly with linux servers. The selection must be turned "On" and the "Create .htaccess" link must be clicked. This option will create a ".htaccess" file that directs the server to parse php in .htm and html files. If there is an existing .htaccess file, Edit-Point will include the code at the end of the file.

	b) Password Protection
	If you have already created passwords, when you revisist options.php, the password boxes will be blank and "(reset only)" will be to the right of the boxes.

	c) File Upload
	Edit-Point uses TinyBrowser now for file uploads. TinyBrowser is used by Edit-Poit and TinyMCE, they share the data.

	d) Setup Utility
	This is for linux servers and is used to set the correct permissions on your data directory. This is primarily for existing directories and probably only needs to be used one time as that the script will create the correct file permissions.

	e) TinyMCE plugin settings
	If you chose "Full" (the default setting), then turning plugins on/off won't work. You have to choose "Advanced" to turn plugings on/off.

	f) TinyMCE Compressor
	I highly recommend using this option as it speeds TinyMCE up considerably.


-----------------------------------------------------------------------
Security:
-----------------------------------------------------------------------
There is a password protection option that can be turned on or off. I STRONGLY recommend using the built in password protection. I believe it is much more secure than .htaccess or most other password protection scripts. Options.php must be used for the password protection. The passwords cannot be set using the config.php file. Cookies must be enabled.

See "Password Protection Settings" under "Setup Advanced" for more details.

I also recommend placing your "data" directory outside of your public files. To do this, after installing the script, move the "data" directory outside of your public directory. Then edit config.php by hand to reflect that path. For example, if your script is located at "home/YOURNAME/public_html/edit-point", the "data" directory should be at "home/YOURNAME/data" and $datadir in config.php should read:
$datadir = "../../data";


-----------------------------------------------------------------------
Setup Basic
-----------------------------------------------------------------------
After unpacking the script, you should have a directory called "edit-point" that contains the script:

- edit-point(directory)
	- data(directory)
		- textlinks.txt(blank)
	- images(directory)
		- edit_lg.png
		- edit_md.png
		- edit_sm.png
	- jscripts(directory)
		- many directories and files
	- lang(directory)
		- de.php
		- en.php
		- es.php
		- nl.php
	- admin.php
	- config.php
	- footer.php
	- header.php
	- index.php
	- info.php
	- options.php
	- setup.php
	- style.css
	- upload.php

1) Upload the "edit-point" directory and it's contents to your server as a subdirectory of your "public" directory. For example: http://YOURDOMAIN.com/edit-point/

2) Visit the webbased configuration at http://YOURDOMAIN.com/edit-point/options.php and make any necessary changes. The last option, "Setup Utility" will automatically chmod your data directory. You can also just edit "config.php" by hand, but the password protection must be set using options.php.

3) To add Edit-Points, go to the Admin-Page:
http://YOURDOMAIN.com/edit-point/admin.php
*NOTE: The first time you go to admin.php or index.php, there will not be any Edit-Points available...

4) To edit the Edit-Points, go to the Editor-Page:
http://YOURDOMAIN.com/edit-point/index.php

5) To perform backups, save all webpages with Edit-Points and regularly backup the "data" directory.


-----------------------------------------------------------------------
Setup Advanced
-----------------------------------------------------------------------
When you add an Edit-Point, a "*.txt" file is created in the data directory. Then you add an include to that file in your webpage. The include code will be automatically created for you. The code can either be copy/pasted where you want it to go or a button is available to add the include code wherever your cursor is in the webpage code. For instance, the code will look like the following example:

<?php $point = file_get_contents('/YOUR/HOME/PATH/edit-point/data/YOUR-POINT-NAME.txt'); echo $point; ?>

There are two buttons available. The first will add just the include code. The second button will add the include code and and a "edit" icon below the include code. This will let the end user "click" the icon and then they can edit the point.

The main configuration file is "config.php". The "config.php" file can be edited through a browser by visiting "options.php". Below are the parameters that can be changed and a brief description as to what they do. Remember, nothing in config.php "needs" to be changed (unless you want to add options). The script will function fine with the default settings (minus file upload, image upload, and password protection).

--------------------
INITIAL SETTINGS
--------------------
$language = "en.php";
	Choose your language (English=en.php/Deutsch=de.php/Espanol=es.php/Nederlands=nl.php).


$page_title = "Edit-Point 4.01 Beta";
	Change to your desired site name and page title. Please change this!!!


$samplename = "New Point Name";
	When you use admin.php, this is the text that pre-populates the field "Choose a name for the new Edit-Point." 


$sampletext = "This is sample text";
	When you use admin.php, this is the text that pre-populates the textarea field in the "create an Edit-Point" form. I prefer to leave this blank so that it is faster creating multiple points and then go back and add text to the points.


$adminlink = "on";
	Decide whether or not to add the links to the Edit-Points on the Admin-Page.


$su = "off";
	Option to add links to all script pages on all pages.


$multi = "off";
	Option to add one Edit-Point to multiple places. The option will appear after you add the Edit-Point.


$ht_select = "off";
	Option to add Edit-Points to *.html files.

Create .htaccess
	This creates or appends a .htaccess file in the webpage directory with the following line:
	Addhandler application/x-httpd-php5 .php .html .htm

$admin_ignore1 = "";
$admin_ignore2 = "";
$admin_ignore3 = "";
$admin_ignore4 = "";
$admin_ignore5 = "";
	Directories to ignore when listing files to add Edit-Points (when using admin.php). The script directory (edit-point) is ignored by default. Use the directory name only, no slashes.

--------------------
PASSWORD PROTECTION SETTINGS
--------------------
$password_protect = "off";
	Option to use the built-in password protection.

I STRONGLY recommend using the built in password protection. I believe it is much more secure than .htaccess or most other password protection scripts. Options.php must be used for the password protection. The passwords cannot be set using the config.php file. Cookies must be enabled.

Basically, the password protection does not save or send any passwords in plain-text, and authenticates a login session so that if the password is intercepted, it cannot be used to login.

The password protection is a "CHAP" (Challenge Handshake Authentication Protocol) system. The system uses md5.js (by Paul Johnston : http://pajhome.org.uk/crypt/md5/) and sha256.js (by Angel Marin : http://anmar.eu.org/projects/jssha2/) to hash passwords client side before sending them to the server. The CHAP system authenticates the user before allowing login.

First, the new password is hashed client side (before submitting), using sha256.js, and then the server encrypts it while hashing it again using another hashed version as the seed. Then it is stored in the data directory.

When logging in, the client and the server do the following:

1) The server creates a unique random string and sets it as a session value and then encrypts it for form submission.

2) The server then concatenates the user agent and language and encrypts a hash of it using the random string as a seed.

3) Then, when the password is submitted:
a) the client hashes the password (sha256) and sends it;
b) the client hashes the password (md5) and sends it;
c) the client hashes the encrypted random string;
d) the client concatenates the hashed/encrypted random string with random string seed and hashed password and hashes it;
e) the client hashes the encrypted, hashed agent/language concatenate with random string seed, and sends it.

4) The server then encrypts the received hashed password, using a hash of the pass with a hash of the pass as seed, and stores a session of it.

5) The server then encrypts the random string session variable, using the string as a seed for the agent response.

6) The server then hashes the encrypted random string, with random string seed, for the random string response.

7) The server then gets the user agent and language (again) and concatenates them.

8) The server then hashes the encrypted, hashed agent/language concatenate with crypted, random string, with random string seed, seed.

9) The server then compares values:
a) The server checks to see if submitted, encrypted, hashed pass with hashed pass seed, matches the stored one.
b) The server then checks if the submitted hash of the hashed encrypted random string with random string seed, and hashed password concatenate matches the servers encrypted session of the random string with session random string seed then hashed while concatenating it with the submitted hashed (md5) pass.
c) The server then checks if the submitted hash of the encrypted hashed agent/language concatenate with encrypted random string with random string seed, matches servers check of the agent/language and random string session while hashing and encrypting them.

--------------------
FILE UPLOAD SETTINGS
--------------------
The option for basic file upload/rename/delete.

$fileupload = "off";
	Whether or not the "File Upload" option is available.

$tinymceupload = "off";
	Whether or not the filebrowsing option is available in TinyMCE.

$tinybrowser_allow_upload = "off";
	Whether or not users are allowed to upload files.

$tinybrowser_allow_edit = "off";
	Whether or not users are allowed to edit files.

$tinybrowser_allow_delete = "off";
	Whether or not users are allowed to delete files.

$tinybrowser_allow_folders = "off";
	Whether or not users are allowed to create subfolders.

$fileupload_dir_name_images = "uploads/images";
	 The directory name for images. This directory will be automatically created. For instance, if you use http://YOURDOMAIN.com/uploads/images/, the images upload directory will equal: uploads/images.

$fileupload_dir_name_media = "uploads/media";
	The directory name for media. This directory will be automatically created. For instance, if you use: http://YOURDOMAIN.com/uploads/media/, the media upload directory will equal: uploads/media.

$fileupload_dir_name_files = "uploads/files";
	The directory name for files. This directory will be automatically created. For instance, if you use: http://YOURDOMAIN.com/uploads/files/, the files upload directory will equal: uploads/files.

Create "php.ini"
	This creates a php.ini file that overrides the default file upload size limit.

--------------------	
SETUP UTILITY
--------------------
$setup = "off";
	The Setup Utility will set the correct permissions for the data directory
	- The data directory permissions will be set to 755 or 777.

--------------------
BASIC SETTINGS
--------------------
$edit_redirect = "3000";
	The redirect speed after editing a point (index.php). 1000 = 1 second
	
	
$admin_redirect = "3000";
	The redirect speed after creating a point (admin.php)., 1000 = 1 second
	
	
$edit_width = "60";
	The textarea width (rows) when editing a point.
	
	
$edit_height = "18";
	The textarea height (columns) when editing a point.
	
--------------------
TinyMCE SETTINGS
--------------------
Documentation is available in the script at:

$tiny = "full";
	TinyMCE display settings. Options are: 1) Full, 2) Advanced, 3) Simple, 4) Off.
	1) "full" is the default Edit-Point usage that has all options available.
	2) "adv" is an advanced option that lets you pick and choose between plugins.
	3) "sim" is a simple option with minimal options.
	4) "off" has no TinyMCE (WYSIWYG) available.

$tiny_compressor = "off";
	Option to use TinyMCE Compressor. This is used to speed up TinyMCE, but is an option as that it may not work well with some servers or browsers.

Custom CSS
	Use this option to create custom css styles in the TinyMCE "styles" dropdown selector. This file is created and stored for use in "edit-point/jscripts/tiny_mce/themes/advanced/css" and stored for safekeeping (in case of upgrades) in "edit-point/data".

$advhr = "on";
	Advanced hr.
$advimage = "on";
	Advanced image.
$advlink = "on";
	Advanced link.
$autosave = "off";
	Gives the user a warning if they made modifications to a editor instance but didn't submit them.
$backcolor = "on";
	Background color chooser.
$contextmenu = "on";
	Bottom menu.
$copy = "on";
	Copy button.
$cut = "on";
	Cut button.
$directionality = "on";
	Adds directionality icons to TinyMCE that enables TinyMCE to better handle languages that is written from right to left.
$emotions = "on";
	Insert smiley images into the TinyMCE editable area. 
$fontselect = "on";
	Type of font selector.
$fontsizeselect = "on";
	Font size selector.
$forecolor = "on";
	Font color button.
$fullscreen = "on";
	Fullscreen editing mode.
$iespell = "on";
	IE spellchecker.
$inlinepopups = "on";
	Makes all dialogs to open as floating DIV layers instead of popup windows.
$insertdatetime = "on";
	Insert date and time.
		$insertdatetime_dateFormat = "%Y-%m-%d";
			Date format.
		$insertdatetime_timeFormat = "%H:%M:%S"; 
			Time format.
$layer = "on";
	Adds a layer support by making it possible to create/remove and z-index block elements.
$liststyle = "on";
	List style selector.
$media = "on";
	Handles embedded media such as QuickTime, Flash, ShockWave, RealPlayer and Windows Media Player.
$nonbreaking = "on";
	This enables you to force TinyMCE to insert three &nbsp; entities when the user presses the tab key.
$noneditable = "on";
	Adds non editable elements support for MSIE and Mozilla/FF.
$paste = "on";
	Adds paste as plain text and paste from Word icons.
		$paste_create_paragraphs = "true";
			Double linefeeds are converted to paragraph elements.
		$paste_create_linebreaks = "true";
			Single linefeeds are converted to hard line break elements.
		$paste_use_dialog = "false";
			MSIE specific option, if you set this to true both Mozilla and MSIE will present a paste dialog. If you set it to false pasting in MSIE will be done directly.
		$paste_auto_cleanup_on_paste = "false";
			MSIE specific option. If you enable this feature, a word paste will be executed when the user copy/paste content to the editor.
		$paste_convert_middot_lists = "false";
			Middot lists are converted into UL lists, these will be assign a special class.
		$paste_unindented_list_class = "unindentedList";
			Enables you to specify what class to assign to the UL list of middot converted lists. Middot lists are unindented in MS Office.
		$paste_convert_headers_to_strong = "false";
			Converts H1-6 elements to strong elements on paste.
		$paste_remove_spans = "true";
			Control if the word parse operation should remove or keep span elements.
		$paste_remove_styles = "true";
			Control if the word parse operation should remove or keep style attributes.
		$paste_replace_list = "true";
			Comma separated list of search/replace chunks.
		$paste_strip_class_attributes = "all";
			Control whether or not class attributes are stripped when using pasteword.
$preview = "on";
	Preview the current content.
		$plugin_preview_width = "500";
			Preview window width.
		$plugin_preview_height = "600";
			Preview window height.
$print = "on";
	Print button.
$searchreplace = "on";
	Search/replace buttons.
$style = "on";
	Adds CSS style editing support.
$table = "on";
	Table management.
$visualchars = "on";
	Adds the possibility to see invisible characters like &nbsp;.
$xhtmlxtras = "on";
	Adds support for some XHTML elements these include cite, ins, del, abbr, and acronym.

//---------------------------------------------------------------//
// You do not need to make changes below, unless you are changing the default directory names or structure.
//---------------------------------------------------------------//

$head = "on";
	Whether or not to use the header/footer. on or off. NOTE: "on" is required for the WYSIWYG option. Do not change unless you do not want to use TinyMCE, the WYSIWYG editor.

$textdir = "edit-point";
	For instance, if your Edit-Point installation is at "http://YOURDOMAIN.com/testing/edit-point", then "$textdir = testing/edit-point".

$datadir = "data";
	Data directory name (where the .txt files, created by the script, are stored). Do not change unless you manually change the "data" directory name or location.

$pagepath = "../";
	From script directory to webpage directory.

$p = "<p>";
$p2 = "</p>";
	The start and end tags used in the html that is created. They are only used for Edit-Point script pages.


-----------------------------------------------------------------------
Upgrading
	IMPORTANT INSTRUCTIONS FOR UPGRADING TO 4.xx - ALL VERSIONS
	Upgrading from 3.xx to Current Release
	Upgrading from 2.xx to Current Release
	Upgrading from 2.0 Beta to Current Release
	Upgrading from 1.0 to Current Release
-----------------------------------------------------------------------
!!!!!! ALWAYS BACKUP YOUR DATA FIRST !!!!!!

IMPORTANT INSTRUCTIONS FOR UPGRADING TO 4.xx - ALL VERSIONS
	
	There are two (2) manual changes that need to be made to perform an upgrade to Edit-Point 4.xx.
	
	1) Edit-Point has changed it's default script directory name from "text" to "edit-point." Your existing webpages with Edit-Points will not work unless you change the new "Script Directory" setting from "edit-point" back to "text."

	2) Edit-Point has slightly changed the way that the links to Edit-Points are stored in the "data/textlinks.txt" file. Your existing textlinks.txt file has to be edited so that the existing "Edit-Points" will work with the new "Delete an Edit-Point" option. The easiest way to do this is to download the textlinks.txt file and edit it with a text editor (kwrite, gedit, notepad, etc). You can also use the "Manually add or delete Edit-Points on the Editor Page." function on admin.php. Basically, the code to your existing Edit-Points needs to be seperated by a line break. Your existing textlinks.txt has the html code for the points pretty much all running together. The "<form></form>" tages for each Edit-Point needs to be seperated. When you are finished, it should look something like the following three (3) Edit-Points:

<form action="index.php" method="post"><p><input type="hidden" name="name" value="test1" /><input type="hidden" name="cmd" value="index2" /><input name="submit" type="submit" value="Edit" /> : TEST POINT 1 </p></form>

<form action="index.php" method="post"><p><input type="hidden" name="name" value="test10" /><input type="hidden" name="cmd" value="index2" /><input name="submit" type="submit" value="Edit" /> : TEST POINT 2 </p></form>

<form action="index.php" method="post"><p><input type="hidden" name="name" value="test10" /><input type="hidden" name="cmd" value="index2" /><input name="submit" type="submit" value="Edit" /> : TEST POINT 3 </p></form>

	After backing up all of your data and performing the two manual changes,
	1) Next, upload all files and directories except the "data" directory.
	2) Now upload your saved "data" directory to the script diretory (edit-point).
	3) Now visit http://YOURDOMAIN.com/edit-point/options.php and edit your options.
	4) If you had  a custom css file, retrieve it from your data directory and either re-run the "add css" script and copy your data in, or place the css file in "edit-point/jscripts/tiny_mce/themes/advanced/css/".
	5) If you have a customized header.php, please compare the number of lines in header.php form the release your site is using with the new release header.php to make sure that no additions need to be made to you custom header.


Upgrading from 3.xx to Current Release
	1) Save your "data" directory and delete everything else.
	2) Next, upload all files and directories except the "data" directory.
	3) Now upload your saved "data" directory to the script diretory (edit-point).
	4) Now visit http://YOURDOMAIN.com/edit-point/options.php and edit your options.
	5) If you had  a custom css file, retrieve it from your data directory and either re-run the "add css" script and copy your data in, or place the css file in "edit-point/jscripts/tiny_mce/themes/advanced/css/".
	6) If you have a customized header.php, please compare the number of lines in header.php form the release your site is using with the new release header.php to make sure that no additions need to be made to you custom header.

Upgrading from 2.xx to Current Release

	1) Save your "data" directory and delete everything else.
		Delete:
			- jscripts (directory)
			- admin.php
			- config.php
			- edit.php
			- footer.php
			- header.php
			- index.php
			- options.php
			- style.css

	2) Next, upload all files and directories except the "data" directory.
		Upload:
			- images (directory)
			- jscripts (directory)
			- lang (directory)
			- admin.php
			- config.php
			- footer.php
			- header.php
			- index.php
			- info.php
			- options.php
			- setup.php
			- style.css
			- upload.php

	3) Next, upload your saved "data" directory to the script directory (edit-point).

	4) Now visit http://YOURDOMAIN.com/edit-point/options.php and edit your options.


Upgrading from 2.0 Beta to Current Release

	1) Save your "data" directory and delete everything else.
		Delete:
			- jscripts (directory)
			- admin.php
			- config.php
			- edit.php
			- footer.php
			- header.php
			- index.php
			- style.css
			
	2) Next, upload all files and directories except the "data" directory.
		Upload:
			- images (directory)
			- jscripts (directory)
			- lang (directory)
			- admin.php
			- config.php
			- footer.php
			- header.php
			- index.php
			- info.php
			- options.php
			- setup.php
			- style.css
			- upload.php

	3) Next, upload your saved "data" directory to the script directory (edit-point).

	4) Now visit http://YOURDOMAIN.com/edit-point/options.php and edit your options.


Upgrading from Edit-Point 1 to Current Release:

	1) First, backup everything on your website, for safety's sake. Most important is the "data" directory.
	
	2) Then delete everything except the "data" directory.
		Delete:
			- admin.php
			- admin2.php
			- config.php
			- edit.php
			- edit2.php
			- footer.php
			- header.php
			- index.php
			- style.css
	
	3) Next, upload all of the files in the new download except for the "data" directory.
		Upload:
			- images (directory)
			- jscripts (directory)
			- lang (directory)
			- admin.php
			- config.php
			- footer.php
			- header.php
			- index.php
			- info.php
			- options.php
			- setup.php
			- style.css
			
	4) There are two options for the next step. Option "b" is the preferred method.
	
	a) Download this file and rename it from "edit.txt" to "edit.php" and upload it to the "edit-point" directory:
	http://covertheweb.com/edit-point/files/edit.txt
	
	b) Go to "admin.php" and click the "Edit the Editor-Page" option. Each Edit-Point has a form field, so change each line that reads:
	
	<form action="edit.php" method="post">
	to
	<form action="index.php" method="post">
	
	Now add the following line to each Edit-Point form field:
	<input type="hidden" name="cmd" value="index2" />
	
	
	For example, if upgrading, your "Edit the Editor-Page" looks something like this:
	
	<form action="edit.php" method="post">
	<p>
	<input type="hidden" name="name" value="test1" />
	<input name="submit" type="submit" value="Edit" /> : test1
	</p></form>
	<form action="edit.php" method="post">
	<p>
	<input type="hidden" name="name" value="test2" />
	<input name="submit" type="submit" value="Edit" /> : test2
	</p></form>
	
	
	When you finish editing, it should look like this:
	
	<form action="index.php" method="post">
	<p>
	<input type="hidden" name="name" value="test1" />
	<input type="hidden" name="cmd" value="index2" />
	<input name="submit" type="submit" value="Edit" /> : test1
	</p></form>
	<form action="index.php" method="post">
	<p>
	<input type="hidden" name="name" value="test2" />
	<input type="hidden" name="cmd" value="index2" />
	<<input name="submit" type="submit" value="Edit" /> : test2
	</p></form>


-----------------------------------------------------------------------
TinyMCE
-----------------------------------------------------------------------
TinyMCE WYSIWYG Editor
Copyright (c)2007 Moxiecode Systems AB
http://tinymce.moxiecode.com/

TinyMCE is the WYSIWYG editor.

This version of Edit-Point uses a full featured TinyMCE. TinyMCE has many options that can be turned on with a little modification of the "header.php" file. I would suggest visiting their site for more instructions and so that you can see the full potential of what it can do.


-----------------------------------------------------------------------
Customization
-----------------------------------------------------------------------
Using your own header/footer files is pretty easy to do. The most important part of header.php is lines 8 through around 430 (from "<?php" through "?>"). Put this between your head tags (between <head> and </head>). The other lines that you want to add are:
Line 6
Line 439
Lines 444-451

Easy translation is now possible. There are three files to translate and the TinyMCE language pack has to be added for the translated language. The Edit-Point files are:
1) "edit-point/lang/en.php"

After translating the files, please email them to me (hide@address.com) and I will add them and the correct TinyMCE language files and release an updated Edit-Point.

-----------------------------------------------------------------------
Notes/Bugs:
-----------------------------------------------------------------------
- To back up your site, after you finish adding points, make a backup of all of your "*.php" files that have an Edit-point. Now all you have to do is regularly backup the "data" directory (http://YOURDOMAIN.com/edit-point/data).


- The dreaded "kind of works, but no files are modified and lots of chmod error messages in setup.php" is an ownership issue. I'll try to explain this as best as I can, without being too technical and without putting my foot in my mouth. The problem is that your files are owned by you (USER for instance) and php is running as another user (usually, www, nobody, or apache. I'll use www for the example). A possible solution is to run this command (ask your server admin if you don't have root privileges): 

chown -R www:www edit-point/

Then run the same command on all files that you will be adding  Edit-Points to. For instance, if you want to add Edit-Points to testing.php, then run this command:

chown -R www:www testing.php

Now the file and edit-point directory ownership settings should look something like this when viewed through a shell propmt or ftp:

drwxr-xr-x  4 www www    4096 Dec 10 21:12 edit-point
-rw-r--r--  1 www www     844 Dec 10 21:13 intesting.php


- If "magic_quotes_runtime" is on in your servers PHP Configuration, the Edit-Points will not work. To workaround it, his line "set_magic_quotes_runtime(0)" needs to be added to your Edit-Point include links. For instance, your include link should look like this:
<?php set_magic_quotes_runtime(0); $point = file_get_contents('YOUR/PATH/YOUR_POINT.txt'); echo $point; ?>
You can either add this everytime you add a point or modify admin.php, lines 355,362,363,690,697,698 to read:
echo "<b>&lt;?php set_magic_quotes_runtime(0); $point = file_get_contents('" . $_SERVER['DOCUMENT_ROOT'] . "/$textdir/$datadir/$nametxt'); echo $point; ?&gt;</b>


- You may experience problems with the "EMOTIONS" (smiley's) plugin if you use .htaccess to protect your directories. Please contact me for a workaround (putting the icons outside the script directory).


- If you use the edit icon there are three sizes available, or you can use your own, by editing admin.php, lines 363 and 698. You can use edit_sm.png, edit_md.png, or edit_lg.png (located in edit-point/images).


-----------------------------------------------------------------------
Todo:
-----------------------------------------------------------------------

- add edit icon size option.
- if cancel is hit when adding an edit-point, remove *.txt file.
- find spellchecker bug/fix so it can be included.
- eyecandy - templates
- think about - redo if/elseif stuff in options.php

You can contact me at: hide@address.com
Return current item: Edit-Point