Hi Ishai, I kind of agree with you, however it is out of my control. any way, for this problem i decided to use the old ( 14 version) content type hub. so that I can publish to old sites, once all the sites upgraded then I will upgrade the content type hub. for the new sites, i will create as 14 version first, then consume, then I will do the upgrade. bit hassle however no choice. Thanks for you comments Ishai. sutha.
From: is...@exd.com.au To: ozmoss@ozmoss.com Subject: RE: content type hub in v 15, subcriber in 14. Date: Mon, 23 Feb 2015 22:56:30 +0000 Sorry to be of no real help, but my best recommendation – do not use a content type hub. The implementation is not robust enough. I recommend to clients to develop own scripts to replicate content type and site column changes. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Sutha Thavaratnarajah Sent: Monday, 23 February 2015 4:23 PM To: ozmoss@ozmoss.com Subject: content type hub in v 15, subcriber in 14. Hi , Recently I upgraded our SharePoint environment. We have challenge, some of the sites are pending for the visual upgrade. Our content type hub was upgraded as some new sites require to consume the latest content types. Challenge is our pending visual upgrade sites not getting the latest updates for the content type from the hub. I am getting following error. The compatibility level 15 of the content type hub site is different from the compatibility level of this site 14 to be clear: Hub in v 15 , subcriber in v 14. any suggestion. thanks. Regards Sutha _______________________________________________ Sponsored by Infotext - Amazing Search for Microsoft SharePoint - http://www.infotext.com/ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ Sponsored by Infotext - Amazing Search for Microsoft SharePoint - http://www.infotext.com/ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss