Closed gdhnz closed 10 years ago
Hi which Magento version do you use?
v1.8.1.0.
The extension works fine on another install using the same version of Magento so I’m stumped.
Regards, Geoffrey
I didn't had the time to test on 1.8.1 that's the reason I didn't put on Magento connect support of 1.8 I would recommend to check if you do not have a conflict with an other module which overwrites the same classes.
If I disable/remove the extension saving a customer works as expected. Enabling the extension and the problems begin.
I have the same extensions installed on the development server and they all work as expected. It’s only when I enable the username extension on the test environment I’m building that I can’t update a customer or login as a customer. I’ve even tried uninstalling all 3rd party extensions to no avail.
Regards, Geoffrey
If I put some debugging code in various functions like _beforeSave and authenticate. Neither are showing the debugging output. It’s like it’s not running them at all.
Regards, Geoffrey
There is a Word wide MageHackDay this week end. I'll take a look if I have the time but try to give me more details, check if it's not at the level of the class Diglin_Username_Model_Entity_Customer or maybe an eav attribute is missing in your test environment
For your info all your private data are sent into Github. For me it's ok but maybe you don't want to publish all info. It comes because you reply per email
Is there any easy day to check if there's an eav_attribute missing?
_getDefaultAttributes in Diglin_Username_Model_Entity_Customer is being called when you edit a user but _beforeSave in the same class isn't when you save.
From: Sylvain Rayé [notifications@github.com] Sent: Thursday, 30 January 2014 12:43 p.m. To: diglin/Diglin_Username Cc: Geoffrey Hughes Subject: Re: [Diglin_Username] Saving user redirects back to admin dashboard (#10)
There is a Word wide MageHackDay this week end. I'll take a look if I have the time but try to give me more details, check if it's not at the level of the class Diglin_Username_Model_Entity_Customer or maybe an eav attribute is missing in your test environment
For your info all your private data are sent into Github. For me it's ok but maybe you don't want to publish all info. It comes because you reply per email
— Reply to this email directly or view it on GitHubhttps://github.com/diglin/Diglin_Username/issues/10#issuecomment-33645278.
It's something with the database from the looks of it. When I copy the database from my testing environment to my development environment, the problem now happens on the development setup.
Update I forgot to update the urls in the database so I was being redirected to the problem system. With the hostnames updated to my development environment I can update customers correctly. So the issue actually seems to be a file based one somehow despite the Diglin_Username files being the same between the 2 environments.
Did you enabled the log of Magento and could you take a look if you have any errors or messages in it? Check also your php error log
Nothing in the php log. I’ll check the magento log tomorrow.
I’ve copied the database and files down to my local install and it all works as expected. I’m wondering if there’s some apache config differences causing problems.
On 30/01/2014, at 8:38 pm, Sylvain Rayé notifications@github.com<mailto:notifications@github.com> wrote:
Did you enabled the log of Magento and could you take a look if you have any errors or messages in it? Check also your php error log
— Reply to this email directly or view it on GitHubhttps://github.com/diglin/Diglin_Username/issues/10#issuecomment-33666058.
Nothing is listed in the Magento logs.
Matching the apache config to the working setup on my local machine also hasn’t fixed anything.
Regards, Geoffrey
GEOFFREY HUGHES | Web Developer / Application Programmer University of Otago, Marketing and Communications Division, 31 Montgomery Ave, Dunedin, 9016
T 64 3 479 5705 F 64 3 470 3430 E geoffrey.hughes@otago.ac.nzmailto:webservices.support@otago.ac.nz W www.otago.ac.nz/webserviceshttp://www.otago.ac.nz/webservices
Service Desk webservices.support@otago.ac.nzmailto:webservices.support@otago.ac.nz
From: Sylvain Rayé notifications@github.com<mailto:notifications@github.com> Reply-To: diglin/Diglin_Username reply@reply.github.com<mailto:reply@reply.github.com> Date: Thursday, 30 January 2014 8:38 pm To: diglin/Diglin_Username Diglin_Username@noreply.github.com<mailto:Diglin_Username@noreply.github.com> Cc: Geoffrey Hughes geoffrey.hughes@otago.ac.nz<mailto:geoffrey.hughes@otago.ac.nz> Subject: Re: [Diglin_Username] Saving user redirects back to admin dashboard (#10)
Did you enabled the log of Magento and could you take a look if you have any errors or messages in it? Check also your php error log
— Reply to this email directly or view it on GitHubhttps://github.com/diglin/Diglin_Username/issues/10#issuecomment-33666058.
Hi,
All sorted. Completely uninstalled the extension and removed the database entries before re-installing it. Finally got an error in the log about missing mbstring. Got that installed and the extension now works as expected.
Sorry for all this.
When the Diglin_Username extension is installed, when I edit a user and save, the form doesn't save the changes and just redirects back to the dashboard.
I also can't login to the store as the user using either the username or email address.