Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba


Go to End

4 Posts   2347 Views


Community Member, 7 Posts

16 March 2015 at 12:13pm


I am getting this error within the SilverStripe admin. Specifically, when I am on page content:

1) I click the page settings tab.
2) The URL changes (but a full reload is not occurring, by design)
3) An AJAX request occurs which fails with this status message.
4) If I then reload the browser, the settings form shows.

So I think the issue is not with the settings screen, but with the delivery of the screen via Ajax when switching tabs. I note that in Chrome, a header shows as {"Content" followed by a long block of HTML. I'm guessing that the connection is closed before the chunk is delivered properly, hence it shows as a header. But I don't have any idea where things might be going wrong. I do wonder if it's a jQuery issue as SilverStripe appears to use jQuery for AJAX.

I see this issue in Chrome / IE / Firefox, but not on all our SilverStripe sites -- only on two at this stage. Running 3.1.8.

Anybody else encountered this or have any ideas?


Community Member, 7 Posts

16 March 2015 at 12:19pm

Some additional info. One of our staff checked SilverStripe 3.1.9 and 3.1.10 and had no resolution. We do find the problem goes away if in dev mode. We also find that it works fine on our test and staging environments in any mode. It appears one page type *doesn't* have the issue, so I'll follow that up.


Community Member, 5 Posts

16 March 2015 at 12:54pm

Hey Matthew

We quite often get this error and its due to our antivirus software blocking packet requests - do you have an antivirus running?


Community Member, 7 Posts

16 March 2015 at 3:17pm

Cheers Stevie, we'll follow this up!