Difference between revisions of "Managing Component Updates (Manifest file)"
From Joomla! Documentation
|Line 46:||Line 46:|
Revision as of 15:59, 27 May 2011
This article or section is incomplete, which means it may be lacking information. You are welcome to assist in its completion by editing it as well. If this article or section
Articles in this series
Manifest File (mytest.xml)
The manifest file in this example is very similar to that of normal components. Important contents for this example include:
Note the inclusion of the SQL folder in the administration files section. This tells Joomla to copy the contents of this folder to the web site during install or update. The SQL folder contains individual SQL files for each incremental update.
<administration> <files folder="admin"> <folder>sql</folder> </files> </administration>
This is the name of the component. The 'getParam($key)' method in the script.php file uses this value to identify the correct row in the extensions table. The manifest_cache field in the extensions table has the version string for the currently installed component.
Joomla stores this value in the manifest_cache field of the extensions table. The extensions table is where the custom code in the script.php file reads the version string of the currently installed component, and compares it to the version string of the update. The custom component code uses this comparison to abort an update, if the version sequence is not allowed. Joomla also compares this string to the SQL update file names, to determine which SQL commands to execute.
This defines the directory that contains SQL files for component incremental database updates. You may choose to put the SQL files somewhere else in your component release, but make sure their location is documented here.
<update> <schemas> <schemapath type="mysql">sql/updates</schemapath> </schemas> </update>