sonofadoc

I tried all of the above and nothing worked. WordPress was showing me the way all along. On the Permalinks page there was a message at the top of the page saying to update my .htaccess file. Down at the bottom of page it provided the mod_rewrite code I needed to put into the .htaccess file. I copied the code and pasted it at the top of my .htaccess file and voila! Like magic. Of course you will need to replace localhost with your file path to your server.

`<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /localhost/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /localhost/index.php [L]
</IfModule>

• This reply was modified 4 years, 5 months ago by sonofadoc.
• This reply was modified 4 years, 5 months ago by sonofadoc.

You helped me solve my problem. Just for ducks I went into FF and entered the URL and it loaded the home page right up. It turned out it was a caching issue in Chrome. I just cleared the cache and everything works. Chrome always does that to me! Thanks for your help.

Well, you would wouldn’t you since you are not connected to my “localhost” server.

localhost/www/bigmesses/ If I type into the address bar localhost/www/bigmesses/wp-login.php I’m able to login to the admin. But localhost/www/bigmesses/ should open to the home page but it doesn’t. I instead get the 404 error.

• This reply was modified 6 years, 10 months ago by sonofadoc.
• This reply was modified 6 years, 10 months ago by sonofadoc.

Easy peezy lemon squeezy – as you said it would be. I’m up and running with MAMP and WP.

Thanks for the help Lyle! Take care.

Well thanks Lyle,

I’ll give it a whirl, there may be something along the way I didn’t do correctly and I may see what it is as I follow your instruction. As far as the URL goes localhost:8888 you are given the option to change that in MAMP to just localhost/. I did forget to mention that the server was working fine as I had some static web pages in the htdocs directory that loaded right up, and the index.php file loaded up OK. It is the WP database that I’m having trouble with.

Thanks again for the famous 3 minute install and I’ll let you know how I fare with it.

Thanks Lyle,

I’ll address the enquiries in the order they appear.

Q. Did you enter the database name that you created?

A. I created the database in the terminal and it exists. The database name is in the config file in DB_NAME ‘name of database’ is the same name of the database I created in the mysql terminal.

Q. Did you use a plain text editor to enter the values in wp-config.php.

A. I’m using Text-Mate so it should be OK out of the box Although text-mate is also a new app to me as I’ve been using notepad++ on a windows machine so it’s possible I may need to configure it in some way as far as line endings or little endian big endian or some such.

Statement: Not sure why one would use the terminal for the db when using MAMP as it is so easy to use the supplied phpMyAdmin from the Tools menu on the MAMP Start Page ??

Response: I actually first learned to create databases via the terminal so it’s a natural inclination for me to do so. Also, why use that big clunky program when you can just type CREATE DATABASE db_name; and be done with it?

I’ll try again from scratch looking at your instructions Lyle. Thanks for the hand.

UPDATE: One thing I discovered after my last post last night was I couldn’t figure out what my password and username was, because I didn’t remember creating either one during the setup process. The last thing I tried was leaving the username and password fields blank (in the wp-config file) and then I got a different error message when going to the URL localhost/example/wp-activate.php. The message said was able to access the server so the username and password was ok, but couldn’t connect to that particular DB_NAME. I know it exists for the simple reason when I enter SHOW DATABASES; in the terminal – there it is. To double check I went into phpMyAdmin panel and it is there also. So there is no question it exists so I can’t figure why WP and mysql can’t find it.

Rather than spend hours, days, or weeks trying to find out why WP loads so slowly I just uninstalled my version of Apache and the program stack under it (PHP, MySql) installed a WAMP stack and then installed the newest version of WP. Everything is now copasetic.

I’ve updated WP and I still have the same problem. Login, pages load slower than molasses. No good, can’t work like that.

False alarm. I’m at a complete loss as to what was going on, but the images are working fine now in whatever path I place them in.

Thanks for jumping on board so fast and helping out. So much help here. This forum is jumpin!

The web property is on my local server, but you can go here for a screenshot if it helps https://sitekitchen.us/screenshot/

Finally! I found the solution here https://www.webdevdoor.com/php/mod_rewrite-windows-apache-url-rewriting/

Uncommenting or removing the hash tag on “LoadModule rewrite_module modules/mod_rewrite.so” in the http.config isn’t going far enough.

The 2.4 version of Apache http.config file looks a little different than the 2.2 version, so you might have to look a little harder for the blocks of code. The steps on the above website (link)are for Apache 2.2 and are easy to follow.

Here are the blocks of code you need to change in 2.4 which comes in the new version of wamp.

‘<Directory “c:/wamp/cgi-bin”>
AllowOverride None
Options None
Require all granted
</Directory>

Change it to:

<Directory “c:/wamp/cgi-bin”>
AllowOverride All
Options All
Require all granted
</Directory>

Find this block:

<Directory />
AllowOverride none
Require all granted
</Directory>

Change it to:

<Directory />
AllowOverride All
Require all granted
</Directory>’

That’s it. All of my permalinks on both local servers began working like they should, With the Pretty Permalinks instead of the default.

For the sake of eliminating possible problems I’ll add this to my post.

I uncommented: LoadModule rewrite_module modules/mod_rewrite.so in the http.conf folder

The .htaccess reads like this in both my local and host servers:

‘# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wp_sandbox/wordpress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wp_sandbox/wordpress/index.php [L]
</IfModule>

# END WordPress
‘

Sure, you can access: here

Of course the links on the navbar aren’t hooked up yet, but still we shouldn’t be getting 500 errors I don’t think.

It looks like all the errors have to do with Jetpack and my dropbox backup.

Well, I just don’t know. I uploaded my theme files into another instance of WordPress I had on my host server. Now I have all the options in the dash that 2014 has like I should. My slideshow is broken, but that’s another issue.

I should have known, I’ve had other problems with WP acting differently on my host server than on my local server (Apache 2.2).

You’re welcome to visit the site here: BSWD

If you want to login to the admin let me know and I’ll give you the keys and you can take her for a spin.