1

I have configured the new UI for a Java web site and everything works fine, but only if I use Firefox as browser. When using Chrome or Internet Explorer, the Update Preview feature doesn't work properly.

When I create a new page it creates the page directly (not the temporary file) and does not display the page but remains as 'Loading'.

Have you experience something like this?any clues in order to fix this issue?Thanks!

Frank van Puffelen
  • 565,676
  • 79
  • 828
  • 807
Emma Varona
  • 241
  • 1
  • 3
  • Have you already reached out to SDL Customer Support with this problem? They might know more about it and the support channel is definitely more suited for this type of troubleshooting than Stack Overflow.. – Frank van Puffelen Jul 19 '12 at 11:25
  • Frank, indeed, I have just open a ticket to Customer Support, I was just wondering if any of you have seen this before. – Emma Varona Jul 19 '12 at 11:38
  • Nope, it doesn't ring a bell. Definitely check the JavaScript console of Firefox/Firebug for errors and check the how the data flow between client and server is different with Firefox than with the working browsers. – Frank van Puffelen Jul 19 '12 at 11:43
  • Firefox is the browser that does work though. – Emma Varona Jul 19 '12 at 11:48
  • Sorry, I misunderstood. The approach to trouble shooting remains the same though. Compare the JavaScript console and data flow between a browser that works and one that doesn't. – Frank van Puffelen Jul 19 '12 at 12:15
  • 2
    It's just a hunch, but when we have things that work on FF but not on IE/Chrome, it is often related to the internet settings (e.g. proxy server). IE and Chrome both use the same settings, FF manages its own. Could this somehow be related? – Quirijn Jul 19 '12 at 12:56
  • 1
    We have been working further in this issue and found out that UI works with Chrome if the TOMCAT contains a ROOT folder...also if this folder is empty we receive a 404 error as it tries to find a se_blank.html. any of you have seen this before? any ideas how to configured this feature so the TOMCAT does not need a ROOT folder? – Emma Varona Aug 02 '12 at 12:15
  • That's good info to update your question with, Emma. I'll post an answer based on this update. – Alvin Reyes Aug 04 '12 at 06:59

1 Answers1

2

You can prevent 404 errors on your Staging site by literally creating that se_blank.html file (which can be an empty page) in the root folder.

Also see more info on session preview configuration. Specifically, there's a web.xml setting that might apply if you have a subdirectory for your site. Use /* if it's at the root, otherwise set it to the path that contains your staging Web site.

<filter-mapping>
    <filter-name>Binary Content Filter</filter-name>
    <url-pattern>/*</url-pattern> 
</filter-mapping>
Alvin Reyes
  • 2,889
  • 16
  • 38