Skip to main content
23 events
when toggle format what by license comment
Jun 2, 2015 at 21:32 comment added george did you find a solution for existing accounts?
May 15, 2015 at 7:51 comment added george These two customers registered on 9 and 10.May: goo.gl/qp5oMz
May 14, 2015 at 21:24 comment added Shaughn Can you screenshot an old account as i have tried both fixes and they seem to resolve the issue.
May 14, 2015 at 19:52 comment added george I have added the template and it seems to work for the year. It doesn't fix older account registration dates (still flipped). Too bad it is already 14th and I can't test :) Please let me know if you find a fix for existing accounts with wrong date.
May 14, 2015 at 15:37 comment added Shaughn oh damn, forgot about the old accounts as well
May 14, 2015 at 15:06 comment added george Thanks @Shaughn. Just to ask (before implementing the edit) - I actually disabled the "module fix" and still the quick fix didn't work. Is there any way to fix the old accounts? Or will the latest edit do it?
May 14, 2015 at 12:51 comment added Shaughn Ok edit is up, you should be good to make the changes and test :)
May 14, 2015 at 12:46 history edited Shaughn CC BY-SA 3.0
Added additional fixes
May 14, 2015 at 12:29 comment added Shaughn Sorry, urgent work to do. I will update the answer in a bit.
May 14, 2015 at 7:56 comment added george did you have a chance to test further?
May 11, 2015 at 23:21 comment added george BTW the quick fix doesn't seem work after the module fix is implemented. I wonder if there is a way to fix existing customers with wrong date?
May 11, 2015 at 22:44 comment added Shaughn I will need to run another test and replicate. Ill post here as soon as i have solution
May 11, 2015 at 21:04 vote accept george
May 11, 2015 at 21:04 comment added george Thanks, I will mark the answer :) But there is another strange thing now. When the customer is logged in I see "Last Logged In: May 11, 8131 4:31:37 PM (Online)". Can you fix that too so the solution is really complete?
May 11, 2015 at 21:02 comment added Shaughn Yip, that looks good
May 11, 2015 at 20:57 comment added george Thanks! It seems this works. Can you please check if this is what it should be: pastebin.com/NxpKZY0n
May 11, 2015 at 20:37 comment added Shaughn ah ok, u dont have you model defined. add to the models: <solution><class>George_Solution_Model</class></solution> then change your observer to <model>solution/observer</model>. Also make sure that observer resides in the following directory: George/Solution/Model/Observer.php
May 11, 2015 at 19:50 comment added george here it is: pastebin.com/p8wKdcGu - note: I still haven't removed the other fix from it but I guess that shouldn't matter for the error.
May 11, 2015 at 15:49 comment added Shaughn @george - nope no need for that other fix, the module fix should handle it just fine. Can you pastebin you config.xml please so i can take a look. Seems like Magento cant fine your observer.
May 11, 2015 at 14:38 comment added george Correction on the fist comment: I use <model>george_solution/observer</model> but it still doesn't work.
May 11, 2015 at 14:33 comment added george Also - if I use your module-fix do I still need to run in parallel this fix (which is partial as I explained in the question): magento.stackexchange.com/questions/18062/…
May 11, 2015 at 14:30 comment added george The quick fix works - thanks! As for the other one - I am trying to implement it inside another simple module (namespace=George, modulename=Solution). But when adding your xml code in the <global> tag and setting <model>solution/observer</model> then upon registering of new customer I get this error: pastebin.com/kbMSXtPk How to fix that?
May 10, 2015 at 21:30 history answered Shaughn CC BY-SA 3.0