Introduction | |
|
Maintenance and configuration of the script is fairly easy - I've tried to group features together, so should you require a feature, you comment it and its dependencies out of the file, do a 'cvs up' and re-run the script to activate changes. This is the first step to isolating features for automated installation scripting. I've already made a few discoveries of dependencies - such as commentslib.php is dependent on webmail (who would have thought đŻ ). With regard to WYSIWYCU, I've already started making changes to Tiki HEAD code, with an introduction of $lib_libraryname variables, which validate that a library exists and any features dependent on this library are enabled or disabled accordingly. If the library is missing, the checkbox is replaced with a 'Not Installed'. See $lib_spellcheck in tiki-setup.php and tiki-admin-include-wiki.tpl. I know that tiki-setup.php is not the correct place for library checking and will change it later when I find where. The name of the script is doc/devtools/tikilite.sh. Execute it from the top of you tiki installation. | |
HowTo | |
|
The current defaults are english language and Moreneat theme. These can be modified from the script. To Install
To Update
Its that simple. | |
Motivation | |
|
This page would be a documented guide to help them determine what they can easily remove, where to do it and what tables it uses. Please feel free to add to this page. Add to it a versioning scheme ... It may become a resouce also for further development and for crossreferencing all files related to certain pieces of tiki, should something like TikiCoreWishlist or TikiCorePrototype be developed in the future and step by step conversion of the existing features would need to be done. It would also give us a picture of how intertwined some features are with others in contrary to distinct features. | |
The works | |
|
for every feature, add the database tables it needs. Then add the files that are theirs solely. Then add the files they depend on that are files belonging to other features. As well as database tables that belong to others. Also make sure that any library used (besides Smarty/adodb) is also mentioned, every img for a theme, ... | |
An example would be | |
|
| |
MyFeature | |
|
| |
Features List | |
|
| |
Wiki | |
|
| |
Trackers | |
|
| |
Blogs | |
|
| |
Articles | |
|
| |
Image Galleries | |
|
| |
File Galleries | |
|
| |
Submissions | |
|
| |
FAQs | |
|
| |
Forums | |
|
| |
Chat | |
|
| |
Directory | |
|
| |
Trackers | |
|
| |
Newsreader | |
|
| |
Webmail | |
|
| |
Polls | |
|
| |
Surveys | |
|
| |
Quizzes | |
|
| |
Ephemerides | |
|
| |
Featured links | |
|
| |
Search | |
|
| |
Banners | |
|
| |
Full Text Search | |
|
| |
Games | |
|
| |
Search stats | |
|
| |
Newsletters | |
|
| |
Live support system | |
|
| |
Workflow engine | |
|
| |
Mini Calendar | |
|
| |
Calendar | |
|
| |
Themes | |
Warning: some themes have their own set of images in img or other dirs. Please see the templates in $tikidir/templates/styles/ | |
Modules | |
| |
Plugins | |
|
| |
Maps | |
|
| |
Charts | |
|
| |
Newsletters | |
|
| |
Menu builder | |
|
| |
Template editor | |
|
| |
HawHaw | |
|
| |
Voice | |
|
| |
... please fill on the list with features, modules, themes (although for them it is almost straightforward to remove) | |