The fix was to register types earlier, thus preventing a default being registered, which was causing the duplicate.
https://github.com/habari/system/commit/589f61220c0e35eff77020ac1a4cd24ab1b20962 On Wednesday, 21 December 2011, Andy C <[email protected]> wrote: > You have just broken the referential integrity of your database. > > Odd things may happen when code is presented with 2 records for 'habari - content' when only 1 is expected. > > Not today, not tomorrow but when you are least expecting it. > > I would remove second 'habari - content' record and reinstate the unique primary key on (module, type). > > Obviously, the installer/upgrade should skip any attempts to re-insert pre-existing meta data and just add new records. > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to [email protected] > For more options, visit this group at http://groups.google.com/group/habari-dev -- Michael C. Harris http://twofishcreative.com/michael/blog IRC: michaeltwofish #habari -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
