Welcome Guest. Please Login or Register  


You are here: Index > AMPPS > General Support > Topic : upgraded to AMPPS 2.3, Wordpress user/pw quit working



Threaded Mode | Print  

 upgraded to AMPPS 2.3, Wordpress user/pw quit working (7 Replies, Read 2529 times)
flamenco
Group: Member
Post Group: Newbie
Posts: 7
Status:
Hi,
I'm on Win7. Ampps told me I should upgrade to 2.3. I downloaded and that ran OK.

I tried running Wordpress and got "error establishing a database connection". I checked some other scripts, they ran OK.

I had installed Wordpress via Softaculous, which generates a db table, user, and password. As far as I can tell, the upgrade somehow messed up that user, even though in the Softaculous Wordpress section all that stuff is still there. I even tried re-saving that data in case that would do anything, it didn't.

I got around this by using my root user in my Wordpress config, so I'm up and running, but obviously this is kind of a bogus solution.

Any insights about that? Anybody else notice that Softaculous users get stomped by upgrading to AMPPS 2.3?

Any help appreciated!
Thanks.
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Can you check for the db users from phpMyAdmin, do they exist ?


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
flamenco
Group: Member
Post Group: Newbie
Posts: 7
Status:
Quote From : tidus February 28, 2014, 6:58 am
Hi,

Can you check for the db users from phpMyAdmin, do they exist ?

Hi Tidus,
Good call - no, apparently my user was gone. I'm not used to creating users via phpMyAdmin - my CPanel bias, I guess. :-) Anyway, I re-created my user and managed to assign them to the DB, and now that user works again.

So I guess deleting users is a bug with the AMPPS installer then, right?

I will say this - I've loved using AMPPS, and this is the first time I've ever had any difficulty with it - thanks for excellent software.

Dave
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
flamenco
Group: Member
Post Group: Newbie
Posts: 7
Status:
Hi,
Wow, more to report.

I was unable to get MySQL to start. After reading the error msgs, I read somewhere that you can add a "force recovery" parm for InnoDB to the MySQL boot-up code. It worked, and that did allow me to run Wordpress and use PHPAdmin with my databases. Then I removed the recovery parm.

Now today, I got the same slew of InnoDB error messages, and MySQL would not start. This time, a google search yielded this posttid=5041&title=1146_MySQL_errorthis post[/url] in this forum. It had a different directory structure than mine,  but I was able to do the same general idea, and again MySQL began to load. 

I hope it keeps working. I must admit that I'm really sorry I updated Ampps to 2.3. I never had any problems before doing that. Now I've had many. I will think long and hard before accepting the next update.

Dave
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

We just checked our upgrade package. Our package does not provide the data directory of mysql so the database and its user should not get affected. We will still try to regenerate this issue and solve the issue if any.

Sorry for the inconvenience.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
flamenco
Group: Member
Post Group: Newbie
Posts: 7
Status:
Tidus,
Thanks for looking into it, I appreciate it. I think I have things sorted now.

I've had a crash course in server admin, and have been carefully reading the scripts that launch MySQL and so on. I see lines in the MySQL script that are commented out that deal with InnoDB. My databases do have some fields that are InnoDB, and they seem to work, so I will leave those commented out for now.

I'm not certain, but some of the problems seem to have been caused at times when I forgot to shut down AMPPS before shutting down my computer, and apparently the previous version of AMPPS was more forgiving of that.

I'll be much more careful when doing future upgrades. I eventually found documentation on upgrading that listed lots of things to back up. I clearly should have done that, but the docs for AMPPS are located all over, so I didn't find the upgrade one before doing the upgrade. If I have time, I might do a fresh separate install of AMPPS, and then do some file compares. I'll check the documentation to see if that's feasible.  :-)

Thanks, Dave
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Quote
I see lines in the MySQL script that are commented out that deal with InnoDB


MySQL Script ? BTW Ampps executes mysql without any scripts.

Quote
I'm not certain, but some of the problems seem to have been caused at times when I forgot to shut down AMPPS before shutting down my computer, and apparently the previous version of AMPPS was more forgiving of that.


Okay. We will check. And look for workaround.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgraded to AMPPS 2.3, Wordpress user/pw quit working
flamenco
Group: Member
Post Group: Newbie
Posts: 7
Status:
[quote poster=tidus date=1394001911]Hi,

[quote]I see lines in the MySQL script that are commented out that deal with InnoDB[/quote]

MySQL Script ? BTW Ampps executes mysql without any scripts.

[quote]
Tidus,
Sounds good.

And I'm probably using wrong terminology - I was referring to this: in the AMPPS Control Center, you choose MySQL and click "configuration". The "my.ini" that appears there is what I was referring to. When things were not working well, I examined that.

Cheers, Dave
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is April 27, 2024, 10:14 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.026