trying to login to backend bounces back

[gfxguru]

latest build as of 10/18/2012 - Trying to login with correct username and password bounces back to "The page your requested was not found,... everytime. I have "www.mydomain.com/index.php/admin/admin/dashboard/index/key/c4f8e034f76ef10384......." in the url. I tried with the new "backend" url and, same thing.

Please do not close this issue until you look at what we are saying!. You closed anothers issue with the same problem and why? #85

[northstarcomp]

I am having the same issue. index.php/backend/admin/dashboard/index/key/ee2f890684d94abef19c10720ae6e757/ or index.php/backend/dashboard/index/key/ee2f890684d94abef19c10720ae6e757/ on a test server. I have cleared cache and cookies. IT bumps me to the "Whoops, our bad..." page. ver. 2.0.0.0-dev1 and PHP Version 5.4.7 I have also check the htaccess file for the rewrite base. Any direction would be great.

[buskamuza]

Magento 2 is not compatible with PHP 5.4 yet. The known issue is one described above. It's related to bug in SimpleXML in PHP 5.4 - see https://bugs.php.net/bug.php?id=62639. Looks like PHP are not going to fix it soon.

[magento-team]

Hi @gfxguru - are you trying it on PHP 5.4 or 5.3?

[gfxguru]

We've updated to 5.4 in dev and still on 5.3 in production. I see this is an issue going forward, anyway to circumvent?

[riconeitzel]

As far as i see magento tries to parse the request 2 times… first parse process is okay, second destroys the params so that it results in 404…

[barbazul]

Guys, are you following #107 ?

There is a discussion going on about the pros and cons of moving to 5.4 which is very related to this issue (PHP 5.4 is still not supported by Magento2)

[northstarcomp]

I got it running on a fresh install of a VM Cento OS 6.3 with Zend Server CE with PHP 5.3 and Apache2. I am still unable to lunch Magento connect. It sends be back to

http://localhost/downloader/?return=http%3A%2F%2Flocalhost%2Findex.php%2Fbackend%2Fadmin%2F

Welcome to Magento's Installation Wizard!
Downloader ver. 1.5.0.0-rc2

Our Magento is version ver. 2.0.0.0-dev29

Not sure if its a Zend Server/PHP issue back end error/issue in the parse...

Any thoughts ideas or comments would be appreciated. I would like to start testing so that we (my company and the community) can have a viable and stable project at release.

Our production system is on AWS E2C and our testing is on IBM XSeries 3650 Dual Quad Core and 24Gb Ram. So I would love to put it through its paces.. Our current web store has about 250-300K items so it will give it a little work out.

[magento-team]

Hello. Where do you save sessions? If files - can you try to change session_save in local.xml from file to db and let me know if it helped?

[riconeitzel]

Doesn't help here.

Best,
Rico

Am 29.10.2012 um 10:38 schrieb mage2-team notifications@github.com:

Hello. Where do you save sessions? If files - can you try to change session_save in local.xml from file to db and let me know if it helped?

—
Reply to this email directly or view it on GitHub.

[magento-team]

Hi @gfxguru, @northstarcomp and @riconeitzel

Can you, please, provide more information for us to reproduce the bug?

1. What is your PHP version (a full one - e.g. "5.3.18").
2. What is your operating system and its version?
3. What is your Magento 2 version (GitHub commit you cloned from)?
4. Do you use APC?
5. Where are your sessions stored - filesystem, database, memcache, etc?
6. Do you have error messages in frontend or in Magento/Apache/PHP logs?
7. Can you turn developer mode on and look for any error messages at frontend?
8. Can you login as customer to you account?
9. What is your backend and frontend addresses?

A phpinfo() log would be of great help as well (i.e. you can upload it to some service and provide a link).

Thank you.

P.S. Also a note, guys: Magento 2 backend doesn't work on PHP 5.4 as for now. It is a known issue, and we will fix it soon. However, if PHP 5.4 is the cause of this ticket, then the ticket can be just closed.

[riconeitzel]

For me it's php 5.4.4 - so I'll stand by for the fix. Thanks for pointing that out!

[northstarcomp]

I am running CentOS (Pretty much Red Hat Enterprise) 6.3, PHP 5.3, Apache 2.2 and Zend Server. All Updates out of
The Base Repositories for our Linux. We are LTS not Bleeding Edge.

Our Sessions are stored in File

You can also see my prior 2 posts for more details.

Logging in 192.168.150.50/index.php/admin <---this is our development server not a live server...
I will try to grab the others logs in a day or two for you.

This is all a clean install and get these errors. I can post my configuration steps IE type this do this ect step by step as we keep a pretty good log as to what we do so we can apply it to our live site without too many variations.

[ideirj]

apache 2.2.22
php 5.4.3
http://localhost.com/magentonew/index.php/backend/admin/dashboard/index/key/..../
Whoops, our bad...

apache 2.2.22
php 5.3.13
http://localhost.com/magentonew/index.php/backend/admin/dashboard/index/key/..../
Whoops, our bad...

magento version: 2.0.0.0-dev33
windows7
don't use apc
session: filesystem
(default magento install settings)

localhost.com an alias (127.0.0.1 is also doesn't work and also dev32 version)

[hidonet]

same problem here...

[magento-team]

@hidonet - can you provide the following:

What is your PHP version (a full one - e.g. "5.3.18").
What is your operating system and its version?
What is your Magento 2 version (GitHub commit you cloned from)?
Do you use APC?
Where are your sessions stored - filesystem, database, memcache, etc?
Do you have error messages in frontend or in Magento/Apache/PHP logs?
Can you turn developer mode on and look for any error messages at frontend?
Can you login as customer to you account?
What is your backend and frontend addresses?
A phpinfo() log would be of great help as well (i.e. you can upload it to some service and provide a link).

Thank you.

P.S. Also a note, guys: Magento 2 backend doesn't work on PHP 5.4 as for now. It is a known issue, and we will fix it soon. However, if PHP 5.4 is the cause of this ticket, then the ticket can be just closed.