hi Folks,
I might be missing something obvious so I thought I'd post and see.
I'm setting up the EES for a bit of testing and it works fine if you have the URL of a site being just the fqdn. But if you have say two sites, say www.example.com/siteA and www.example.com/siteB, the instructions to include the 'site_link'
[html] <script type="text/javascript" src="<MySource_PRINT id_name="global" var="site_link" full_url="true" />/__data/ees/Libs/jquery/jquery-1.4.2.min.js"></script>[/html]
…would append the URI to the host also resulting in URLs like:
[html]http://www.example.com/siteB/__data/ees/Libs/jquery/jquery-1.4.2.min.js[/html]
which doesn't seem to work.
Am I seeing this right. The short term work around would seem to be to hard code the FQDN's in but is there a better solution?
K
Omitting the "<MySource_PRINT id_name="global" var="site_link" full_url="true" />" altogether will be fine.
[quote]
Omitting the "<MySource_PRINT id_name="global" var="site_link" full_url="true" />" altogether will be fine.
[/quote]
Ah of course - thanks (some sort of comment about woods and trees probably appropriate ;_)
Hi Guys,
We have a similar situation: www.example.com/siteA and www.example.com/siteB and after reading the 'fix' here have been able to get EES running on these, however…
When loading the EES screen it takes a long time compared with loading it on www.example.com (the status bar in the browser constantly uodates with Transferring… and Waiting… messages).
Once the EES loads we can go into Edit and change the status to Safe Edit. We can view the various screens (Metadata, URL) but the Content one just locks up. It displays the 'darkened' overlay with the circle for the timer (but no animation) and you can see the div on the page but obviously can't do anything with it.
When looking at the source we get:
Squiz MySource v3.28.0 (Matrix) Simple Edit Interface
which is all fine, but if we then click through on one of these e.g. "...=header" we get:
<!--
//<![CDATA[
var SQ_DOCUMENT_LOADED = false;
function page_on_load()
none of which resolve as the path doesn't exist. It seems there is a config. file somewhere that is using the full URL to generate these, which is then introducing the original problem of appending the URI.
[quote]
When loading the EES screen it takes a long time compared with loading it on www.example.com (the status bar in the browser constantly uodates with Transferring… and Waiting… messages).
Once the EES loads we can go into Edit and change the status to Safe Edit. We can view the various screens (Metadata, URL) but the Content one just locks up. It displays the 'darkened' overlay with the circle for the timer (but no animation) and you can see the div on the page but obviously can't do anything with it.
When looking at the source we get:
Squiz MySource v3.28.0 (Matrix) Simple Edit Interface
[/quote]
Hello
You should not be seeing any framesets within the source code, have you followed step 2 of ‘Adding the Easy Edit Suite to your Design’s Parse File’ on http://manuals.matrix.squiz.net/ees/chapters/installation ?
The load time sounds odd, have you installed the 2.28.1 or 3.28.0 EES release? The latest download (http://matrix.squiz.net/download/ees) will work in 3.28.0 and has a get locks bug fix which may help if you installed the original release. The original release was getting locks on ALL children which was taking a very long time for screens to load on large systems.
[quote]
You should not be seeing any framesets within the source code, have you followed step 2 of ‘Adding the Easy Edit Suite to your Design’s Parse File’ on http://manuals.matrix.squiz.net/ees/chapters/installation ?
The load time sounds odd, have you installed the 2.28.1 or 3.28.0 EES release? The latest download (http://matrix.squiz.net/download/ees) will work in 3.28.0 and has a get locks bug fix which may help if you installed the original release. The original release was getting locks on ALL children which was taking a very long time for screens to load on large systems.
[/quote]
Maybe I should have clarified - we are viewing the source code when in EES view so I assume you would get the framesets. When viewing in normal web page mode we don’t see them. And just to confirm your question - yes we have followed step 2. The EES works fine for anything under www.example.com but as soon as we try it on www.example.com/siteA we get this problem. It seems to be the fact that the paths being generated include siteA when they shouldn’t.
We are still running the original release under 3.28.0 so I’ll see about getting this updated to the latest.
[quote]
Maybe I should have clarified - we are viewing the source code when in EES view so I assume you would get the framesets. When viewing in normal web page mode we don't see them. And just to confirm your question - yes we have followed step 2. The EES works fine for anything under www.example.com but as soon as we try it on www.example.com/siteA we get this problem. It seems to be the fact that the paths being generated include siteA when they shouldn't.
We are still running the original release under 3.28.0 so I'll see about getting this updated to the latest.
[/quote]
Hi Uo
I might not be understanding you fully here. If installed correctly there should be no 'frameset' tags present in EES code anywhere. EES requies that the new 'No Frames in Simple Edit Interface' feature available from the Design details screen is set to 'Yes', which strips the design of simple edit frames when in simple edit mode.Regarding the URL issue, try removing <MySource_PRINT id_name="global" var="site_link" full_url="true" /> from before any file paths just before /__data - see if that helps?
[quote]
I might not be understanding you fully here. If installed correctly there should be no 'frameset' tags present in EES code anywhere. EES requies that the new 'No Frames in Simple Edit Interface' feature available from the Design details screen is set to 'Yes', which strips the design of simple edit frames when in simple edit mode.Regarding the URL issue, try removing <MySource_PRINT id_name="global" var="site_link" full_url="true" /> from before any file paths just before /__data - see if that helps?
[/quote]
Thanks Scott, appreciate the help but I'm getting nowhere with this.
To recap: We have a site www.example.com that works perfectly with the EES. We have several other sites (as individual sites) with URLs of www.example.com/siteA, www.example.com/siteB etc., none of which work properly.
The conclusion is that EES is configured correctly but something is 'breaking' when it is referring to anything outside the root site (www.example.com).
Steps carried out:
- Copied the code from the working parse file to the others and removed <MySource_PRINT id_name="global" var="site_link" full_url="true" />
- I have matched all the settings in the Details screen etc.
- Applied the URL (www.example.com/siteA) to the Designs Folder and Web Services Folder. This now gives www.example.com/siteA/_design etc.
Behaviour =
The root site displays the edit screen within a few seconds, the other sites take considerably longer.
The root site displays the correct code when viewing the source code, the other sites display the frameset tag.
The root site allows editing of content, the other sites hang on the editing screen.
[quote]
The root site displays the correct code when viewing the source code, the other sites display the frameset tag.
[/quote]
This is still bringing in the matrix simple edit frameset. Each design that contains the Easy Edit design area code also needs to be configured not to show simple edit frames. It sounds like these other sites possibly have different designs, and those designs may not have this setting set to 'Yes'.
Viewing the source of a page in _edit with Easy Edit configured won't show any frames. The frames that Easy Edit uses for preview etc are written into the DOM after the page is loaded.
[quote]
This is still bringing in the matrix simple edit frameset. Each design that contains the Easy Edit design area code also needs to be configured not to show simple edit frames. It sounds like these other sites possibly have different designs, and those designs may not have this setting set to 'Yes'.[/quote]
You're right in that each of these sites have their own designs, however each one has the 'No frames in Simple Edit Interface' set to Yes, so shouldn't be showing the frameset.
I did some testing. I applied the design from the root site (www.example.com), that works perfectly, to one of the other sites (www.example.com/siteA) and it didn't work i.e. source code showed the framesets. So it's using the parse file and details settings from a site that we know works, but is breaking when trying to access a site outside the root. The only difference being the URL.
What I cannot understand is why it partially works. It wouldn't be a permissions problem, although I can't see how.
[quote]
You're right in that each of these sites have their own designs, however each one has the 'No frames in Simple Edit Interface' set to Yes, so shouldn't be showing the frameset.
I did some testing. I applied the design from the root site (www.example.com), that works perfectly, to one of the other sites (www.example.com/siteA) and it didn't work i.e. source code showed the framesets. So it's using the parse file and details settings from a site that we know works, but is breaking when trying to access a site outside the root. The only difference being the URL.
What I cannot understand is why it partially works. It wouldn't be a permissions problem, although I can't see how.
[/quote]
Hi Uo
The frameset issue continues to baffle us, sounds like you've deffinately set the correct feature to strip these out of the design.
Regarding the loading animation not appearing for www.example.com/siteA this sounds like files are not being served from the matrix __data/ees folder where required (view net tab in firebug to see what 404's for EES files you might be getting) if you have already stripped the EES exit design area code of the full site URL print tags and are just using '/__data' and that approach is working for you then make sure to remove it from the global EES variable that is in there too e.g. change var eesSiteURL = '<MySource_PRINT id_name="global" var="site_link" full_url="true" />'; to var eesSiteURL = '';
Were you able to correct the loading overlay speed by updating to the latest EES package provided on http://matrix.squiz.net/download/ees ?
[quote]
Regarding the loading animation not appearing for www.example.com/siteA this sounds like files are not being served from the matrix __data/ees folder where required (view net tab in firebug to see what 404's for EES files you might be getting) if you have already stripped the EES exit design area code of the full site URL print tags and are just using '/__data' and that approach is working for you then make sure to remove it from the global EES variable that is in there too e.g. change var eesSiteURL = '<MySource_PRINT id_name="global" var="site_link" full_url="true" />'; to var eesSiteURL = '';[/quote]
Woohoo - some progress. Removed the statement from the global variable and the animation is now displaying but editing content still hangs and eventually gives:
Warning
The request has taken a long time to process and may have generated an error on the server. Please check with your administrator.
Reload Page
Continue anyway
Running Firebug shows dozens of 404 errors:
So what's interesting is that the path for those that don't resolve are shown as:
GET edit.css = 'http://www.business-school.ed.ac.uk/aib2011/__lib/web/css/edit.css'
Those that do resolve are shown as:
GET easy-edit-suite.js = 'http://www.business-school.ed.ac.uk/_web_services/easy-edit-suite.js'
The problem seems to be that 'aib2011' is being inserted into the URL when it shouldn't be, but I can't work out why.
- Still not upgraded. We are in the process of moving buildings so the Infrastructure Manager is busy with that. However I think the slowness is due to the 404 errors and it trying to access the page over and over.
Are you able to try hard coding the url into the global variable. I believe we introduced it as a measure to account for these kinds of sub-site issues:
eesSiteURL = '';
to
eesSiteURL = 'http://www.business-school.ed.ac.uk';
The basic idea is that URL will be used as the path for the extra files needed by the wysiwyg editor and other simple edit functions that load files.
[quote]
Are you able to try hard coding the url into the global variable. I believe we introduced it as a measure to account for these kinds of sub-site issues:
The basic idea is that URL will be used as the path for the extra files needed by the wysiwyg editor and other simple edit functions that load files.
[/quote]
Hi Anthony,
I've added the URL to the global variable but no change to the behaviour. The animation still shows but the page load time and 404 errors remain. The path is still showing with the sub-site name inserted so it seems the global variable is being overridden. I've checked through everything I can think of but don't see anywhere else that this is being defined.
There may be some legacy code in the content screen that isn't using that global variable correctly due to the version you are using. I (or scott) will have a peek in some of the older code to confirm it when we get a chance.
If you are planning to upgrade soon, the latest version will have a few bug fixes and performance enhancements.
Hey
Double checked the use of site url variable, we apply it to every instance where we dynamically insert references to required editing scripts and styles that are not automatically given to use by matrix with returned data. The content screen brings a bunch of its own in based on what the js api returns for for get keyword replacement for '%__custom-contents%'.
We have had two other systems we have installed it on experience the same issues with sub folder URLs (except for content screen locking up) and these were resolved by removing all uses of print site url tag and changing eesSiteURL to an empty string, deffinately looks like your getting more 404 than I've seen to date for similar issues.
Almost impossible to sort this one out without access to troubleshoot.
I have attached a screeny of matched uses for 'eesSiteURL' throughout all of our code.
Regarding the content screen: make sure you're not experiencing the content snippets bug and make sure the quality of content is 100% e.g. is all the html for that pages content body copy 100% html valid? We had a client in Melbourne who couldnt see the preview mode iframe height because they failed to clear floats correctly on the site design and in testing I recall a content screen loading timeout due to some horrendously broken html that I pasted into it. Create a sandbox site asset with one or two pages and test against that, or is that what you have already done?
Our code (and jQuery for that matter) can only do so much until it may fall over due to poor quality of returned html data, so maybe that is something to look into?
[attachment=469:sitevar-matches.gif]
sitevar-matches.gif (8.11 KB)
Sorry, meant to link back to issues, see content snippet bug description here: http://forums.matrix.squiz.net/index.php?showtopic=7405 which will be fixed in our next release.
Thanks Anthony and Scott.
I'll have a look in more detail this afternoon at your suggestions (out all morning) and see what I can come up with. In terms of a sandbox site I'll give that a go, although the ones I've tested against so far are fairly minimal in terms of design and content.
We upgraded out development box yesterday but unfortunately the behaviour of the EES was exactly the same so it doesn't seem like the bug fixes have fixed this particular issue.
Will report back later.
Hey
Just another one to look at, but the UK team had a content screen loading/lockup issue which was corrected by turning on HTML Tidy.
Cheers
Pulling together a few strands:
Snippet bug - we applied the 'fix' for this some time ago as we ran into the problem.
HTML Tidy - this is switched on already.
Upgrade to 3.28.2 - we have done this on both our live an development boxes - no difference.
Our designer is busy setting up a sandbox site with just the basics so we can test against that. Will report the outcome.
Can you clarify please - should the eesSiteURL be 'http://www.business-school.ed.ac.uk'; or ''; Either option gives the same result so it seems to support the theory that the eesSiteURL is not being used.