Hi All,
I am able to run the Twitter Feed Scheduler, But Tweets are not updating Could you please help on this.
[sling-default-4-com.adobe.acs.commons.twitter.impl.TwitterFeedScheduler.34311] com.adobe.acs.commons.twitter.impl.TwitterFeedUpdaterImpl Twitter component found on /content/my-Project/en/configurations/twitter/commission, but page cannot be adapted to Twitter API. Check Cloud SErvice configuration.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @naveen123,
Looking into screen-shots and all information provided under this topic https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/twitter-feed-issues-in-aem...
I think there are 2 things you could do. Assuming you have your Twitter configuration done according to what has been advised by @Vijayalakshmi_S, e.g. making sure cq:cloudserviceconfigs property is in place and is pointing to correct Twitter configuration etc.
First of all (this is optional and you can jump into next paragraph) you could add additional logger set to debug - this is just to verify if my suspicions about the place where creation of Twitter object failing are correct.
com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at /conf/global/settings/cloudconfigs/twitterconnect is not readable or adaptable to com.day.cq.configuration.Configuration ( also tried looking at /conf/global/settings/cloudconfigs/twitterconnect/jcr:content/public )
Now is time for potential solution or rather workaround. Navigate in crx/de to your configuration jcr:content node. It will be probably this path /conf/global/settings/cloudconfigs/twitterconnect/jcr:content. Change sling:resourceType property value from social/connect/twitter/components/admin/hbs/twitterconfig to cq/cloudserviceconfigs/components/configpage
That's it, you can test your code once again. This should solve the problem that Twitter object was null. Of course this does not mean there will be no other issues, but at least you should be able to move forward.
If above will work for you, I would suggest to also raise above as an issue via GitHub https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues
Hi All,
Anybody Could you please help on this ASAP.
Regards
Naveen V
Hi All,
Could you please help on this ASAP. Please community Team please help on this issue.
Hi @naveen123,
Looking into screen-shots and all information provided under this topic https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/twitter-feed-issues-in-aem...
I think there are 2 things you could do. Assuming you have your Twitter configuration done according to what has been advised by @Vijayalakshmi_S, e.g. making sure cq:cloudserviceconfigs property is in place and is pointing to correct Twitter configuration etc.
First of all (this is optional and you can jump into next paragraph) you could add additional logger set to debug - this is just to verify if my suspicions about the place where creation of Twitter object failing are correct.
com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at /conf/global/settings/cloudconfigs/twitterconnect is not readable or adaptable to com.day.cq.configuration.Configuration ( also tried looking at /conf/global/settings/cloudconfigs/twitterconnect/jcr:content/public )
Now is time for potential solution or rather workaround. Navigate in crx/de to your configuration jcr:content node. It will be probably this path /conf/global/settings/cloudconfigs/twitterconnect/jcr:content. Change sling:resourceType property value from social/connect/twitter/components/admin/hbs/twitterconfig to cq/cloudserviceconfigs/components/configpage
That's it, you can test your code once again. This should solve the problem that Twitter object was null. Of course this does not mean there will be no other issues, but at least you should be able to move forward.
If above will work for you, I would suggest to also raise above as an issue via GitHub https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues
Hi Lukasz,
Thanks for replying let me do suggested changes and If any issues, I will come back.
Regards
Naveen V
Views
Replies
Total Likes
Hi Lukasz,
I have what ever you suggested that as below.
Now is time for potential solution or rather workaround. Navigate in crx/de to your configuration jcr:content node. It will be probably this path /conf/global/settings/cloudconfigs/twitterconnect/jcr:content. Change sling:resourceType property value from social/connect/twitter/components/admin/hbs/twitterconfig to cq/cloudserviceconfigs/components/configpage
But this not worked after I have try with Log Debug.But I am getting same thing Debug as 6.05.2022 07:17:00.008 *DEBUG* [sling-default-4-com.adobe.acs.commons.twitter.impl.TwitterFeedScheduler.18244] com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at /conf/global/settings/cloudconfigs/twitterconnect is not readable or adaptable to com.day.cq.configuration.Configuration ( also tried looking at /conf/global/settings/cloudconfigs/twitterconnect/jcr:content/public ). Could you please help on this.
com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Resource at /conf/global/settings/cloudconfigs/twitterconnect is not readable or adaptable to com.day.cq.configuration.Configuration ( also tried looking at /conf/global/settings/cloudconfigs/twitterconnect/jcr:content/public )
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies