kengr

Never mind. I hadn’t placed the JavaScript code inside a <script> tag. Once I did that, the error message disappeared and the correct code was generated. Sorry for the noise.

Thanks.

Thanks.

I’ve been working with it for a couple of hours now, and it seems to be working well with the Theme My Login plugin.

I ended up creating a brand new MySQL database, importing the SQL backup file into that database, editing the wp-config.php file to point to the new database, and I’m back in business.

I would still be interested in knowing why I was getting the reported error when attempting to restore to the existing database that had structure but no tables.

By the way, based on my notes, it appears that I had All In One WP Security 4.3.8.3 installed at the time the database backups were created. But I’m not 100% sure that there wasn’t a plugin update somewhere in there, so this version is as close an approximation as I can come up with right now.

Thanks for your reply.

Unfortunately, because Crayon conflicted with Enlighter, I couldn’t have them active at the same time. I had to move forward and change all the code chunks in my blog site to use Enlighter, so that it would be usable by my users/customers/visitors. I used up my available time converting everything to Enlighter.

At this point, I’m going to have to wait for a Crayon version that has already been tested under WordPress 5.1, before I can invest any more time moving back to Crayon and experimenting.

Since I can’t seem to get this to work, I have temporarily switched from the Crayon Syntax Highlighter to the Enlighter plugin. I don’t like Enlighter as much as Crayon, feature-wise, but it works reliably in WordPress 5.1.

The page listed at the beginning of this thread is now using Enlighter.

If you have a way to get Crayon Syntax Highlighter to work reliably in WordPress 5.1, I would certainly be open to switching back to it.

I was able to solve the pasting location issue by revering back to the Classic Editor (using the Classic Editor plugin).

But even in the classic editor, I’m not getting any of the syntax highlighting, color scheme, or bar at the top.

Any ideas on how to get this working properly in WP 5.1 would be much appreciated.

Understood.

Thanks very much for your assistance and your advice.

Thanks for your reply.

When I went to check the PHP version in Plesk, it looked like PHP was completely turned off. That certainly didn’t look right, so I turned it back on to version 7.0.33 (which is what it was before), and now my site appears to be back to life…home page, pages, posts. So, thanks for asking the question about the PHP version number…that led me to the solution.

I had opened a support ticket with the web host support folks, but they haven’t responded yet. I will update them that the problem is resolved now.

I’m not sure why PHP got turned off. I checked the site operation five minutes before attempting the 5.1 upgrade, and it was working then. But immediately after the attempted upgrade, it stopped working. And as soon as I turned PHP back on manually, the site started working again. Coincidence? Cause-effect?

Is there anything in the upgrade process that might have temporarily disabled PHP, and then failed to re-enable it?

I’m trying to learn what to avoid doing going forward.

Thanks again.

• This reply was modified 5 years, 8 months ago by kengr.

I have some other plugins going, but I don’t think they interact with the theme. I will do some experimenting and see if I can get rid of it. If I find something, I’ll let you know.

In the meantime, thanks in advance for fixing the other problem in the next update.

I am using A2Hosting, which is running Windows Server for my shared hosting account. They provide WordPress and access to a lot of plugins including yours.

Are there some guidelines somewhere on how to set the permissions properly in Windows Server to match your recommended permission settings?

Yes. I have tried deactivating all other plugins, and have tried it with the following themes:

• Twenty Seventeen (default)
• Twenty Sixteen (default)
• Twenty Fifteen (default)
• Colorskin (the theme I normally use)

I have triple-checked my reCaptcha strings as well.

But no matter what I do, I cannot get reCaptha to show up in any of the TML pages (login, register, etc.).

Just to make sure that I could get my reCaptcha strings to work in WordPress, I deactivated TML and activated WP reCaptcha Integration, and the reCaptcha worked fine there. Deactivating that plugin and reactivating TML (and verifying all the settings again), I got no reCaptcha at all.

Thanks for your reply. Yes, I understand that. But your plugin adds a menu item named “Reset Password”. If a user clicks this menu item, they are sent to the page resetpass which is redirected immediately to the page lostpassword/?error=invalidkey, and they get the red error message “Your password reset link appears to be invalid. Please request a new link below” before they have even had a chance to reset their password. This happens whether they’re logged in or not.

Is there any way to configure this so that, when the user clicks on Reset Password, they don’t get the red error message, but instead are given a chance to just reset their password? In other words, is there any way to get the Reset Password menu item to land on the resetpass page and start the reset password process, rather than landing on the lostpassword page with a red error message?