Andrew Mills

You could use custom menus & categories to create the equivalent of two blogs.

This video should help walk you through the basic concept:

https://www.youtube.com/watch?v=RUG-_nE2tEc

Your specifics will be different, of course. You’ll want to label all your current blog posts with a category of “Reflections,” for example, and then replace your current Reflections menu with an identically named menu item that draws posts from the Reflections category.

Then create a new category called “Prayer Request”, add a post or two with that category, and create a second menu item that pulls from the category of “Prayer Request.”

When I’ve had .sql files that were too large to import via phpmyadmin, I’ve been able to sometimes work around the size limit by *carefully* splitting the .sql file into a series of files in a plain text editor.

I’d think that would generate a lot of annoying emails very quickly, but maybe that’s just me.

I found this plugin via Google search: https://urbangiraffe.com/plugins/audit-trail/

But I’ve never used it myself, so I can’t vouch for it.

Just a guess mind you, but I’d say either the WordPress URL or the Site Address URL found in Settings -> General aren’t correct.

When you installed WordPress this second time, did you put it in a subfolder?

It will depend upon the specifics of your new web hosting plan. But, yes, it is possible and many people do exactly that. Just check with your web hosting company support FIRST to make sure that the plan you have will support hosting multiple/different websites.

Are you trying to start over using WordPress from scratch, or are you trying to repair/restore the installation that you previously had?

It looks like you’ve got your website back up and running again. Care to share what the problem was, and what you did to resolve it?

If you have access to cPanel, you can get inside of and *carefully* alter your WordPress installation by that means. But first things first, all right?

Let’s see if we cannot get some more detailed information with the WordPress debugger, before we start taking any action.

When you go into your cPanel, do you have a File Manager icon/link?

If so, open that and find a file called wp-config.php. There is one line and only one line you should alter.

Please change this: define(‘WP_DEBUG’, false);

To this: define(‘WP_DEBUG’, true);

Save the change, and then IN ANOTHER TAB OR WINDOW, try to visit your website. It will not be fixed, but there will most likely be an error message– possibly more than one. Copy and paste the error message(s) for safe keeping, so you can post it back here later.

Almost done. Now go back to the wp-config.php file and change the true value back to false again, and save the file. We are returning the wp-config.php back to its original condition, in other words.

Then, if you’d be so kind as to share the error message(s) with us, we can better advise you how to proceed in repairing things.

So the public side of the website still displays properly, but the admin dashboard is coming up completely blank, yes?

Have you installed any new plugins recently? Or made any modifications to the functions.php file?

I understand re: copy & paste– been there myself. Thanks for taking a look.

A child theme based on the Headway Base. I’ve put an entry on their support forums, and they are looking into it.

Sorry to have taken your time– I knew themes could slow things down in general on WordPress, but I didn’t know they could operate as early as the .htaccess point of things in the sequence.

Clearly I still have lots more to learn about WordPress. Think I’ll try to get that debugger tool running this weekend, if I can.

Thank you again for your time.

It’s looking like the theme is somehow responsible. (Which baffles me because I thought the .htaccess file was more of an Apache thing than a WordPress or WordPress theme thing.)

Basically, we switch the theme to TwentyEleven, and it loads everything in under 5 seconds. We switch it to the regular theme and just the trailing slash rewrite takes longer than that. But proving it definitively is beyond my current skills/tools.

I guess I need to find some kind of PHP debug tool that will let me do a step debugging walk through. Or am I barking up the wrong tree?

Hi, Ipstenu. Thank you for the reply.

> W3TC isn’t turned on. If it was, it would have some diagnostics in the source code.

I could easily be doing something wrong, but the plugin says it’s enabled in green letters on the General Settings tab.

Is there a parking brake I need to release somewhere? ??

Kidding aside– I’ll go back and take a second look at the installation instructions. Maybe I missed a checkbox or something.

> It shouldn’t be taking 8-12 seconds to parse the / – That should be near instantaneous.

Yes, I know. And I’m thinking neither CloudFlare nor W3T Cache will help improve that situation.

Any suggestions about how I might streamline or sequence the .htaccess file . . . or is it time to start searching for a better webhost?

It looks like it is generating XML when I view source in my browser.

Did you do something to fix it since you posted?

FWIW, when I scroll to the bottom of the feed, I am seeing this error message

<b>Fatal error</b>: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16 bytes) in <b>/home/content/01/8489601/html/wp-includes/wp-db.php</b> on line <b>1449</b>

It looks like the process runs out of memory before it can complete the task?

It may be innocent, since actions such as changing your permalinks settings within WordPress would legitimately re-write your .htaccess file. I’d suggest inspecting your .htaccess and comparing it against a copy of .htaccess from a backup of your site dated prior to the report, so you can identify precisely what was altered. Once you know what’s been changed, you can tailor your response accordingly.