Clearly this is a bug, and I know the workaround but where can I log this as an issue? Connect has no way to submit issues back to the sharepoint team. The affected product is MOSS Enterprise SP2 (no CUs applied)
Repro:
- Create a site collection with publishing template (e.g. at /)
- Create variation labels (e.g. english/french)
- Modify the root /Pages library (which will eventually host the VariationRoot.aspx page) to NOT require checkout for editing files (via settings > versions)
- Attempt to create hierarchy
Failed
Result from LRO log:
<error><message>The file "Pages/VariationRoot.aspx" is not checked out.</message><full>Microsoft.SharePoint.SPException: The file "Pages/VariationRoot.aspx" is not checked out. ---> System.Runtime.InteropServices.COMException (0x8107090F): The file "Pages/VariationRoot.aspx" is not checked out.
at Microsoft.SharePoint.Library.SPRequestInternalClass.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
at Microsoft.SharePoint.Library.SPRequest.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
at Microsoft.SharePoint.SPFile.CheckIn(String comment, SPCheckinType checkInType, Boolean bIsMigrate, SPUser modifiedBy)
at Microsoft.SharePoint.SPFile.CheckIn(String comment, SPCheckinType checkInType)
at Microsoft.SharePoint.Publishing.Internal.VariationSettings.CreateVariationRootPage(PublishingWeb area)
at Microsoft.SharePoint.Publishing.Internal.VariationSettings.CreateHierarchies(LongRunningOperationJob lroLogger, List`1 errors)
at Microsoft.SharePoint.Publishing.Internal.WebControls.CreateVariationHierarchiesLro.CreateVariationHierarchies()</full><customData>The file "Pages/VariationRoot.aspx" is not checked out.</customData></error>
Cleary the answer is to leave the root Pages library alone, however, it took us a long long time to find this issue because we were using a custom feature to create the variations hierarchy in a custom site definition (ONET.xml) - lots of mud in the way.
So, where can we log these things?