Correcting error: “You don’t have permission to access /phpmyadmin on this server.”

After installing Acquia Dev Desktop, lynda.com student Kelly Thebo click its “Manage my database” button and got the following error:

You don't have permission to access /phpmyadmin on this server.

She adapted a solution on Corpocrat.com:

  1. In Acquia Dev Desktop, click Settings > Config > edit(next to Apache [httpd.conf file])
  2. Go to the bottom of the file and find:
    Options Indexes FollowSymLinks ExecCGI
    AllowOverride All
    #Order allow,deny
    Allow from localhost 127.0.0.1
  3. Comment out the “Order allow,deny” line.

Thanks, Kelly!

Error in “Drupal Essential Training” regarding settings.php file

Lynda.com subscriber Sarah Faraud uncovered an error at the 2:12 mark of the “Downloading and installing Drupal on a Mac” video in Drupal Essential Training. I stated:

Now the file itself was called settings.php and it’s created by duplicating this default.settings.php. You can also just delete the word default and the period, but I prefer to leave a backup.

It turns out that deleting the original default.settings.php file causes problems, so just leave it there! My apologies to anyone who’s been inconvenienced by this error.

How can I change my admin password?

If for some reason the default exercise file username (admin) and password (booth) don’t work, you can change them in the database itself using phpMyAdmin. (This technique is demonstrated in a video from Chapter 8, “Recovering from disasters”.)

  1. Open your Drupal database with phpMyAdmin.
  2. Go to the “users” table. Click the Browse icon.
  3. For the row where uid = 1, click the Edit icon. (Note the value under the “Name” column: That’s the administrator’s username.)
  4. In the “pass” row, select “MD5” under the “Function” column
  5. In the same row, enter your new password under the “Value” column.
  6. At the bottom of the screen, click the “Go” button.

You should now be able to log in with that username and new password.

Searching inside the videos

On Drupal.org, NigelFK asked:

…as far as I can tell there is no information telling the student exactly what is in each section of the DVD. I know there are headers like ‘Enabling Other Content Types’ for example but you’ve got to watch that section to find out exactly what’s in it…

Personally I’d REALLY appreciate some sort of index. Any chance you could create one?

You’re in luck! The videos are closed-captioned, and the captions are searchable. Here’s what you do:

1) On the video series’ home page, click on “Closed Captioning” to expose those controls.

2) Enter the text you’d like to search in the “find text in captions” box.

What happened to my .htaccess file?

A few times during the Drupal Essential Training video series, I say to copy a Drupal installation by selecting all the files in the folder and then “dragging and dropping” them, either to a server or another location on your local computer. This is not the best way to do so, as the hidden file “.htaccess” will not be copied. Two ways to get around that problem:

  • When installing Drupal for the first time: Instead of copying files from the Drupal folder, move the entire folder to its target location and rename it. This is the easiest solution for those without experience with Unix.
  • Use the command-line interface to copy the .htaccess file.

The .htaccess file is a place to put custom directions for your Apache Web server. Failure to copy this file usually doesn’t cause problems, unless you’ve modified it in some way. If you find it missing, you can grab a fresh one from a fresh Drupal download, or (if experienced with such things) get the latest version from the CVS repository.

This one was my fault. Sorry for any inconvenience!

On Lynda.com I hear audio, but don’t see video

Skip Taylor reported on drupal.org:

I wanted to see the video quality so I tried one of the free demo tutorials. There’s audio and a green background. I have the latest QuickTime installed and using Firefox 3 with the QuickTime plug-in. Should there be more to this than a green background?

Indeed there should. 🙂 Lynda.com gave him the following steps, which solved the problem:

I had to change a setting in Quicktime 7.5:

  1. Open the QuickTime Application
  2. Go to: Edit > Preferences > QuickTime Preferences
  3. Click on the Advanced tab
  4. In the Video section (midway down in the window), select the option for Safemode (GDI only) instead of DirectX
  5. Restart the browser.

Please comment here if that doesn’t work for you.

WAMP icon has disappeared from Windows’ system tray

L.H. writes: “In Windows Vista, the WAMP icon disappears from the system tray after x time (not sure about the duration protocols). To make the WAMP icon re-appear (so that you can access localhost, phpmyadmin, php.ini, etc.), you have to activate the “start WAMP server” icon (from start menu, desktop or wherever); then the system tray icon reappears. Pain in the chicken, but that’s Vista.”

Can’t import a Drupal site in Windows

This problem often occurs because one of the default settings of WAMP is too low. You’ll see the issue if you go to the MySQL-controlling phpMyAdmin screen (probably at http://localhost/phpMyAdmin) and click “Import”: The maximum file size allowed is 2,048K. That’s only 2MB, and the databases for most Drupal sites are much larger than that. (The example site for Drupal Essential Training gets as big as 5MB.)

To change this limit:

  1. Click the WAMP icon in your system tray.
  2. Select “PHP”. In the side menu, select “php.ini” to open a file containing PHP’s configuration options.
  3. Search for the line, “upload_max_filesize = 2M”.
  4. Change it to “upload_max_filesize = 64M” (or whatever you like). You can get by with as little as 32M, but I recommend at least 64M, particularly for Drupal 7.
  5. Save the file and restart WAMP. (Better yet, restart your computer entirely to be sure. I’m frankly not sure whether it makes a difference.)
  6. Now go back to that “Import” screen in phpMyAdmin: You should notice that the limit has changed.

Thanks to L.H. for pointing this out!