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.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

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

admin not loading certain pages after upgrade to 3.1.1


Reply


4 Posts   885 Views

Avatar
nomadic

Community Member, 2 Posts

27 October 2013 at 9:51am

HI all,

I have just had to revert my upgrade to 3.1.1 to 3.0.5 due to an issue I was having with the admin area. It would allow me to log in fine and click on the security section and files, but when I went to edit the pages - I would click on one, then another - and the loading icon would show and would freeze there. The url is correct, but the content didn't load - I had to refresh the page.

There were a number of errors being presented;
1. $ is not defined
2. /security/ping was not functioning
3. The admin area would time out and ask me to log in again.

OS is OSX under WAMP
Browser is chrome
version 3.1.1

Anybody else having issues with the 3.1.1 release?

Cheers

Avatar
Jakx

Community Member, 3 Posts

7 November 2013 at 11:36am

I am having the same issue. (but I don't have a 3.0.5 to roll back to, started this site fresh on 3.1).

I can also add that CMS sections I've added by extending LeftAndMain work fine without any issue. It's only the /pages/ section that is affected.

No errors in console when trying to navigate to pages via the cms.

Any thoughts?

Avatar
Mojo5000

Community Member, 5 Posts

19 November 2013 at 9:09am

There is a javascript issue - Sizzle.error that is surfacing. I've been working with 3.1 without a problem, but then all of a sudden ran into this err. Removed everything from assets/_combinedfiles, cleared cache, etc. Anyone else run into this?

Avatar
Mojo5000

Community Member, 5 Posts

19 November 2013 at 12:29pm

Doh. Solved it.

-----

<?php

Left a line break above the <?php for one of my Page.php files. This was causing it not to load and therefore held up the entire CMS.