History: TikiReleaseGentooLinux
Preview of version: 7
Howto use external Adodb
emerge adodb
edit db/tiki-db.php to use external adodb libs, change IncludePath to where external adodb has been installed like this:
TikiInit::prependIncludePath('/usr/lib/php/adodb');
maybe check your php_admin_value open_basedir to include /usr/lib/php/adodb in your vhost settings or php.ini or htaccess depending on your configuration
php_admin_value open_basedir /var/www/tiki19:/tmp:/usr/lib/php/adodb
Note: tiki-install.php also depends on adodb so use this after working install, or modify tiki-install.php appropriately
Note: this works with adodb 4.61 at the time of writing ang
Howto use external Smarty
emerge smarty
edit setup_smarty.php in tikiroot directory to include external smarty
define('SMARTY_DIR', "/usr/lib/php/Smarty/"); require_once ( '/usr/lib/php/Smarty/Smarty.class.php');
and below edit the plugins_dir array, that dirname stuff is unneccessary:
$this->plugins_dir = array(»····// the directory order must be like this to overload a plugin "lib/smarty_tiki", SMARTY_DIR."plugins" );
Note: tiki-install.php also depends on smarty so use this after working install, or modify tiki-install.php appropriately
define('SMARTY_DIR', "/usr/lib/php/Smarty/"); require_once (SMARTY_DIR . 'Smarty.class.php'); and the plugins_dir array again
Note: this works with latest Smarty 2.6.7 at the time of writing ang
- we use version 2.5.5 in 1.9 CVS is at the time of writing
Note: help developing.
For Devs:
TikiWiki comes as is, bundled with some external applications and many media files - especially Smarty too.
But GentooLinux has a separate ebuild for Smarty, and hence there would be an ample opportunity separating TikiWiki from external apps, so that bare Tiki can fit in with less redundancy in any System. CVS dev. versions of Tiki already check-out separate from Smarty...
Hence, for now, the TikiReleaseGentooLinux focuses on this separation of TikiWiki in InstallTikiGentoo from internal Smarty.
Primary objective for now is the achievement of the use of external Smarty libs - (Gentoo ebuild based) with Tiki.
Secondary objective is the externalisation of media files included in TikiWiki into TikiMediaReleaseGentooLinux (e.g.: avatar images).
Tertienary objective is the use of TikiGamesGentooLinux ebuild for the easy install of TikiGames.
Fourth objective is the externalisation of TikiStyles into separate TikiStyleReleaseGentooLinux ebuilds, so that themes and templates are easily installed and extended...
Finally, the most community-extending aspect of this project is the TikiLanguageReleasesGentooLinux in line tiwh TikiProfilesDev, so that all kind of languages and cultures easily benefit from TikiWiki.
TikiWikiInternationalizationAndLanguages
InstallTikiDev
TikiProfilesDev
ContentPacksDev - TikiMediaReleaseGentooLinux, TikiGamesGentooLinux, TikiStyleReleaseGentooLinux
InstallMultipleTikis - InstallVirtualHosting, for hosting multiple virtual domains in one Tiki filebase with separate db-s
All comments and suggestions, and any kind of cooperation is very wellcome!
UserPageang
Hey, Gentoo fellows! Add your name here!
This is where new features being developed and only in CVS are documented. When the CVS becomes RC/official release, the info in the CVS docs is transferred to update the official docs (FeatureXDoc).
For a start the ebuild is going to use CVS checkout of Tiki for installing a bare 1.8 Tiki version, and patching it for the use of external Gentoo-Smarty.
Where ideas can be exchanged, debated, etc. Interested people can subscribe to the wiki page and/or to these forums as they would a mailing list.
http://bugs.gentoo.org/show_bug.cgi?id=27944
Yet Another Ebuild Is Soon To Come. 🙄