[Fusionregistry-commitlog] fusionregistry INSTALL.txt,NONE,1.1
Brought to you by:
copland007
Menu
▾
▴
[Fusionregistry-commitlog] fusionregistry INSTALL.txt,NONE,1.1
|
From: CVS c. <fus...@li...> - 2007-06-06 20:38:28
|
Update of /cvsroot/fusionregistry/fusionregistry In directory sc8-pr-cvs17:/tmp/cvs-serv32555 Added Files: INSTALL.txt Log Message: Initial import into cvs. --- NEW FILE: INSTALL.txt --- /*-------------------------------------------------------------------------\ | | ======================================================== | Fusion Registry GPL v3.0.3 | Copyright (C) 2007 Fusion Scripts | | This program is free software; you can redistribute it and/or | modify it under the terms of the GNU General Public License | as published by the Free Software Foundation; either version 2 | of the License, or (at your option) any later version. | | This program 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 General Public License for more details. | | You should have received a copy of the GNU General Public License | along with this program; if not, write to the Free Software | Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. | ======================================================== | | Email: in...@fu... | Web-Site: http://www.fusionscripts.com/ | | $Id: INSTALL.txt,v 1.1 2007/06/06 20:38:25 copland007 Exp $ | \-------------------------------------------------------------------------*/ ============================================================================ These instructions are for a new fresh install. Fusion Registry v3.0.3 only works with IPB v2.2.x! ============================================================================ Upgrading and Installing note: As with any change to files on your server you should always make a backup of any files that will be modified or removed. It would also be good practice to make a backup of your database. ============================================================================ Step 1: Upload the following files ============================================================================ /cache/lang_cache/en/lang_registry.php /sources/components_acp/* (and all sub files/folders) /sources/components_public/* (and all sub files/folders) /sources/portal_plugins/* /sources/tasks/registrysessions.php /style_images/1/registry_images/* Ensure that your ./uploads directory permissions are CHMOD 0777 ============================================================================ Step 2: Run Installer ============================================================================ To install the needed SQL tables and data point your internet browser to the new installer. DO NOT EXECUTE this from within any site management software such as Cpanel! http://yourdomain.com/forum/sources/components_public/fusionscripts/fusionregistry/install/ Follow the installer steps and when you are finished remove the install directory from your server. ============================================================================ Step 3: Import and setup the skin ============================================================================ This is a tricky procedure, please follow it closely ;) Since the Fusion Registry skin combines edits to other template bit groups, and custom macros, you can not simply place a copy of the skin_*.php files into your skin cache folders and be done. If for some reason your XML skin import function is not working you need to resolve that problem before continuing to ensure skin inheritance functions properly! i) Head into your ACP -> Look & Feel -> Skin Import/Export ii) In the 'Upload XML Template set' box, click Browse and choose the included "ipb_skin-fusionregistry.xml.gz" file. iii) In the 'New Skin Set Name?' box you may leave it blank or type in a custom name. iv) Click Import Skin XML. Ensure no errors occur. If you have a skin set already that you have done modifications to, then set that skin to have this newly imported skin as the parent. This will ensure that the skin inheritance works and you maintain all your custom edits along with the Fusion Registry elements. To set another skin set to have the garage skin set as the parent click on the other skin set on the 'Skin Manager' page, choose 'Edit Settings'. For the 'Skin Set Parent?' option choose 'Fusion Registry' or whatever you named the newly imported skin set. Click Edit Skin Settings. It is not suggested that you do your site skin modifications to the imported Fusion Registry skin set. Keep the Fusion Registry skin set as is so future upgrades to the Fusion Registry skin will be painless for you ;) ============================================================================ Step 4: Configuring session cleanup task ============================================================================ Although this step is not required it is highly recommended to keep your ibf_registry_sessions table nice and tidy. Head into your Task Manager and click 'Add New Task' near the bottom. Enter the following values: - Task Title: "Fusion Registry Session Cleanup" - Task Short Description: "Remove old Fusion Registry sessions" - Task PHP File To Run: "registrysessions.php" - Time Options... - Task Time: Minutes: "0" - Task Time: Hours: "Every Hour" - Task Time: Week Day: "Every Week Day" - Task Time: Month Day: "Every Day of the Month" - Enable Task Logging: "Yes" - Enable Task?: "Yes" ============================================================================ Step 5: Importing and setting up the component settings ============================================================================ Once you complete this process below you will find the administration for your Fusion Registry in your ACP -> Components screen. If you have sub-admins you can also configure permissions for Fusion Registry administration through the ACP -> Admin -> Manage Restrictions page. This process will also automatically add a link to your board header. i) Head into your ACP -> Admin -> Manage Components. ii) In the 'Upload XML components file from your computer' box, click Browse and choose the included "fusionregistry_component.xml" file. iii) Click Import. ============================================================================ All done! ============================================================================ You can access Fusion Registry by pointing your browser to: http://www.yoursite.com/forums/index.php?autocom=registry Change yoursite.com to your website name. The first thing you will want to do is go into your AdminCP and go through the Configuration options for Fusion Registry, reading each carefully! Then add your Modification Categories. Please note that many features are disabled by default, you will need to enable them in your AdminCP. All editable text is available in the language section of your AdminCP under the filename lang_registry.php. |
