Shooting in the dark | Different DOM markup b/w author and publish | Community
Skip to main content
A
AshishSPanwar-a
Level 2
October 16, 2015
Solved

Shooting in the dark | Different DOM markup b/w author and publish

  • October 16, 2015
  • 6 replies
  • 1673 views

Hi All,

We are trying to address a weird problem. Suggestions are welcome. We have a custom component (Social Share) that does not show up correctly in Production Publish instance only. In all other environments DEV, QA the component works as expected across both author and publish instances.
Production instance is managed by another team and we have very limited access to it. So currently it seems like shooting arrows in the dark.
On author the DOM markup produced by the component is as follows:-

<a href="http://www.facebook.com/share.php?u=http%3A//www.xyz.com/path/to/current/page.html" target="_self" title=""><img src="/etc/designs/xyz/images/facebook.gif"></a>

Instead what we are getting in publish is as follows:-
<a href="https://forums.adobe.com/path/to/current/page.html" target="_self" title=""><img src="/etc/designs/xyz/images/facebook.gif"></a>

  • Codebase is same across all instances
  • We remotely suspected link checker service might have something to do with it but disabling that also did not help.

We are not sure what the issue might be. The component is working but generated html output is different between author and publish and that too only on PROD. Could anybody point to any service that might interfere with output html?

AEM version in use "6.0 SP2".

- Ashish

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 smacdonald2008

This looks like it may be some sort of customization that accounts for this. OOTB - this does not make sense. That is - if it works on other AEM instances - it will work on PUB instance - assuming no custom changes were made. 

6 replies

L
leeasling
Level 8
October 16, 2015

Have there been any customizations to the XSS protection configuration that maybe didn't make it to the production server?

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

This looks like it may be some sort of customization that accounts for this. OOTB - this does not make sense. That is - if it works on other AEM instances - it will work on PUB instance - assuming no custom changes were made. 

A
AshishSPanwar-aAuthor
Level 2
October 16, 2015

Thanks for the reply,

I checked all runmodes in codebase and it seems there is no customisation made for any XSS protection configuration. 
Additionally looking into Felix configuration manager I could not find any service config for XSS service.

- Ashish

A
AshishSPanwar-aAuthor
Level 2
October 16, 2015

I also suspect the same but cannot pinpoint the cause unfortunately. The last bit is confusing where it works on DEV publishers but generates different mark up on PROD publishers. Clearly some other service is coming in the way of this component's output.

- Ashish

edubey
edubey
Level 10
October 16, 2015

Just wondering, can it be because of rewrite rules you have setup.

A
AshishSPanwar-aAuthor
Level 2
October 16, 2015

@edubey: Which rewrite rules do you mean?

I have already checked any applied resource resolver rules and there are none being applied.

Only other rewrite rules would be in web server layer which again seems unlikely. I do not believe Apache has been configured to modify the DOM.

- Ashish

Terms & ConditionsAccessibility statement

Loading footer...