Upgrading to Tags.App 2
Originally Tags.App was developed to handle the input and management of tagged entry data in addition to visualization and search. With the introduction of tagging into the Movable Type core, Tags.App was re-engineered to seamless integrate and enhance these new found capabilities. Movable Type has introduced many new features that significantly improve the usability and functionality to a plugin like Tags.App. Clearer recommendations and best practices for packaging plugins have also emerged.
Through this re-engineering, we believe Tags.App has the been given a strong foundation to move forward and be the best (and hopefully indispensable) plugin it can be.
See "What's New and Different in Tags.App 3" for an overview of the changes.
System Requirements
Tags.App 2 requires at least Movable Type 3.31 or Movable Type Enterprise 1.03. Like these versions of Movable Type, Perl 5.6.1 is required however we strongly recommend using Perl 5.8.1 or better.
Tags.App 2 still requires a few external libraries from CPAN all of which ship with the required versions of Movable Type. One notable change is that previous to version 2, users had to run a script to create the data tables used by the plugin to index entry tags. Tags.App now makes use of MT's database upgrading system to streamline this process.
We strongly recommend the use of FastCGI or mod_perl for the optimal performance of the tag search functionality.
Upgrading
Upgrading from Tags.App 1.x to Tags.App 2 requires the same installation process that a new user would follow. See "Installing Tags.App 2" for that process. There are a few added steps and considerations that an upgrade includes.
Movable Type will read go through any weblog that was set as Tags.App Enabled and look for space-delimited tags in the keywords field. It will autoamtically transfer all tags it finds into the MT's data tables and then clear out the keywords fields.
File Cleanup
Because of the changes in how plugins are packaged and the re-engineering of the Tags.App code a number of files will be left in your MT installation that are no longer needed.
Clearing out these files from the old version is NOT necessary and completely optional. Not clearing out these old files should have little to no impact. Do not attempt these steps if you are not comfortable with this process. Always be sure to backup your MT code directory in case you need to revert your system back to its original state.
The following files can be deleted AFTER you have installed the software and let MT run the upgrade procedure. File names are relative to your MT system directory.
- docs/mtxsearchtags.html**
- docs/mtxsearchapi.html**
- docs/mtxsearch.html**
- docs/mtgrep.html**
- extlib/MT/App/Tags.pm
- extlib/MT/Plugin/TagsApp.pm
- extlib/MT/Plugin/TagsApp/ConfigMgr.pm
- extlib/MT/TagCloud.pm
- extlib/MT/TagMap.pm
- extlib/MT/TemplateFile.pm
- extlib/MT/XSearch/ (and all its contents)
- plugins/mt-grep.pl
- plugins/mt-xsearch.pl
- plugins/mt-xsearch.pod
- plugins/tags/LICENSE
- plugins/tags/README
- plugins/tags/tmpl/default_results_blog.tmpl
- plugins/tags/tmpl/weblog_config.tmpl
- mt-load-tags.cgi
- mt-static/tagsuggest.js (Tags.App 1.2P only)
- mt-tags.cgi
- mt-tagsmgr.cgi (Tags.App 1.2P only)
- schemas (and all its contents)
- xsearch-sample.template
- xsearch.txt
** - the docs directory may be in the mt-static directory along with other documentation.
