In the sql update files for 2.5.28 (administrator/components/com_admin/sql/updates/...
) we have an insert query something like:
INSERT INTO `#__extensions` (`extension_id`, `name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `system_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
(900, 'plg_quickicon_eosnotify', 'plugin', 'eosnotify', 'quickicon', 0, 1, 1, 1, '', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0);
This will fail if there is already an extension installed with id 900. It would be better to not specify an id and allow the auto-increment to set it. Like so:
INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `system_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
('plg_quickicon_eosnotify', 'plugin', 'eosnotify', 'quickicon', 0, 1, 1, 1, '', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0);
Labels |
Added:
?
|
yes regular new extensions starts with ID 10000
Status | New | ⇒ | Expected Behaviour |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-01-05 10:41:16 |
Closed_By | ⇒ | brianteeman |
Closing as expected behaviour - not an issue
Somehow I had a site where this didn't happen properly. Not sure why.
IIRC 900 is in a protected range that only the core can use
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5618.