You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by Sarwar Bhuiyan <sa...@gmail.com> on 2012/11/10 12:18:56 UTC
RE: POST operation modifying jcr:primaryType
Hi all,
Has there been any change recently to the sling post servlets to enable the
modification of the jcr:primaryType? Or was that always modifiable?
At the risk of posting something that should be posted on the CQ forum, I'm
facing a problem where if a page properties dialog is submitted from the
/siteadmin, it is sending
./jcr:primaryType=unstructured
The jcr:primaryType should really be cq:PageContent but that's another bug
I suppose.
Now, when the POST completes, I can see that the jcr:content node's
jcr:primaryType has indeed been modified to nt:unstructured. The issue is
occuring on a CQ5.5 with sevice pack 1.
I tried this on the GA version of CQ5.5 and the problem does not occur
there even though ./jcr:primaryType is also posted as nt:unstructured there
too. For those on the CQ forum, any idea why this is being posted from
siteadmin?
Apologies for the cross posting but I believe there is a problem on both
sides
Thanks.
Sarwar
Re: [day-communique] RE: POST operation modifying jcr:primaryType
Posted by Sarwar Bhuiyan <sa...@gmail.com>.
Thanks to all for the response.
>From what I could see, the page's jcr:content did get created as
cq:PageContent but then later if we changed any dialog properties from
siteadmin, the type changed. The knockon-effect of that is that search
results would disappear after the page props dialog changed.
Good to know about the sling change.
Cheers,
Sarwar
On Sat, Nov 10, 2012 at 7:06 PM, David Gonzalez <da...@gmail.com>wrote:
> Slightly off topic, but iirc the PageManager shipped w 5.5 types newly
> created pages' jcr:content nodes as nt:unstructured.
>
> Sent from my iPhone
>
> On Nov 10, 2012, at 1:12 PM, Davide <ge...@gmail.com> wrote:
>
> > On 11/10/2012 05:38 PM, Mark Adamcin wrote:
> >> I can confirm that this is happening on our CQ5.5 SP1 instances and
> >> that we only discovered it this week.
> >
> > I don't remember the issue in SP1 but it could be. Definitely it doesn't
> > appear in SP2 and SP2.1. IMHO the quickest solution is to install the
> > latest SP.
> >
> > If you can't do it right now, you could try by overlaying the
> > */libs/cq/ui/widgets/source/widgets/wcm SiteAdmin.js and
> > SiteAdmin.Actions.js with a version from SP2.1.
> >
> > See if it solves the problem or creates a new one :)
> >
> > HTH
> > Davide
> >
> >
> > *
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Day Communique" group.
> > To post to this group, send email to day-communique@googlegroups.com.
> > To unsubscribe from this group, send email to
> day-communique+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/day-communique?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Day Communique" group.
> To post to this group, send email to day-communique@googlegroups.com.
> To unsubscribe from this group, send email to
> day-communique+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/day-communique?hl=en.
>
>
Re: [day-communique] RE: POST operation modifying jcr:primaryType
Posted by David Gonzalez <da...@gmail.com>.
Slightly off topic, but iirc the PageManager shipped w 5.5 types newly
created pages' jcr:content nodes as nt:unstructured.
Sent from my iPhone
On Nov 10, 2012, at 1:12 PM, Davide <ge...@gmail.com> wrote:
> On 11/10/2012 05:38 PM, Mark Adamcin wrote:
>> I can confirm that this is happening on our CQ5.5 SP1 instances and
>> that we only discovered it this week.
>
> I don't remember the issue in SP1 but it could be. Definitely it doesn't
> appear in SP2 and SP2.1. IMHO the quickest solution is to install the
> latest SP.
>
> If you can't do it right now, you could try by overlaying the
> */libs/cq/ui/widgets/source/widgets/wcm SiteAdmin.js and
> SiteAdmin.Actions.js with a version from SP2.1.
>
> See if it solves the problem or creates a new one :)
>
> HTH
> Davide
>
>
> *
>
> --
> You received this message because you are subscribed to the Google Groups "Day Communique" group.
> To post to this group, send email to day-communique@googlegroups.com.
> To unsubscribe from this group, send email to day-communique+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/day-communique?hl=en.
>
Re: [day-communique] RE: POST operation modifying jcr:primaryType
Posted by Davide <ge...@gmail.com>.
On 11/10/2012 05:38 PM, Mark Adamcin wrote:
> I can confirm that this is happening on our CQ5.5 SP1 instances and
> that we only discovered it this week.
I don't remember the issue in SP1 but it could be. Definitely it doesn't
appear in SP2 and SP2.1. IMHO the quickest solution is to install the
latest SP.
If you can't do it right now, you could try by overlaying the
*/libs/cq/ui/widgets/source/widgets/wcm SiteAdmin.js and
SiteAdmin.Actions.js with a version from SP2.1.
See if it solves the problem or creates a new one :)
HTH
Davide
*
Re: [day-communique] RE: POST operation modifying jcr:primaryType
Posted by Mark Adamcin <ad...@gmail.com>.
I can confirm that this is happening on our CQ5.5 SP1 instances and that we
only discovered it this week.
Mark Adamcin
Acquity Group
On Sat, Nov 10, 2012 at 3:18 AM, Sarwar Bhuiyan <sa...@gmail.com>wrote:
> Hi all,
>
> Has there been any change recently to the sling post servlets to enable
> the modification of the jcr:primaryType? Or was that always modifiable?
>
> At the risk of posting something that should be posted on the CQ forum,
> I'm facing a problem where if a page properties dialog is submitted from
> the /siteadmin, it is sending
>
> ./jcr:primaryType=unstructured
>
> The jcr:primaryType should really be cq:PageContent but that's another bug
> I suppose.
>
> Now, when the POST completes, I can see that the jcr:content node's
> jcr:primaryType has indeed been modified to nt:unstructured. The issue is
> occuring on a CQ5.5 with sevice pack 1.
>
> I tried this on the GA version of CQ5.5 and the problem does not occur
> there even though ./jcr:primaryType is also posted as nt:unstructured there
> too. For those on the CQ forum, any idea why this is being posted from
> siteadmin?
>
> Apologies for the cross posting but I believe there is a problem on both
> sides
>
> Thanks.
>
> Sarwar
>
> --
> You received this message because you are subscribed to the Google Groups
> "Day Communique" group.
> To post to this group, send email to day-communique@googlegroups.com.
> To unsubscribe from this group, send email to
> day-communique+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/day-communique?hl=en.
>
Re: POST operation modifying jcr:primaryType
Posted by Justin Edelson <ju...@gmail.com>.
Sarwar-
This feature was added to Sling in https://issues.apache.org/jira/browse/SLING-1704
There is a bug in CQ 5.5 which causes the behavior you are describing. Adobe support can provide you with a workaround. I believe it was also fixed in SP2.
Regards,
Justin
On Nov 10, 2012, at 6:18 AM, Sarwar Bhuiyan <sa...@gmail.com> wrote:
> Hi all,
>
> Has there been any change recently to the sling post servlets to enable the
> modification of the jcr:primaryType? Or was that always modifiable?
>
> At the risk of posting something that should be posted on the CQ forum, I'm
> facing a problem where if a page properties dialog is submitted from the
> /siteadmin, it is sending
>
> ./jcr:primaryType=unstructured
>
> The jcr:primaryType should really be cq:PageContent but that's another bug
> I suppose.
>
> Now, when the POST completes, I can see that the jcr:content node's
> jcr:primaryType has indeed been modified to nt:unstructured. The issue is
> occuring on a CQ5.5 with sevice pack 1.
>
> I tried this on the GA version of CQ5.5 and the problem does not occur
> there even though ./jcr:primaryType is also posted as nt:unstructured there
> too. For those on the CQ forum, any idea why this is being posted from
> siteadmin?
>
> Apologies for the cross posting but I believe there is a problem on both
> sides
>
> Thanks.
>
> Sarwar