MikeHarrison

Will do.

Thanks, Melissa!

The only plugins I use are:

Akismet
All in One Webmaster
Bulletproof Security
Captcha
Contact Form
Platinum SEO Pack
Redirection

A couple of those may have updated but, beyond that, nothing.

Thanks, Melissa.

I have posted a question on Redirection’s support forum asking why I’m seeing 0.0.0.0. I’ll let you know the answer.

Thanks!

The ip address 0.0.0.0 does not show up in the BPS security log. It shows up in the Redirection plugin’s log of 404 errors. This address is apparently trying to access pages or other files on my site.

Again, I posted this here out of curiosity to get feedback from others as to whether it *might* pose a security issue, as I’d read 0.0.0.0 was (or could be) a spoofed address. And, if someone if spoofing an ip address (just as entries on caller ID can be spoofed), I figured they were up to no good.

Thanks!

Thanks Melissa.

A hard refresh is the first thing I tried when I wasn’t able to see the favicon, but I should have checked my other browsers before posting here.

Safari and Chrome both display the favicon but, for some reason, Firefox – the very latest version – does not. I have just reported the issue to them.

And… while typing this I Googled the issue and not only saw that others are having the same problem, but also that Firefox WILL display favicons, but ONLY in tabs, not windows. So, I must not have ever noticed the issue before.

Sorry to bother you with this, but I do appreciate your time and the feedback.

Thanks.

Never mind.

As I write this, at least two other people are reporting the same problem I’m experiencing in the thread: Fatal Error.

Yes, I’ve saved the favicon.

Here is a link to a screen shot showing the favicon, selected, and the Save button disabled (because the change had already been saved):
https://goo.gl/wfpRH7
and here is the site itself:
https://goo.gl/bCVLFR

Thanks!

I certainly don’t mean to question your knowledge and experience, but couldn’t I delete all of the WP files/folders from the root directory – leaving the existing .htaccess and index.php in place – and then move the WP files/folders from the sub-directory into the root?

Yes, I realize the site will be completely down during that period, but it should only take the time required to move the files, plus any time to make any necessary adjustments, no?

That is my goal, yes.

So there is no getting around having WordPress and all content in both the root directory and sub-directory, even though only one set will be used?

Yes, thanks! I was going to backup both sites before going forward.

The new site is in a sub-directory titled “newsite.” But it wasn’t the name of the directory itself that is confusing to me; it’s why I would change that one line of code in index.php TO the sub-directory when the site will no longer be in that directory.

Are you suggesting, then, that I should just REPLACE all the WordPress files and folders in the root directory with the ones from the sub-directory? Or have I totally confused myself?

Yes, to both questions. The changes I made to actual content were minimal; most of the changes I made were to adjust the new theme to my liking. My site is a very simple, basic site; only a handful of pages, and I’m debating whether I even want to continue having a blog, which was rarely updated at all anyway.

And, YES; in case I failed to make it clear, I’ve already installed the mobile-friendly theme into the original, root directory WordPress install, so I’m hoping the adjustments I made to the theme in the sub-directory will also copy over to the root directory.

One of the reasons I’m very cautious about making sure I get these changes correct is that I don’t want to accidentally disrupt the configuration of the files associated with the plugin overseeing site security.

Thanks for your understanding!

Please bear with me; I want to be sure I get this right. See, now that I’ve updated the content, I would prefer not to have anything at all remain in a sub-directory; I’d like everything to reside in the root directory.

My original WordPress installation (all the WP files and folders) are in the root directory; not a sub-directory. But I did create a sub-directory only for the purpose of changing to a mobile-friendly theme (and adjusting content to display properly using that theme).

So, the instructions you referred to are unclear to me, only because my original WP install is not in a directory called “WordPress,” as the example uses.

Am I to assume the General panel referred to in Step 1 is the one I’ll have access to when logged into my updated site?

If that’s the case, then: if I am copying the index.php from the sub-directory into my root directory, I don’t understand why I would change:

require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );

to

require( dirname( __FILE__ ) . ‘/wordpress/wp-blog-header.php’ );

Because – when I began the update process – I copied my original content into the sub-directory by having WordPress export that content in an .xml file, which I then imported into the new theme to make the changes, is it not possible to do the same thing in this case: have WordPress export the updated content from the sub-directory and then import it into the root directory?

Again, apologies for my ignorance and I do appreciate your patience and assistance.

Thank you for the quick response! Much appreciated.

However, I’d prefer not to unnecessarily clutter my server with two WordPress installations.

Could you please point me to instructions on how to copy/move only what is required to display the new/updated content using my original root directory WP installation?

I’m asking here, rather than asking my hosting company, because I often get conflicting or confusing information from them.

Thanks!