21304 Posts in 5736 Topics by 2603 members
| Go to End | Next > | |
| Author | Topic: | 2415 Views |
-
Login Problem

18 March 2009 at 4:46am
Hi,
since today i have a login Problem.
I can login to the cms with my name and password but than there is the silverstripe logo
and there is the text 'loading..." on the top left of the page.
But then nothing happens.Its not a problem with the client (i try it on 3 different clients on different IP's with different OS)
Any idea?
Thanks a lot
-
Re: Login Problem

18 March 2009 at 5:27am Last edited: 18 March 2009 5:28am
In addition to my first post:
in dev mode
with this line in my '_config.php':
Director::set_environment_type("dev");
it is working without any problems and i can login to the cms.
Without the line its the same problem i describe.
-
Re: Login Problem

11 May 2009 at 8:47am Last edited: 11 May 2009 8:52am
I'm having the exact same symptoms running 2.3.2 beta 1.
I did a clean install on a new database, uploaded my theme which was running fine on a local MAMP setup (OS X 10.5). Then I went in and created a couple of new pages with Spanish translations then logged out again.
All seemed OK, so I then tried to get another domain (I have multiple domains) to go directly to a Spanish home page by using the Spanish home-page url. This resulted on a 403 error as I'd forgotten that I'd reset the .htaccess to restrict things until I have the site fully online.
However I kept getting the 403 despite entering the correct password, so I reopened the .htaccess and started getting exactly the same results as jarop: The CMS load page just sits there forever.
I have noticed the browser status line reporting loding 48 of 49 objetcs, then nothing.
Removing session cookies makes no difference, but adding the line:
Director::set_environment_type("dev");
works fine. As soon as it's commented out, the symptoms reappear. Putting it back in lets me log in again.
I get the same symptoms on Safari 4 beta and Firefox 3.0.10 (OS X)
-
Re: Login Problem

11 May 2009 at 6:09pm
Hm, sounds a lot like: http://silverstripe.org/general-questions/show/260141#post260141
You guys should install Firebug (http://getfirebug.com/) and then have a look if there are some files that aren't loading properly. Maybe it's a permission problem
-
Re: Login Problem

12 May 2009 at 2:31am
Hi banal,
Thanks for the pointers.
How I missed that post you highlighted, I don't know. But miss it, I did. Must have been the tired, red, eyes from staring at the screen.
OK, so, I've run Firebug against the problem site and get the following:
The Net tab shows a successful GET admin, followed by three "500 Internal server errors" for GETs against each of the files;
base.js
leftandmain.js
cmsmain.jsThere are also nine console errors:
two: "Class ss.i18n not defined" in line 2 of en_US.js
one: "Class not found" in line 1 of tiny_mce_improvements.js
six: "Behaviour is not defined" errors against the admin URL on various linesHow I would guess that most, or all, of the console errors are likely as a result of one or more of the failed GETs?
Any more pointers would be appreciated.
In the meantime, I'm going to look into file permissions.
-
Re: Login Problem

12 May 2009 at 2:45am
More info.
While trying to edit the site with "Director::set_environment_type("dev");" set, clicking on the "Files & Images" tab reliably gives the following error:
"[Notice] Undefined index: Folder_UnusedAssetsField
GET /admin/assets/Line 157 in ... <path cut by Lokash20> ... /sapphire/core/ClassInfo.php"
-
Re: Login Problem

12 May 2009 at 3:13am Last edited: 12 May 2009 3:13am
I really wonder where this admin/assets is coming from. AFAIK there is no such folder (unless it was introduced in 2.3.2).
What are the URLs that are causing the server error (500) ? Do these files exist?If not, it might be an .htaccess error?
-
Re: Login Problem

12 May 2009 at 4:19am Last edited: 12 May 2009 4:20am
Having done a little digging, I'm now assuming that 'admin/assests' is probably error in the error message! 8-|
The physical locations for the files are as follows:
base.js - <cms ROOT>/assets/base.jms
leftandmain.js - <cms ROOT>/assets/leftandmain.js
cmsmain.js - <cms ROOT>/assets/cmsmain.jsand they all seem to have been correctly referenced in amongst the details shown in Firebug.
What's more, they all appear to have the same access permissions as my dev site which is working fine.
| 2415 Views | ||
| Go to Top | Next > |



