Tagged: cornerstone
-
AuthorPosts
-
May 5, 2016 at 10:13 am #914380
Hey guys,
I just got an issue resolved on one of my sites where Cornerstone wasn’t loading for pages already created…also new pages weren’t saving all the newly created elements…
I’m not having the exact same issue for another site!
I’m writing to let you guys know that I think it likely the embedded video element. I have used Wistia with both of the sites that have had issues…is there a potential that using Wistia in the embedded video element is causing a glitch in Cornerstone??
It’s just happened (the exact same thing) for two of my sites…and I use a LOT of Wistia embedded video.
Also, on the new site that is having issues…I can’t edit previously created pages…I CAN create new pages…and it will save all the new elements I create UNTIL I add in an embedded Wistia video…then all of the sudden it won’t save anything new.
Any fix that you guys know for this?
May 5, 2016 at 11:49 am #914549I’m having the same issue and was able to track it down to Wistia. If you remove the Wistia JS, it will load the page fine (not in skeleton mode). Also if you load the Wistia JS in the head rather than putting it directly into Cornerstone, it loads fine. Chrome is saying it’s some sort of jquery conflict that is causing the issue and says it can’t load the iframe.
Would love a resolution to this….
May 5, 2016 at 7:23 pm #977927Hi guys,
Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:
– Link to your site
– WordPress Admin username / password
– FTP credentials
– Procedure on how we can reproduce the issuesDon’t forget to select Set as private reply. This ensures your information is only visible to our staff.
Thanks!
May 6, 2016 at 7:00 am #978485I’m sorry, but I’m unable to give you a login to my client’s site. Besides, I did a workaround to add the Wistia JS into the header and it’s now loading in Cornerstone OK on that site. I did a bit of testing on my local dev site (where I also saw the problem) and found that when I removed a section from the page, it would then load. This particular page has 3 sections. The section I removed had nothing but a text element in it with plain text. The odd thing is, when I recreated the section – changing NOTHING – everything loaded in Cornerstone. This leads me to believe there was some sort of corruption when Cornerstone saved the page at some point. Why this only happens on pages with a Wistia embed, I don’t know. Perhaps it’s simply because the Wistia embed contains a javascript snippet, whereas other embeds (YouTube, etc.) do not, and Cornerstone is choking on the script tags. In general javascript has problems when you load script tags within script tags, so I’m wondering if Cornerstone broke some of its code when it saved the file at some point, then my deleting and re-adding the section forced a re-save of the data. OR it could have to do with how Cornerstone saves multiple sections because I also found that if I had a Wistia embed by itself on a page (only a single section), there was no issue in loading Cornerstone. It was only when I got to multiple sections on a page.
I know this isn’t much to go on, but it’s probably why it’s an elusive issue….
May 6, 2016 at 11:22 am #978773Hi There,
Thanks very much for your input.
Let us know if you need further help.
Joao
May 6, 2016 at 11:41 am #978793Joao, if you were responding to me, then YES, we need further help. This issue has not been solved. I simply did a workaround that is a patch for now – but isn’t a fix.
Perhaps the other person on this thread can give you access to their site so you can see the issue in action.
May 6, 2016 at 7:40 pm #979503Hello There,
Could you please post the embedded code for Wistia so that can test it in our local test server. Maybe we could give you screenshots using your embedded code and whether it will worked out in our local testing server or not.
Please let us know how it goes.
May 6, 2016 at 8:21 pm #979619Hi there … I believe I see what is causing the problem. When Cornerstone is saving the embed code, it’s adding in extra backslashes. When it does that, the page can’t find the script and tries to load up a 404 page instead of the script and this is why the page is breaking.
The embed code is this: <script charset=”ISO-8859-1″ src=”//fast.wistia.com/assets/external/E-v1.js” async></script>
However, it’s showing up as trying to load this: http://[currentdomain].com/%22////fast.wistia.com//assets//external//E-v1.js/%22
Why is Cornerstone storing this incorrectly? It looks like it’s backslashing it before storing it and trying to sanitize or something. This explains why the page displays with no problem as you build it and add in the embed code, but as soon as you SAVE it and read from what was saved (which has a bunch of backslashes in it), it’s breaking the page.
I discovered this when I was checking exactly what was being loaded on the page using the Web Developer addon for Chrome. (See attached file).
May 7, 2016 at 2:43 am #979899Hello There,
This is not a Wistia video embed code. The correct code should like this:
<script charset="ISO-8859-1" src="//fast.wistia.com/assets/external/E-v1.js" async></script> <div class="wistia_embed wistia_async_j38ihh83m5" style="height:349px;width:620px"> </div>
I’ve tested this in my local testing server and this is the result:
For proper Wistia embed code, please check it out here:
http://wistia.com/doc/embedding
http://wistia.com/doc/construct-an-embed-codeCan you please confirm that you are using the latest version of X and Cornerstone? Thanks.
May 7, 2016 at 8:45 am #980162Sorry, I meant to say that was the javascript snippet from the embed code. I was using the the full embed code, but the only thing causing the issue is the javascript snippet.
From looking at the console, the problem is a conflict with the ajaxSend trigger. See screen shots attached. I am using the latest version of X, Cornerstone and WordPress. I started noticing the issue with the latest update to Cornerstone (the one where you did something with the ajax call).
Also note that the first time you use the embed code (when you first insert it), everything works fine. It’s only after you save the page and RELOAD it, that there is a problem. And it doesn’t seem to be happening with new pages I’m creating – just ones that I try to edit that had been created with the older version of Cornerstone. I’m guessing it saved the code differently?
Also, I’m not using the embedded video element – I’m placing the embed code into a text element or a raw element so I can have more control over it.
May 7, 2016 at 8:44 pm #980573Hello There,
Thanks for writing in! Based on the screenshot, the JS error may have came from any other script present in your site. Do you have a custom JS code added? Would you mind posting it in your reply? Or maybe you could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
Please let us know how it goes.
-
AuthorPosts