Description of problem:
When a ContentItem is created through the PageCreate class, the item is created
and then the Bundle is created.  In the constructor for ContentBundle, there is
a call to addInstance.  Inside of addInstance, it grabs all of the current
instances to make sure that there is not currently an instance of that language.
 This check causes a database hit.  However, before the database can be hit, the
persistence layer has to flush the content item.  Thus, the content item is
saved and inside of the afterSave method, the parent is null so no context is
set.  Then, inside of the addInstance method the parent is set.  Then, when the
content item is saved again, the context still is not set because this time
m_wasNew returns false.  So, the context of the primary instance of the bundle
is never set which means that the permissions are not correct.  Specifically,
this makes it impossible for a public user to view a published item and it makes
the workflow open to pretty much anyone.  the following patch is one way to fix
this problem:

[randyg@graebner intragroupe]$ diff -u cms/src/com/arsdigita/cms/ContentBundle.java
intragroupe/src/com/arsdigita/cms/ContentBundle.java 
+++ intragroupe/src/com/arsdigita/cms/ContentBundle.java	Wed Oct 22 16:04:16 2003
--- cms/src/com/arsdigita/cms/ContentBundle.java	Wed Oct 22 15:59:10 2003
@@ -89,7 +89,6 @@
         Assert.exists(primary, ContentItem.class);
         setDefaultLanguage(primary.getLanguage());
         setContentType(primary.getContentType());
+        primary.setParent(this);
         addInstance(primary);
 
         super.setName(primary.getName());


Version-Release number of selected component (if applicable):
6.0

How reproducible:
Always

Steps to Reproduce:
1.  Create a content item and notice that it does not appear in object_context_map
2.
3.
    
Actual results:
the bundle should be the context

Expected results:
the object has no context

Additional info: