Login | Forgot password | Register

X

What is OpenID?

OpenID is an Internet-wide identity system that allows you to sign in to many websites with a single account.

With OpenID, your ID becomes a URL (e.g. http://username.myopenid.com/). You can get a free OpenID for example from myopenid.com.

For more information visit the official OpenID site.

Jump to:

457 Posts in 123 Topics by 165 members

Upgrading SilverStripe

SilverStripe Forums » Upgrading SilverStripe » Admin not working after upgrade to 2.3.2beta

Ask questions about upgrading SilverStripe to the latest version.

Page: 1
Go to End
Author Topic: Admin not working after upgrade to 2.3.2beta 434 Views
  • qlex
    avatar
    Community Member
    47 posts

    Admin not working after upgrade to 2.3.2beta Link to this post

    Hi,
    i have just finished upgrading to 2.3.2 beta1. I was able to dev/build and ?flush=1 at the end. Website works ok (with exception of img but this is explained in the wiki), with exception of Admin panel.
    I simply can't log in and im stuck at whitescreen with silverstripe logo in the center and Loading... in top left corner of screen.

    My firebug console says there's 500 INternal server errors when loading following files:
    http://xxx/assets/base.js?m=1242223986
    http://xxx/assets/leftandmain.js?m=1242223990
    http://xxx/assets/cmsmain.js?m=1242223992
    and stops at loading:
    http://xxx/jsparty/tiny_mce2/plugins/fullscreen/editor_plugin_src.js?m=1242221419

    As the upgrade doc suggest i added the multilangual stuff to _config.php and this didnt help.
    Im also using: Security::setDefaultAdmin but this didnt help me log in either.

    Does anybody have any hints ?
    Qlex

  • AMcD
    avatar
    Community Member
    2 posts

    Re: Admin not working after upgrade to 2.3.2beta Link to this post

    Probably too late to help the original poster, but I'll post here for anyone else encountering the same problem.

    The problem lies with the 'php_flag engine off' directive in .htaccess within the assets folder.
    It wasn't supported on our hosting, so was returning HTTP Status 500 Internal Server Error for every file in assets.

    Solution, rename or delete the .htaccess file in assets.

    434 Views
Page: 1
Go to Top

Currently Online: Hamish, sicp

Welcome to our latest member: fearofbuttons

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.