Can't edit file assets through VPN
I'm working remotely today and noticed a quirk when editing our
CSS style sheet in Cascade 7.8, via our Cisco SSL VPN Service. When
I click on the View tab, the page hangs while saying Loading
content preview...
(screen
shot). And when I edit the asset and click the Submit button,
all the buttons get grayed out and the page hangs.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by goodwinj on 03 Jan, 2014 05:49 PM
The same thing is happening to me (I have the same VPN access as espanae). I also want to add this: It seems as though the actual pages are editable and not hanging, as well as text and XML blocks .... it's the individual files such as CSS files that are not loading and I am not able to edit and publish them.
2 Posted by Ryan Griffith on 03 Jan, 2014 06:58 PM
Hi,
It sounds as though your VPN may be causing the AJAX request that loads the file's contents to fail. Perhaps a similar issue with regards to editing the asset may be occurring.
When this behavior occurs, do you see any JavaScript errors in the browser's console? If so, please include them with this discussion.
Please let me know if you have any questions.
Thanks!
3 Posted by goodwinj on 03 Jan, 2014 07:56 PM
I checked the page in Firefox with firebug turned on and didn't see any errors in the console...
4 Posted by espanae on 03 Jan, 2014 08:12 PM
When I click on the Warning icon, in the bottom-right corner of Chrome dev tools, I get this message:
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery-1.7.2-hh-custom.min.js?v=7_8-11192013:16
How do I display the other seven warnings?
Screen shot
5 Posted by Ryan Griffith on 03 Jan, 2014 08:35 PM
Thank you for checking, this looks normal and the additional items are most likely CSS warnings which are hidden by default in Chrome's console.
I would like to also check what the request looks like under the Network tab. When you have a moment, please:
file.act
I've attached a screenshot from my local instance for reference.
Please let me know if you have any questions.
Thanks!
6 Posted by espanae on 03 Jan, 2014 08:55 PM
Sure thing, Ryan. Let me know if these screen shots suffice:
Headers: http://d.pr/i/KRo1
Response: http://d.pr/i/8BWi
7 Posted by Ryan Griffith on 03 Jan, 2014 09:06 PM
Perfect, thank you for providing the screenshots. Can you also provide a screenshot of the rest of the Headers tab as well? Just want to check the Response Headers section.
Thanks!
8 Posted by espanae on 03 Jan, 2014 09:16 PM
Sure, here's that screenshot: http://d.pr/i/8dXW
9 Posted by Ryan Griffith on 03 Jan, 2014 09:46 PM
Perfect, thanks.
It definitely looks as though the AJAX request is successful and the content is being returned (indicated by the Response tab). So the question now is why would the VPN be causing the success callback for the AJAX request to not be executed.
What VPN are you using? I am seeing some results on Google relating to AJAX issues with Cisco AnyConnect client.
10 Posted by Ryan Griffith on 14 Jan, 2014 01:26 PM
Hi,
Just wanted to follow up to see if you had a chance to view my recent comment.
Please let us know if you have any questions.
Thanks.
11 Posted by espanae on 14 Jan, 2014 02:50 PM
We are using Cisco AnyConnect and it's the browser-based client that's associated with the AJAX issues. That is, when I log into Cascade from their browser-based VPN platform.
However, I recently discovered the option to download and install their Java client and Cascade works just fine when I log in to our VPN that way.
I think we can close this issue now. Thanks for your help.
Support Staff 12 Posted by Tim on 14 Jan, 2014 07:02 PM
Thanks for the update! Glad to hear things are working as expected with the installed client. Have a good one!
Tim closed this discussion on 14 Jan, 2014 07:02 PM.