Cloud Service (Site Verification) value not displaying through dispatcher | Community
Skip to main content
S
stephenm5797042
October 4, 2018
Solved

Cloud Service (Site Verification) value not displaying through dispatcher

  • October 4, 2018
  • 4 replies
  • 997 views

Hi,

We have set up Site Verification through the Cloud Service Configuration. We can add the service to our pages and we successfully see the output in the page source in both author and publisher. However when we view the page through a dispatcher the value is not included in the page source. Has anyone else had this issue?

Presumably it's a permissions issue with the anonymous user when going through the dispatcher, but how can this be resolved with such Cloud Service Configurations?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Peter_Puzanovs

Dear Stephen,

Good, -1 thing to look for.

Does meta tag displays on publish when you are not logged in to the instance?

Could be the issue with permissions:

Permissions on Publish for anonymous

Regards,

Peter

4 replies

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity Advisor
Community Advisor
October 5, 2018

Dear Stephen,

Have you tried to clear Dispatcher cache?

Regards,

Peter

S
stephenm5797042Author
October 8, 2018

Hey Peter,

Yes have deleted all cache on the dispatcher. The <meta> tag displays fine in the page in author and publisher, just not when viewing through dispatcher. The developer who worked on this has extended from WcmUsePojo where they get the ResourceResolver from the request and adaptTo ConfigurationManager. Usually we would use a service user to get the resource resolver, but not sure if this is the issue.

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity AdvisorAccepted solution
Community Advisor
October 8, 2018

Dear Stephen,

Good, -1 thing to look for.

Does meta tag displays on publish when you are not logged in to the instance?

Could be the issue with permissions:

Permissions on Publish for anonymous

Regards,

Peter

S
stephenm5797042Author
October 8, 2018

You were indeed correct, it was due to the permissions for the anonymous user. Thank you!

Terms & ConditionsAccessibility statement

Loading footer...