ibullock

Hi mzimmers,

The path name should be the same as the path to your wp-admin but with the /wp-admin removed.

That being said, I’ve had times when changing the path in the admin area has failed to work. In these cases you need to make changes directly in the database.

Let me know if you’re still having trouble.

Hi mzimmers,

I was flagged for “spam” last week, so that might explain my posts not displaying.

Anyway, in your wp-config, did you check the name of the database there and the one you created on your localhost? If you named your database at all differently on your localhost vs. the remote server this would cause the error.

An error establishing database connection practically has to be a misconfigured wp-config file, since it handles the connection to the database.

Do you have the WordPress install in the root of your localhost?

I generally install mine in a subfolder so that they can be accessed with URLs like https://localhost/My-Website/ this helps avoid problems with any other files stored in the root.

For example, MAMP/WAMP have some files in the root by default that help you browse the directory.

Hi incedo,

You’ll need to change:

<img href="/wp-content/images/map.png" alt="Error" />

to:

<img src="/wp-content/images/map.png" alt="Error" />

href is used for links where as src is used for images.

Hope that helps!

Hi ashishpurohit,

This problem is likely with the permalinks to the pages.

With localhost installs you have to enable Apache’s mod_rewrite module to get permalinks to work.

There’s a tutorial here: How to make WordPress Permalinks work in Xampp

The tutorial is XAMPP specific, but it applies to MAMP/WAMP too.

Hi mzimmers,

You’re probably going to have to change the username and password for the database in the wp-config.php file for your WordPress install.

By default the username for your localhost should be “root” and the password will probably not be set.

The lines of code in the wp-config should look like this:

/** MySQL database username */
define('DB_USER', 'root');

/** MySQL database password */
define('DB_PASSWORD', '');

You might also need to change the WordPress address (URL)and the
Site address (URL) in your WordPress admin under Settings>General Settings.

You may also want to try changing the following in your php.ini:

memory_limit = 1000M

You might not need it at 1000, but you get the idea.

I’m not sure of the differences between WAMP and MAMP, but on my WAMP installation there are two php.ini files, one in the php folder as you’ve noted, and one in the bin for Apache.

As Chouby noted, make sure you restart your sever, or at least the PHP service.

Something else to check are any .htaccess files for the site or the root directory. Upload size can also be affected by changes there. That being said, I’ve made my fair share of WordPress installs and never had that problem. The php.ini seems to be the typical fix.

Looks like something got uncommented in the theme’s functions.php and was causing a bunch of errors down the line.

Thanks for the help!

Hi Brad,

I’m just getting a start on debugging things this morning. Looks like a few plugins are having issues. “Headers already sent” seems to account for most of them. But some are also coming up with undefined indexes.

Thanks for the tip about the DEBUG setting in wp-config, I don’t know why I didn’t think about that.

I’ll post again once I’ve got things figured out.

Here’s a pastebin of what the page code looks like when I view page source:

https://pastebin.com/8mqmUH0e

Things look pretty normal other than the closing tags not rendering.

There’s really not much to put into pastebin. The code as it stands is simply HTML ending tags for the body and html elements, but anything I put after the wp_footer call doesn’t execute.

</div>
<?php wp_footer(); ?>
</body>
</html>

I’ve solved the issue. Here’s what fixed things for me:

Changed reading settings for “Blog pages show at most” from 10 to 5.

That solved the 404, but then my query wasn’t working properly so I changed it to look like the follow:

$year=$wp_query->query_vars['year'];

$month=$wp_query->query_vars['monthnum'];

$page = (get_query_var('paged')) ? get_query_var('paged') : 1;

query_posts('cat=3&paged='.$page.'&posts_per_page=3&year='.$year.'&monthnum='.$month);

Hope this helps anyone else looking to paginate their archive!

Any suggestions for something to look into as a solution?

This is happening on another site I’ve worked on as well, only on it there are some sections of the archive that paginate perfectly.

The link for my localhost is:

https://localhost/Wordpress/2011/02/page/2/

They’re exactly the same, and also producing a 404.

Oh, and I’ve tried changing Permalink structure, but still get the same thing.