This creates the user and takes you to the "Edit Privileges" for this new user on the new database. Leave the default settings for the remaining sections.Leaving it as "Any host" will not allow Drupal to connect to your local database and you'll get an error. Fill out the "Login Information" form, making sure to change the "Host" field to "Local".Under the "New" section, click on "Add user account".Look on the left-hand column under the phpMyAdmin logo and make sure that your new database is selected.Select "utf8_general_ci" from the "Collation" drop-down (must be utf8!).Under the "Create database" section, enter a name for your Drupal database in the "Database name" field.On the phpMyAdmin page, click the "Databases" tab.Under "Tools", click the link to "phpMyAdmin".It is generally best to download and unzip Drupal directly in the document root (default is htdocs) so you don't miss the. htaccess file which is necessary for clean URLs to work. Note: if you use Finder you may miss moving the. Where yourdrupaldir is whatever you want the directory to be called. ![]() Mv drupal-x.x.x/* drupal-x.x.x/.htaccess /Applications/MAMP/htdocs/yourdrupaldir Move the directory containing the Drupal files into the MAMP htdocs directory: Open MAMP and click "start servers," then "Open start page." Download Drupal (This will install Apache, MySQL, and PHP in one step.)ĭownload and proceed through the installer to install MAMP. This page is to be used in conjunction with the installation instructions for Drupal on Mac OS X.Īlso you may want to check out this video in the Videocasts section of the handbook: Installing a Local Web Server on Mac OS X. This will make Drupal much easier to install because the components don't have to be installed separately. I am assuming I can re-connect it to the existing MySQL database so I don’t lose that work.MAMP creates a local server environment on Mac OS X by installing PHP, MySQL, and Apache right out of the box. I also went back to my browser history to re-enter the url I was using to go directly to the site I have been developing, and that doesn’t work either ( I have no problem with just reinstalling the EE2 software from scratch if that is the simplest approach. Moreover, I know I am using the same url in the browser to get to the control panel, since I use the application 1password to login which generates the same string as I used since the start of this project. No, I don’t believe I changed anything regarding my EE installation (although I wouldn’t be the first person who made such a claim). So, you asked was the site ever working: yes, as I said in the original note, for several days. Here’s my issue: what had been working for several days-starting up the servers using MAMP, logging into the EE2 Control Panel or going directly to pages I was creating via EE2-simply stopped working. And email is tricky business about tone, but I’m not sure what you mean about just having issues. But be careful: do notġ10522 14:52:26 InnoDB: remove old data files which contain your precious data!ġ10522 14:52:26 Plugin ‘InnoDB’ init function returned error.ġ10522 14:52:26 Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.ġ10522 14:52:26 Unknown/unsupported storage engine: InnoDB InnoDB only wrote those files full ofġ10522 14:52:26 InnoDB: zeros, but did not yet use them in any way. InnoDB: Some operating system error numbers are described atġ10522 14:52:26 InnoDB: Could not open or create data files.ġ10522 14:52:26 InnoDB: If you tried to add new data files, and it failed here,ġ10522 14:52:26 InnoDB: you should now edit innodb_data_file_path in my.cnf backġ10522 14:52:26 InnoDB: to what it was, and remove the new ibdata files InnoDB createdġ10522 14:52:26 InnoDB: in this failed attempt. InnoDB: Error number 35 means ‘Resource temporarily unavailable’. (see below)Īnybody have this experience and find a way out?ġ10522 14:52:26 InnoDB: Unable to open the first data fileġ10522 14:52:26 InnoDB: Operating system error number 35 in a file operation. I looked at the MAMP mysql error log, but got no great insight. The Apache Server status light is green, but the MySQL Server status stays red. ![]() Today, I used them again, logged out, and then later attempted to restart MAMP. I recently installed MAMP and EE2 on my Mac (OS X 10.6) and have been using them for the last several days.
0 Comments
Leave a Reply. |