jayseae

Nice work! I (among others, I am sure) don’t often think about messing about in the apache configuration files – so well done, and glad you got it sorted out!

Overlooked that one, sorry. Missing files can certainly resolve as 404 errors, since that is what they are, but didn’t think of that as an option for 403 errors!

Nonetheless – the wp-admin directory shouldn’t contain any actual content (and it certainly doesn’t contain any content now, regardless). There are scripts, but they are typically not modified by users.

The best way to get you up and running is going to be to copy the contents of the existing directory from your other site over to the new one.

I’d say there is an above average chance that will get you going again. If not, then it’s onto the next item at that point.

According to the Facebook Debugger, you have some errors in your page when trying to share it.

One that stops it is that the fb:admins value is invalid. A bunch of stuff in there – but it chokes on the very first character (which is “{“). It looks like an array perhaps, but the values are invalid.

Also, you don’t have a valid image for your site – this is according to the plugin.

Check your plugin settings for WordPress Facebook Open Graph protocol – the admins are incorrect, and the image is missing. Correcting these may help.

Great, glad that it worked – I think the header/footer is what threw me off in the first place, but totally my fault for sending you down the wrong path. Hope I didn’t get you too lost, and glad that you’ve got it set now!

This is really a part of #2. Using an FTP client, you would need to download each of the images and then upload it to the new server.

If you put them in the same location – so that the file name will be the same – then you won’t have to do any mapping/rewriting at all. If you change the file location (and/or name), then you will have to create rules for the images as well, so make sure you keep good records of which files you move, and where you move them to!

The comment won’t be stopped, but it will not be published. You can also try a plugin – there are plenty of them out there.

I only mentioned two hosts because your IP addresses resolve to different locations.

Just as a technicality, don’t delete your theme, because then you may lose data (and the time spent on it). It would be better to deactivate it instead. Since you cannot log in, try renaming it via FTP (or a control panel). This may render your outward-facing site inoperable for a time, but it may also allow you to log in, if it is indeed the problem.

Immediately after you rename it, try logging in and if it works, try reactivating a default theme, such as Twenty Fourteen.

Couple of things…

First, I was looking at the wrong template (series of templates, actually). One important reason why child themes are important! So some of this may not apply. Sorry about that. Still, it may have some useful information, so:

The language file (for you) is twentytwelve.pot, found in the languages directory under your theme directory (technically, in your parent theme directory, since you haven’t made any changes to it).

You can read more about doing that here, in case you want to add it to your child theme and make any changes.

The function that says:

<?php _e( 'Comment navigation', 'twentytwelve' );

Is actually calling the language function for “Comment Navigation”, and returning the localized string for that text – so if you have your language set to some other language, it would return that string instead.

In the single.php template, you’ll see a line like this:

<?php get_template_part( 'content', get_post_format() ); ?>

This calls loads the content, into the posting format. What is the posting format? Well, it depends. The default one for that theme is in content.php. But you can define alternate templates. In that case, you would need to look and use that template instead.

In content.php, however, you will see a line that looks like this:

<?php comments_popup_link( '<span class="leave-reply">' . __( 'Leave a reply', 'twentytwelve' ) . '</span>', __( '1 Reply', 'twentytwelve' ), __( '% Replies', 'twentytwelve' ) ); ?>

In a somewhat confusing fashion, it is named comments_popup_link. I don’t have statistics, but I suspect for most people, it just points further down the page. Regardless, this is likely where your link comes from – however, the default content.php looks a lot different than your page.

For instance, the default one has that link in the header, where yours is in the footer. So perhaps you’ve already made some changes. Regardless, this is where you would want to make the changes, not where I was pointing you, so sorry for the misdirection!

I think the rule that really affects you is this one:

media="all"
@media screen and (min-width: 846px)
.full-width.singular .site-content .hentry.has-post-thumbnail, .full-width.home .site-content .hentry.has-post-thumbnail {
    margin-top: -72px;
}

It is overriding this rule:

media="all"
@media screen and (min-width: 673px)
.full-width .site-content .has-post-thumbnail .entry-header, .full-width.singular .site-content .hentry.has-post-thumbnail, .full-width.home .site-content .hentry.has-post-thumbnail {
margin-top: -48px;
}

A couple of thoughts.

First, I would make sure you are applying the change in a child theme, or in a Custom CSS plugin, as opposed to the Twenty Fourteen theme itself.

Second, rather than making the change to the .hentry element, I would target it more directly, as that seems to be what is happening in the CSS now – otherwise you might see some other effects down the line. But this is ultimately up to you, and if you are happy with the changes, that is what is important. ??

Getting adventurous now, eh? ??

Okay – this is where it gets a bit more complicated.

Very important. Make sure you are still in your child theme. See in the single.php template, where it has this line:

<?php comments_template( '', true ); ?>

That loads the comments template. It may not output much at all – and this is where it gets tricky. The comments template for your theme is comments.php. Copy that over to the child theme and start looking, if you want to mess with it. You can always remove it if you decide not to do anything.

In comments.php, there is a line that looks like this:

<h1 class="assistive-text section-heading"><?php _e( 'Comment navigation', 'twentytwelve' ); ?></h1>

That line calls the language file to render the text, which will say (wait for it): Leave a reply.

So if you want to add something, that’s where you would put it. However, notice that you have another couple lines in there, that talk about “older comments” and “newer comments”? You probably want to be careful with those, or you may interrupt that flow. Perhaps it would be best to move your Facebook and Twitter links prior to the “Leave a Comment” text. Or after the whole shebang?

If you deleted the first page (named blog), but it’s not in the trash, there must be a reference to it somewhere in order to prevent the second page (also named blog) from being named blog – otherwise you wouldn’t get a blog-2.

The only way to find this is to look at the database itself, using a tool such as phpMyAdmin. The wp_posts table contains the records of your posts (and pages), where you can look to see if there are any records that my be left in there that haven’t been cleaned up correctly. I have also seen mention where there could be a record in wp_terms that may cause this problem – though I have not seen that one personally.

This is all because WordPress does not allow two pages (or posts) to share the same name, so you would need to get rid of that original one first (or restore it) in order to restore your site to “blog”.

These rollovers all seem to be working for me in Chrome and Firefox (as well as IE). Are you still having a problem or did you get them fixed?

This shows up fine for me in Chrome and Firefox. Are you still having a problem?

IE is a bit slower than Chrome (or Firefox), but the menu for “Guide” shows up for me. This is IE11 in Windows 7. Are you still seeing the problem? Is this the menu you mean, or a different one?

I see a decent amount of space between each post, in Chrome and Firefox. Are you still seeing the problem?