I am using ContentO to create a new type and assign it to a container. After I create the type, if I go in and edit something (description, lable, assign to container, etc and submit, I get the following error:

* user warning: Duplicate entry 'category_nodeapi_Come_Worship_With_Us_Type_conta' for key 1 query: INSERT INTO variable (name, value) VALUES ('category_nodeapi_Come_Worship_With_Us_Type_containers', 'a:1:{i:0;i:2;}') in /home/pittsfor/public_html/drup474/includes/database.mysql.inc on line 121.
* warning: Cannot modify header information - headers already sent by (output started at /home/pittsfor/public_html/drup474/includes/database.mysql.inc:121) in /home/pittsfor/public_html/drup474/includes/common.inc on line 269.

This is a very clean install and is the first content type created and assigned to one of three containers just created.

I am using ContentO version: contento-4.7.x-1.x.tar.gz

Hope this helps. I am going to try reverting back to some older versions as this is a show stopper.

Rich
(rl)

Comments

rl’s picture

rl commented
Title: user warning: Duplicate entry » user warning: Duplicate entry - work around available

Here is more info:

When I went back into the Content type, the container selection shows All Except and is not what I originally set it to.

Warning: Table 'watchdog' was not locked with LOCK TABLES query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Duplicate entry 'category_nodeapi_Come_Worship_With_Us_Type_conta' for key 1\nquery: INSERT INTO variable (name, value) VALUES ('category_nodeapi_Come_Worship_With_Us_Type_containers', 'a:1:{i:0;i:3;}') in /home/pittsfor/public_html/drup474/includes/database.mysql.inc on line 121.', 2, '', 'http://www.pittsfordcc.org/drup474/?q=admin/settings/content-types/Come_...', 'http://www.pittsfordcc.org/drup474/?q=admin/settings/content-types/Come_...', '70.100.109.250', 1164494863) in /home/pittsfor/public_html/drup474/includes/database.mysql.inc on line 121

Here is a work around...

You will need to delete you content type that caused the error (I deleted everything since there was no content yet).

Create the new content type as you would... DO NOT give it Category behavior (yet). Make sure that setting is None. After creating the new type, go back in through the configuration menu and then it is ok to specifiy Category behavior with the radio button. Select your Container - save configuration and all is well.

When I tried this on my test site I followed the above procedure, but when I was on my production site, I was "smarter" and shortened up the procedure since I "knew" what I was doing and selected category behavior at the time I created the new content.

I hopes this helps someone.

Rich
(rl)