From: <var...@us...> - 2021-08-04 08:34:17
|
Revision: 10421 http://sourceforge.net/p/phpwiki/code/10421 Author: vargenau Date: 2021-08-04 08:34:15 +0000 (Wed, 04 Aug 2021) Log Message: ----------- Update instructions, remove old stuff Modified Paths: -------------- trunk/INSTALL trunk/README trunk/TODO trunk/UPGRADING trunk/doc/INSTALL.MacOSX trunk/doc/INSTALL.flatfile Modified: trunk/INSTALL =================================================================== --- trunk/INSTALL 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/INSTALL 2021-08-04 08:34:15 UTC (rev 10421) @@ -1,11 +1,8 @@ REQUIREMENTS -PhpWiki 1.6.0 requires a web server with at least PHP version 5.3. -PhpWiki 1.6.0 is compatible with the PHP 7.0 series. +PhpWiki 1.6.0 requires a web server with at least PHP version 5.3.3. +PhpWiki 1.6.0 should work for all PHP releases from 5.3.3 to 8.0.9. -All users of PHP are strongly encouraged to upgrade to PHP 5.6 -or PHP 7.0. - Visit <http://www.php.net> and <http://php.net/downloads.php> for downloads and information. @@ -15,19 +12,6 @@ installation and configure options. <https://www.php.net/manual/en/installation.php> -Since version 1.3.0 PhpWiki uses the 'DB.php' from PEAR, a database -abstraction layer which is part of PHP. PhpWiki version 1.3.3 and later -includes the necessary PEAR libraries and will use it if your system -PEAR library can not be found. For more information about PEAR -see <http://pear.php.net/>. -PhpWiki version 1.3.7 and later includes the ADODB libraries and will -use it for DATABASE_TYPE=ADODB. ADODB has more features, can use yet -unsupported backends out of the box, and this is where SQL development -happens. ADODB improvements are then backported to the stable PEAR -backend (which often suffers from bad upstream PEAR libraries) and to -PDO for php5. - - QUICK START INSTRUCTIONS Copy 'config/config-dist.ini' to 'config/config.ini' and edit the @@ -112,7 +96,7 @@ CERT, malicious users can embed HTML in your pages that allow pure evil to happen: - <http://www.cert.org/advisories/CA-2000-02.html> + http://www.cert.org/advisories/CA-2000-02.html Set the ENABLE_RAW_HTML to true in 'config/config.ini' to allow embedded HTML, but you should NEVER do this if your Wiki is publicly @@ -128,12 +112,12 @@ 4. PATCHES Post patches to: - <http://sourceforge.net/tracker/?func=add&group_id=6121&atid=306121> + https://sourceforge.net/p/phpwiki/patches/ 5. BUGS Post bugs to: - <http://sourceforge.net/tracker/?func=add&group_id=6121&atid=106121> + https://sourceforge.net/p/phpwiki/bugs/ 6. SUPPORT @@ -141,6 +125,4 @@ <php...@li...> You can join this list at: - <http://lists.sourceforge.net/lists/listinfo/phpwiki-talk> - -FIN + http://lists.sourceforge.net/lists/listinfo/phpwiki-talk Modified: trunk/README =================================================================== --- trunk/README 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/README 2021-08-04 08:34:15 UTC (rev 10421) @@ -5,16 +5,6 @@ See ./INSTALL for installation notes. Read ./UPGRADING before upgrading from a previous version of PhpWiki. -Supported browsers: - -Phpwiki should work with the following browsers: -* Firefox >= 2 -* Safari >= 5 -* Opera >= 8 -* Chrome >= 6 -* Konqueror >= 3.5 -* Edge - Additional docs: doc/: @@ -33,8 +23,7 @@ CREDITS HISTORY -For a list of current bugs see: - https://sourceforge.net/bugs/?group_id=6121 +For a list of current bugs see: https://sourceforge.net/p/phpwiki/bugs/ The fastest and out-of-the-box version uses DATABASE_TYPE=dba, a dbm file in the /tmp directory; you may wish a more permanent @@ -44,4 +33,3 @@ implementations have the full set of features; DBM and mSQL are missing only a few, and the flat file implementation is solid and waiting for your improvement. All are suitable for production. - Modified: trunk/TODO =================================================================== --- trunk/TODO 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/TODO 2021-08-04 08:34:15 UTC (rev 10421) @@ -1,13 +1,5 @@ -== Blockers == -* can no longer save UserPreferences: Warning: "Attempt to assign property of non-object" - (partial revert to get in work again) -* WantedPages give too many pages (from interwiki map) - (to be tested in both Pear and ADODB) -* revert of Patch 3024787 by Sébastien Le Callonnec (caused an SQL syntax error) - ----- - short-term TODO: +* WantedPages gives too many pages (from interwiki map) * rename should check existing subpages and rename these also. * Sidebar: merge AVL theme (internal MonoBook derivate with customizable box states) with Sidebar Modified: trunk/UPGRADING =================================================================== --- trunk/UPGRADING 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/UPGRADING 2021-08-04 08:34:15 UTC (rev 10421) @@ -1,158 +1,9 @@ To migrate to a new phpwiki installation you might want to backup your old pages (best via a zip dump), configure your new installation, and restore the old pages in PhpWikiAdministration. -UPGRADING from 1.3.7 on requires just ?action=upgrade. -Can't unpack bad cached markup. Probably php_zlib extension not loaded. -======================================================================= -Sign in as ADMIN_USER, go to PhpWikiAdministration#Purge_Markup_Cache -and click on the [Purge Cache] button. - ?action=upgrade =============== -To upgrade default pages, the database and some config settings +To upgrade default pages and some config settings add "?action=upgrade" to your HomePage url and press "Enter", which will do most of the upgrades automatically. - -You might need to enter the DBADMIN_USER and DBADMIN_PASSWD in -config/config.ini for SQL databases and default permissions. - -The importer looks at the Date header of the page. In your current wikidb -against the creation date of the pgsrc, you want to import. -If you changed your pages after I changed the pgsrc pages, -they will not be upgraded. - -Or just upgrade your configuration as described below. - -UPGRADING since 1.3.11 -====================== -?action=upgrade should be enough. - -UPGRADING since 1.3.10 -====================== -?action=upgrade should be enough. - -UPGRADING from 1.3.9 -====================== -At first you have to manually create a config/config.ini based on -config-dist.ini and your previous index.php. We don't have a script, -to do that automatically. - -mysql: - ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT; -NOTE: ?action=upgrade does this also, if your mysql user has the -ALTER permissions or DBADMIN_USER and DBADMIN_PASSWD are set. - -UPGRADING from 1.3.7 -====================== -mysql + postgres: - ALTER TABLE session ADD sess_ip CHAR(15) NOT NULL; - CREATE INDEX sess_date ON session (sess_date); - -postgres: - New pref and session tables have been added for more - efficiency. - -user and themes: - -WikiUser and signin.tmpl changed from $user->getId() to -$user->getAuthenticatedId() -Authenticated reflects the level (confirmed by password), -Signed just the username (possibly by cookie only) - -pgsrc: - -To upgrade not-existing pages add "?action=upgrade" to -your HomePage url and press "Enter", which will -add all fresh pages from pgsrc to your pageset. -If you deleted some pages on purpose, you'll have to removed -them again with PhpWikiAdministration/Remove then. - -There's no smart "Merge Diffs" yet to upgrade existing docs, -this will come with the next release. Also upgrading the -database automatically. - -UPGRADING from 1.2.x -====================== -FIXME: WARNING WARNING: The schemas used by the new databases -are completely incompatible with schemas in any previous version -(i.e. before release 1.3.1 of PhpWiki). If you install this new -PhpWiki, you must start with a new empty database (currently -either mysql, postgres or dba). (It will be filled with the -usual default pages.) - -FIXME: add more. - -Here's an excerpt from a note I posted on phpwiki-talk with my -recommendation on how to move a wiki from and older version of -PhpWiki to a 1.3.x PhpWiki: - -From: Jeff Dairiki <da...@da...> -Cc: php...@li... -Date: Fri, 9 Nov 2001 11:33:18 -0800 - -> Now, say I want to migrate all my 1.2.1 pages. I need to do a zip dump -> (does the admin page let me do that?) and then.... what? - -It's still a bit of a messy process at this point. Here's my suggestion. - -1. Start 1.3.x with an empty database. Browse the FrontPage. This should -fill the wiki with the distributed default 1.3.x pgsrc. (You've probably -already gotten this far.) - -2. Make a zip dump of your 1.2 wiki. If the contents of -PhpWikiAdministration are correct there should be a links -(near the top) which will do that for you. You need to be -in admin mode, though. This means you must have set an -admin user and passwd in admin.php, and you should be browsing -through a URL like: - http://path.to.your/wiki/admin.php?PhpWikiAdministration -(If your PhpWikAdministration page is broken, then - http://path.to.your/wiki/admin.php?zip=all -should get you a zip dump.) - -WARNING! WARNING! WARNING! There is a bug in releases 1.2.0 -and 1.2.1 of PhpWiki which results in corrupt zip dumps if -you are using the DBA, DBM or flat-file backends. If you -are using one of those backends you should make sure to -fix that bug (see note below) before making the zip dump. - - -3. Now upload your zip dump to your new 1.3 wiki. (First you need to -have set the admin user/passwd in the new index.php.) You should -be able to use the "Upload File" form on the PhpWikiAdministration -page. - - -If that works, the pages from your 1.2 wiki have now overwritten -the 1.3 pages (though the 1.3 pages are still saved in the archive). -This will break a bunch of 1.3 functionality until you restore -the page contents. Of the top of my head, some pages for which -this will be an issue are: - MostPopular, RecentChanges, PhpWikiAdministration, - MagicPhpWikiURLs, and ReleaseNotes. - -To restore these pages to the original (1.3) contents: - -4a. Login as the administration user (using the SignIn button at the -bottom right corner of the page.) (You need to do this because -some of the pages which need fixing are locked.) - -4b. Browse to a page which needs restoring. Hit the "History" button -(at the bottom of the page). This should get you a list of all -archived versions of the page. - -4c. Browse to the archive 1.3 version of the page (probably version -number 1) by clicking on the version number of the desired version. - -4d. Click the "Edit old revision" button (bottom of page). This should -get you to the edit form. - -4e. Click the "Save" button. This should save the archived page contents -as the current contents. - -We really need to figure out a way to simplify this process, but, for now, -that's what you gotta do. - -An older note on the same subject can be found at: - http://sourceforge.net/forum/message.php?msg_id=107858 Modified: trunk/doc/INSTALL.MacOSX =================================================================== --- trunk/doc/INSTALL.MacOSX 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/doc/INSTALL.MacOSX 2021-08-04 08:34:15 UTC (rev 10421) @@ -97,20 +97,6 @@ <http://versiontracker.com/macosx/> <http://fink.sourceforge.net/> -PHP 4.1 and Mac OS X --------------------- - -The version of PHP 4.1 from Mark Liyanage's web site requires an -updated PEAR library. PhpWiki seems to work anyway but it will produce -warnings about a depreciated user function with each page load. - -1. Move the current contents of '/System/Library/PHP' into a backup - folder, such as '/System/Library/PHP/PEAR-4.0.6'. - -2. Take the contents of the 'pear' folder from the official PHP 4.1 - tarball (php-4.1.0.tar.gz) and move it into '/System/Library/PHP'. - - PhpWiki Configuration Notes --------------------------- Modified: trunk/doc/INSTALL.flatfile =================================================================== --- trunk/doc/INSTALL.flatfile 2021-08-04 07:55:38 UTC (rev 10420) +++ trunk/doc/INSTALL.flatfile 2021-08-04 08:34:15 UTC (rev 10421) @@ -7,7 +7,7 @@ You should read the main INSTALL file before this one (it's not long and complicated so go ahead and we'll wait for you right here). -INSTALLATION NOTES for 1.3 +INSTALLATION NOTES Set DATABASE_TYPE = file in config/config.ini, check DATABASE_DIRECTORY not to start with /tmp, @@ -15,14 +15,6 @@ The webserver will then start to create this directory with the correct permissions and populate the database. -INSTALLATION NOTES for 1.2 - -First, edit lib/config.php and set the database to "file": - - $WhichDatabase = 'file'; // use one of "dbm", "mysql", "pgsql", "msql", - // or "file" - - Now, the key thing is you need a directory that the web server can read and write to. This is where it will store current and archived pages. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |