MAMP issues

[smirking]

I am running a wordpress site.

I have read very good opinions for an alternative local server, called...'local'.

I was going to recommend Local if you're just running WordPress. I don't have extensive experience with it, but I have tried it and it was super easy to use and worked great in my limited experience.

There's zero reason to use MAMP if all you want is to power a single WordPress site. There's also very little reason for MAMP to put much energy into making their free product work great for people just running a WordPress site. That was useful as a gateway to MAMP PRO once, but there are many other better options for the "only want to run WordPress" crowd.

MAMP is ideal only for MAMP PRO users who need to support a diverse portfolio of sites that would otherwise require multiple virtual machines to support.

I did discover an unhappy "improvement" in MAMP 7 though. I still have some PHP 5 sites that I have to support and they dropped PHP 5 support. Luckily, I have an old 2009 MBP that I can run an old version of MAMP on to work on those.

 

[cool11]

Before deciding to go to Local, I tried once again, the new mamp 7.1.
Though I will go for it, as I can see.

Mamp 7.1. Some good news and bad news for my installation.

So, they fixed the apache problem. Now it starts normally.

But here comes a new problem.
I am not totally sure what is going on with mysql.
I mean, every new version of mamp, use to migrate everything from the older setup/installation, right?
This time it did not worked this way, as far as I can understand.
I read about mysql 8 support.
The previous database, till 6.9 mamp version, was in mysql 5.7 version compatibility.

So, the new installation, did not transferred the database.
Also, when I tried to make an import from phpmyadmin, a zipped dump/package/db export from my site, it displayed a message that there is no database to do the import. But, it is supposed that it should create it from the importing database file, right? Any ideas?

 

[smirking]

I am not totally sure what is going on with mysql.
I mean, every new version of mamp, use to migrate everything from the older setup/installation, right?
This time it did not worked this way, as far as I can understand.

You can set MySQL to run on MySQL 5.7 just like in MAMP 6. If you go into preferences > Server inside MAMP, you'll see a toggle for MySQL 5.7 or 8.0.35.

I don't think MAMP will automatically migrate everything from MySQL 5.7 to 8.0. Even in MAMP PRO that requires a manual step where you have to press a button to copy the database over to 8.0. When it copies, it doesn't destroy the old database. It creates a new version of it for MySQL 8.0.

I did have some issues with one of the databases I converted to MySQL 8 so I've still got most of my stuff on MySQL 5.7. I'm gradually going to move some of them over to 8.0.

The one database I successfully converted to MySQL 8, I exported using mysqldump and reimported from the command line.

 

[cool11]

Thanks for the clarification.

Is there any easy free way/tool, to convert mysql 5.7 database to version 8, if I need it?

 

[cool11]

----
Also I check here the features of Local

Features

localwp.com

and they mention php 7.4, as one of the supported versions and that's all!
Can I suggest they have outdated page? I use php 8 for some years now, in mamp and online.

 

[smirking]

Thanks for the clarification.

Is there any easy free way/tool, to convert mysql 5.7 database to version 8, if I need it?

I'm not familiar with the differences between the different versions of MySQL enough to be able to advise on what you need to watch out for, but you should be fine with just a DB dump out of 5.7 into a *.sql file that you then re-import into your MySQL 8 DB. I've worked between versions before and the way the engines work or the rules they follow evolve, but most of the basic syntax barely changes.

I'd expect the export and import syntax to remain really stable. I've had no problems exporting from 5.7, toggling over to the 8.0 DB server and then running an import. If you have trouble doing it through phpMyAdmin, report back and I can give you command line script to run.

 

[cool11]

I'm not familiar with the differences between the different versions of MySQL enough to be able to advise on what you need to watch out for, but you should be fine with just a DB dump out of 5.7 into a *.sql file that you then re-import into your MySQL 8 DB. I've worked between versions before and the way the engines work or the rules they follow evolve, but most of the basic syntax barely changes.

I'd expect the export and import syntax to remain really stable. I've had no problems exporting from 5.7, toggling over to the 8.0 DB server and then running an import. If you have trouble doing it through phpMyAdmin, report back and I can give you command line script to run.

So, I exported mysql 5.7 database.
Then I tried import while running mysql 8 on mamp.
Both of my tries failed.

I used phpmyadmin and after a few seconds it displayed a generic internal server error

I also tried navicat.
Here is some part of the error message
[ERR] 1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'PK

So, till now, I do not have a proper way, to transfer my wordpress mysql 5.7 database to a wordpress mysql 8 database on mamp. Any ideas?

 

[cool11]

-----
I really really would like to have, just a simple app, to do the conversion.
I remember, back in the days, when I had to make the conversion from the old ms access mdb file to sql. A simple plain small app, did the work for me in a glimpse.
I cannot understand why there is no such tool today.
Without heavy apps like navicat, without phpadmin with several limitations.
Just import and export in the format that you like.
I would like this straightforward solution.

 

[cool11]

------
Meanwhile, I discovered that new mamp 7.1, broke every link/permalink. Not only 'posts', but not even (rather static) 'pages' load anymore!!! Truly unbelievable. No matter what I tried (htaccess, wordpress settings etc), nothing worked! It is obviously a huge bug of the new mamp. They fixed the apache problem, they bring the links problem. I have no words to say.

I had to revert back to mamp 6.9 where everything still works perfectly.

But I had to keep an eye on newer versions of mamp (and others).
I just want to give a chance to mamp, as my experience taught me that there is no perfect solution.
It is very rare. So, still, I do not want to move elsewhere, only to find other kind of problems there.
But for sure, I cannot be stuck to mamp 6.9 for long.

 

[smirking]

Were you running MAMP 7.1.1? In their release notes they mentioned that they had some MySQL issues with the 7.1 release.

 

[smirking]

UPDATED: Removed an extra useless step. Added default password suggestion.

If you want to try doing this from the command line here's what you would do.

1) Go into MAMP and set the DB to MySQL 5.7 and start the servers.
2) > cd ~
3) > /Applications/MAMP/Library/bin/mysql57/bin/mysqldump -u USERNAME -p"PASSWORD" DATABASE_NAME > wordpress.sql
4) Use phpMyAdmin to create your database
5) Create the user for your database and reload all privileges.
6) > /Applications/MAMP/Library/bin/mysql80/bin/mysql -u USERNAME -p"PASSWORD" DATABASE_NAME < wordpress.sql

Everything preceded with the ">" means it's a command line execution. Replace everything in all CAPS with your own credentials.

If you don't already have user credentials, the defaults should work. You can use root as your username and root as your password.

 

[smirking]

I just want to give a chance to mamp, as my experience taught me that there is no perfect solution.

Yup. That is some truth there. As much as MAMP PRO has grated on me, I've stuck with it because for all of its frustrations, it has given me the luxury of not having to think very hard about how I have my local development server set up.

That I'm still not letting it go even after I'm now also running Dockerized solutions alongside it speaks to just how valuable it has been. I've spun up Apache servers from scratch before. I could have dropped it a long time ago, but yet I've happily paid for every version since the original one because its allowed me to not have to think very hard about how I have my development servers setup.

 

[cool11]

Were you running MAMP 7.1.1? In their release notes they mentioned that they had some MySQL issues with the 7.1 release.

Not totally sure, it was 7.1 or 7.1.1
It was very disturbing experience and I deleted it completely, waiting in general for a new future update from them.

 

[cool11]

UPDATED: Removed an extra useless step. Added default password suggestion.

If you want to try doing this from the command line here's what you would do.

1) Go into MAMP and set the DB to MySQL 5.7 and start the servers.
2) > cd ~
3) > /Applications/MAMP/Library/bin/mysql57/bin/mysqldump -u USERNAME -p"PASSWORD" DATABASE_NAME > wordpress.sql
4) Use phpMyAdmin to create your database
5) Create the user for your database and reload all privileges.
6) > /Applications/MAMP/Library/bin/mysql80/bin/mysql -u USERNAME -p"PASSWORD" DATABASE_NAME < wordpress.sql

Everything preceded with the ">" means it's a command line execution. Replace everything in all CAPS with your own credentials.

If you don't already have user credentials, the defaults should work. You can use root as your username and root as your password.

Not truly a terminal guy myself.

But I guess, something structural and generic happens here.
I mean, I can export 5.7 database with no problems.
The problem is when I try to import it to mysql 8.
I cannot understand.
I have an .sql/zipped file, with everything inside.'Create', 'Import' etc
And I execute it.
I tried it without selecting an existing database in phpmyadmin/mysql 8, and also after creating a database, just the name of it as I am not a programmer to know a lot of technical info about it.
None of the efforts gone well. Both failed.

As I said above, and with your experience,
do you think it is a bug that it will be solve in a next update of mamp?
I mean, it smells like a 'local server' problem, not a phpmyadmin problem or the sql file problem.
What do you think?

 

[cool11]

Well, there is also one thing kind of confusing with mamp updates.

They make their updates, ok?
I check here

Release notes (Mac) - MAMP & MAMP PRO

Read the latest release notes for the macOS version of MAMP & MAMP PRO

www.mamp.info

But, I am not sure, when they only mention in the updating, the mamp pro,
that the plain mamp also do not update.
Because, we all know how it usually goes.
The options and choices are there inside the core of the application,
it is just if you unlock them further with some kind of purchased key.

So, when they say
'Fixed: error when dumping databases'
I cannot tell if they just offer it to mamp pro,
and leave simple mamp with the same error!
It is possibly that they give the choice of 'in-app update function', while the others have to manually download the simple mamp.

I am not sure that they really separate the mamp/mamp pro in the core application.

 

[cool11]

Were you running MAMP 7.1.1? In their release notes they mentioned that they had some MySQL issues with the 7.1 release.

Today they released 7.2 version, both for Mamp and Mamp pro.
So I downloaded and tested it.

While it runs as it should, the local homepage of my site (wordpress),
every other link is broken! Not a single link work!
Not 'static' links/pages, no (dynamic) posts.

So, there seem to be a rather central problem.
Can someone imagine what is broken, what cause all links to broke?

---
When I revert back to 6.9, all links play normally.

 

[smirking]

I had problems with MAMP (Pro) 7.2 as well. All of my sites running on the default PHP version broke, but I was able to fix it by adding the version of PHP that I was using before. Instead of running on the default PHP 8.2.26, I reinstalled PHP 8.2.20 that I was using previously and my sites started working as expected again.

I'm not sure what that would mean for users of the free version of MAMP though.

Anyway, today's issues aside, I've found the latest release of MAMP Pro to be the most solid version they've released in many years. The issue with the MAMP Pro control panel constantly being unresponsive until you force quit the program or kill all MySQL processes from the command line has entirely been resolved. That has been a recurring issue since at least MAMP 4.

 

[cool11]

I am glad it went well for you!


It seems that I found the solution, as the problem was general with 7.x versions.
Here it is

Upgraded MAMP from 6.7 to 7.0: Just Homepage accessible, other pages 404

Hello dear Processwire users, I just upgraded my MAMP from 6.7 to 7.0. (MySQL remains 5.7). Now I can only access the homepage of each Processwire site on my local host, all other pages (including Admin) give me this message: Not Found - The requested URL was not found on this server. - Additiona...

processwire.com

 

[cool11]

In this 7.2 version, there seem to be buggy or a kind of sloppiness.

If you choose php 8.4.1, it displays a message that phpmyadmin do not work!
The included this new version of php, but without the industry standard phpmyadmin support!
So, if you want phpmyadmin, you have to choose the 8.3.14 version.

Also, why this problem with broken links? I have used mamp for decades, for the first time they break the httpd.conf file. In 7, 7.1, 7.2 version. Ok, I managed to find a solution, but what is this?

Lets see how it will go.