Looking for the latest version? Download wikindx4.2.2.zip (3.6 MB)
Home
Name Modified Size Downloads / Week Status
Totals: 8 Items   3.6 kB 3
plugins wikindx v4.x 2013-05-30 33 weekly downloads
bibliographic styles wikindx v4.x 2013-04-21 22 weekly downloads
localizations wikindx v4.x 2013-03-10 11 weekly downloads
scripts wikindx v4.x 2013-02-15 11 weekly downloads
wikindx CORE PROGRAM 2013-02-10 2222 weekly downloads
plugins pre-wikindx v4.1 2013-01-08 22 weekly downloads
localizations pre-wikindx v4.1 2013-01-08 11 weekly downloads
README.txt 2013-05-13 3.6 kB 33 weekly downloads
************************* * WIKINDX v4.2.x * ************************* After unzipping into your web server's web folder, read the README files in wikindx4/trunk/docs/index.html If you are upgrading a previous installation of WIKINDX 4.1.x to 4.2, simply overwrite the existing installation. $WIKINDX_WIKINDX_PATH has been added to config.php.dist and should be copied to config.php. Otherwise, if you are upgrading, your previous WIKINDX version should be v3.8.2 or v4.1.x. v4.2.x will detect the earlier database and will upgrade it at first use. If you have a database from an even earlier version, you should first upgrade it to v3.8.2 using the WIKINDX v3.8.2 code then convert that database to v4.2.x using the v4.2.x code. For a v3.8.2 upgrade, you will need to copy config.php.dist to config.php and edit the latter file. At the very least, for a fresh install, you should create a database, assign a wikindx user to it with GRANT ALL permissions, and copy config.php.dist to config.php and edit the latter file. In all cases, ensure that 'files/', 'attachments/', 'templates/compiled_templates', 'styles/cache' and 'styles/bibliography/' and the XML files within 'styles/bibliography/xxx/' folders are writable by the web server user (usually 'nobody'). If you are running WIKINDX locally on Windows (using something like WAMP), you can skip this step as the folders will be writable by default. Additionally, in any plugin folder, index.php and the config.php file (if it exists) should also be writable. If you are running WIKINDX locally on Windows (using something like WAMP or XAMPP), you can skip this step as the folders will be writable by default. LOCALIZATIONS: Localizations for v4 should be unzipped with their directory structure into wikindx4/languages/ and the localization directory and files within made writeable by the web user. (v4 lets administrators configure localizations directly within the web browser interface.) Localizations for versions of WIKINDX prior to v4.1.x can be imported using the localization plugin. Missing messages in the converted files will be replaced automatically by English messages when using WIKINDX. PLUGINS: Plugins for v4 should be unzipped with their directory structure into wikindx4/plugins/ and the plugin directory and files within made writeable by the web user. (v4 lets administrators configure plugins directly within the web browser interface.) Plugins for versions of WIKINDX prior to v4.2.x cannot be used with 4.2.x. v4.1.x plugins will be configurable in the Admin|Plugins menu but will not be visible in the menu system. You should download the latest plugins from the Sourceforge site. USING SVN: This is complex software developed by simple humans -- it will have bugs. If these bugs are reported on the SourceForge tracker (https://sourceforge.net/tracker/?group_id=94435&atid=4842858) then they can be quickly dealt with. It is not efficient to make a full version release for every bug fix (or new feature) so such fixes will be uploaded to the SVN repository until a sufficient number have accumulated to justify a new version release. Therefore, if you wish to keep up with the very latest post-bug fix, pre-version release WIKINDX, you should access the SVN repository. Details of how to access it (it's very easy) can be found here: https://sourceforge.net/apps/trac/sourceforge/wiki/Subversion and the base SVN address you need is: svn checkout svn://svn.code.sf.net/p/wikindx/code/trunk The main code is under trunk/ while plugins are maintained under plugins/
Source: README.txt, updated 2013-05-13