I'm developing my Wordpress site locally on OSX 10.8 using MAMP Pro v2.2.1. Everything works normally EXCEPT for when I'm logged in as an admin user and I go to Settings > All Users and then try to search for a specific user (using the search bar at the top). Whenever I do this, the form seems to submit, the little spinner on the browser starts turning... and then nothing happens. No errors in the console. No 500 page. Just spinning wheel forever. And after that I can't open any of the other menus unless I stop/start MAMP. I have a lot of experience debugging wordpress plugins and themes, but I have no idea how to debug admin stuff since it's provided by the core.
What I've tried so far:
All other menu pages respond normally (unless I cause this crash).
All other admin menus respond normally, including search functionality.
The live site works fine on the server, including user search
My colleague does not have this problem when checking out the same code and testing on his PC with XAMP.
I ran CHECK TABLE wp_users and MySQL returned "Ok"
I checked MAMP's php_error.log, mysql_error_log.err
Another detail is that after I trigger the problem (by searching users), I can close the window, browse to other websites, and when I return to my local site it's STILL broken. The only way to resolve it is to restart MAMP
I would love any suggestions for how to debug this problem because I'm in the middle of a project that involves user registration and the inability to search users is really inconvenient.
Have you set up a local database to use, or is your MAMP copy of the site connecting to the live database? Remote database connections are often slow and may time out if you're opening and closing connections quite often (or not closing them all).
I was able to solve this by deleting a bunch of users from the wp_users table. I suspected that I was only having this problem in the users table because that was by far the largest table (it had recently been dumped from the production site with around 9000 users). I guess MAMP's MySQL was crashing because it couldn't handle the search query on such a large table. As soon as I removed most of the rows the search started working normally again. I'm sure there's another solution for someone more familiar with MySQL configuration in MAMP.
Related
Been trying to figure out an issue not being able to use php's dns_get_record when called in a webpage under IIS. Thru some trial an error i figured out it was a permission issue. I think I confirmed this when i temporarily added the app pool user the webpage was running under as part of the admin user group. Suddenly it started working. And surprisingly, it kept working even after i removed the app pool user from the admin group. I have 2 versions of php installed on the server. It was not working on either version. And now it works on both versions.
My guess at this point is that it wants to write to some temp/cache file and as a user it has permission to write to the file, but does not have permission to create the file. When i added it to the admin group it was able to create the file. This is purely a guess on my part.
Since i don't know the exact cause, i can't be sure it's really fixed. So would really appreciate if anyone might have a better idea of what's going on and how i can make sure it's fixed permanently.
Update1: some additional info - after removing admin rights on the app pool user, i can restart the app pool or even restart IIS through the IIS control panel and it keeps working. But, if i restart IIS using iisreset, it stops working until I give admin rights again and then run it once. I'm not sure what's different between restarting IIS in the IIS control panel, or using IISRESET, but something causes it to stop working again using iisreset.
Thanks
I am currently running 2 websites that share the same source code, changing only the DB and some minor aspects.
I recently launched my 2nd website and although everything appears to be running just fine I realized that I can't add new entries in the DB. It just gives me the message that the entry already exists, which is not true since there is only a few entries and I am obviously testing using unique entries. Another thing that I noticed is that the data that exists in the DB (I used an internal server to test things out) can be edited, which I assume that UPDATE statement is working but not INSERT INTO and DELETE. It appears that there is some problem with the connection/permission to add/delete new entries, while updating is fine.
All this is very strange as the code (PHP and JS) is exactly the same between websites and the only thing that changes is the VM I used for each of them, which makes me believe that the issue is somehow in the configuration of the webserver. I have replicated all the configurations from the other website, so I am not sure if I am missing something. Here's a list of all the configuration I have implemented:
edited 000-default.conf (of Apache to set the new document root)
changed the ownership of my app to www-data
created a user group with myself in it and changed the group of all subdirectories/files to this group
opened up the port 3306 for mysql
I honestly can't understand what is wrong, I am clearly missing some configuration setting but I have no clue what it might be. One thing that is different is the MySQL version between websites. The website that works is running this version:
5.7.26 MySQL Community Server (GPL)
While my new website is running this:
5.7.19-0ubuntu0.16.04.1 (Ubuntu)
Could this be an issue?
Any help would be appreciated.
Thank you.
I've made an Heroku app with latest Drupal 8.
After it, I've deployed it and configured the installation successfully.
Now I'm getting the problem where Drupal automatically redirects to the installation page when I open my application after 1-2 hours.
I feel that there's something to do with dynos.
And yes, I have a free account.
I've already tried searching a lot on google, but all the guides are outdated which are very complicated/do not make any sense.
The installation page of the Drupal should not come again and again. instead of it, the installation should be permanent.
If drupal is showing you install page that means that it didn't find the (old) database.
So either your database account data is not correct for new environment so it can't connect to database server ( sites/default/settings.php ) or something is wrong with your database (wiped out by heroku?). Check on database (with PHP MyAdmin or some similar tool maybe) to see do you have tables and data inside them.
Heroku has an ephemeral filesystem and Drupal creates/modifies some files during installation such as: "settings.php".
ephemeral file system means that all the modifications to the files/file system will be lost upon the dynos restarting.
So, as soon as Dynos do restart, the files are revert back to their original state.
Due to this, all the changes are wiped up and thus when you open the site/application, the drupal can't detect the installation and thats why it redirects to the installation page.
It all happens because the file changes do not persist if the file system is an ephemeral one.
as #ceejayoz suggested, please see this article for a possible work around by which you can fix this problem:
https://www.fomfus.com/articles/how-to-create-a-drupal-8-project-for-heroku-part-1
I'm new here so sorry if this is posted in the wrong place >.<
I recently started using CraftCMS and decided to make a site with it. After looking at multiple forums about development I decided to use Laravel/Homestead to develop the site locally. It's working great! Everything is working fine, all the data is being saved and it works every time I boot up homestead.
The one question I have is how to move all this data from my local database to a live site. I have Bluehost and I know it's capable of mySQL and hosting a CraftCMS site. I just need to know how to transfer all the data.
I've been using Sequel Pro to monitor everything locally. So I feel like it's possible. Not really experienced with databases in this way. Just need a nudge in the right direction. Thanks!
Can you access to your Bluehost DB in Sequel Pro? If you can, I think you should first go to your local homestead DB and click [File]->[Export]. And go to Bluehost DB and click [File]->[Import]. Remember to choose the same format as you exported.
It's definitely possible.
If you can export your craft db with sequel pro (or the command line)
Assuming your local database env is root with
mysqldump -u root -p password mycraftdb > dump.sql
You'll need to import this sql file in phpmyadmin on bluehost
Here's a help doc. https://my.bluehost.com/hosting/help/256
Start a new database unless you're using the old tables in your new local craft site. Definitely back up your old one.
Whenever you work with a host like Bluehost, godaddy, etc. You're going to have an obnoxious time trying to get everything configured to pass the system report for craftcms. Sometimes you'll even have to reach out to the host to do something simple like upping a memory_limit.
Here's an article my friend wrote about his experiences using craftcms with these hosting environments. It could be helpful.
https://medium.com/#importantcoding/craftcms-how-i-hate-to-love-you-e0d26722a1d2
I recently updated to MAMP 3 and as a result see to have lost all of my database files. When I start the servers, and load up my developed websites it begins a wordpress install from fresh. I can see the db files in the directory but they don't seem to load in phpmyadmin. Does anyone know if it is possible to recover the database file and website to previous functionality or what I can do to restore the site back to normal.
Any help would be much appreciated.
Thanks.
if you host is not making backup, there's no way to get the DELETED data back.
however login to cpanel and click on backup, click on generate & download a backup, check if it has a option "system generated backup" and has a button called weekly.
if there's a weekly button, that should give you the backup when the main server owner Ran the backups.
http://forums.cpanel.net/f49/my-database-removed-accidentally-how-recover-155173.html