Subject line is a bit of a mouthful I know :-) I've noticed a bit of an odd effects going on with the Preview and Library Search features of one of our Content Types - Staff
With the Preview what I'm seeing is the page renders then in the footer a sudden flash of extra content appears before the whole page is wiped out and goes blank. With the Library Search, which is coming from a Related Content picker, I'm seeing something similar. You put in your search, you get the loading prompt and then the screen flashing with this content and everything goes blank. --- So a bit of investigation work has turned up some interesting findings :-) What seems to be happening is the Webtop is making an AJAX call to pull in extra content. I'm assuming with the preview it's to load in the Webtop Toolbar in the footer? The call itself is going to something like this:- http://localhost/Staff/FE93D940-15E2-11E1-A334005056837ACE/trayContainer/ajaxmode/1/totalTickCount/110 Likewise with the Library Search it's doing a call on this kind of address - http://localhost/staff/FE93D940-15E2-11E1-A334005056837ACE/displayLibrary/property/teaserImage/ajaxmode/true/filterTypename/dmImage Note the Staff part of the addresses. The problem seems to be that we're using Staff as a FURL. One of the main navigation points on the Site Tree uses it so what I'm guessing is happening is the AJAX call is being intercepted by Core's FURL features, it's being thrown into the Staff webskin and the HTML I'm seeing a flash of is actually the rendering that's happened from http://localhost/staff. Just to confirm that's the case I removed the FURL from the Site Tree. Ran the preview and search again and they've started working. ---- On a side note since we've gone live with 6.1.1 I've started recieving new error reports from the site. It looks like Content Types now get their own FURLs by default. So the Content Type of "News" is automatically getting - http://www.domain.com/news ---- So my question was really - what's the best approach to getting around this do you think? I'm currently thinking I should rename the content type and then check to make sure others aren't showing the same symptoms. Or is this something that should be looked at as a fix in Core? Cheers, James -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
