Jesse Owens

Hi @djblade311

Thanks for the heads up! We’ll update the template in the next release. In the meantime, it’s safe to ignore the warnings.

Hi @softpol

We’re still working on the underlying bug, but I have discovered a workaround that might get you past the problem.

In my testing, the bug only happened when Total Upkeep was first activated from the Network dashboard. I was able to install the plugin, activate it only on a single site, and then activate it for the whole network.

Let me know if that works for you!

Hi @softpol

Thanks for the info! I was able to replicate the same error in PHP 8.1.9 with Multisite.

The deprecation warnings are to be expected when using PHP 8.1.*, because WordPress still only has “beta” support for 8.0 and above.

I was also able to confirm that Total Upkeep still works on Multisite using PHP 7.4, and works on WordPress single-site with PHP 8.1, so the issue is some mixture of Multisite together with the newer PHP version.

We haven’t found the root cause yet, but I’ve engaged our developers to help investigate further, and I’ll update you when we have some news.

Hi @jdsweet99167 –

Thanks for the kind words! Sorry about the hassle of signing up for your www.ads-software.com account, but I think you’ll find a great community here, full of WordPress experts who can help you build and succeed with all your website ventures. Cheers!

Hi @softpol

Thanks for the logs!

First thing to mention- we don’t extensively test Total Upkeep with Multisite. That being said, the last time we did test it should at least work when used by the Super Admin to back up the entire network. It definitely won’t work for individual network sites. We do strive to make sure that it won’t create fatal errors for Multisite, but this plugin might not be the right solution for your sites.

I also noticed quite a few Deprecated warnings in the logs you posted, can you also share the PHP version you’re using? With that information, we should be able to try and replicate the issue and see if we can find a good way to make it compatible again.

Hi @softpol –

Thanks for the update! This is my first time seeing a site with Total Upkeep on a Raspberry, that’s pretty cool!

I don’t think that the message about PCRE is related to our problem, that just means that ModSecurity is configured to use a different version of PCRE than PHP is configured to use.

PCRE means, “Pearl Compatible Regular Expressions,” and it’s the library that adds RegEx functionality. You’re loading PCRE 8.44 and PHP has 8.39. I’m not an expert on these, but from what I see after a little Googling seems like you’d see bigger issues (like segfaults) if that was causing a problem. I think that’s probably something to do with the Apache and ModSec PPA repositories for Raspbian and would take some high-level Linux system work to resolve that.

Let’s try another tactic. Right now, we’ve been working purely with the Apache error logs. It’s possible we might get more insight using the WordPress debug mode. Use the instructions in this article to enable debugging and the debug log from your wp-config.php file. Specifically, add these lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false ); //Avoid showing errors to your visitors
define( 'WP_DEBUG_LOG, true );

Then, reproduce the error and look for the wp-content/debug.log file to see if we can get any more info. I also recommend making sure you have a fresh installation of Total Upkeep. Run these two commands to re-download it fresh from the repository:

wp plugin delete boldgrid-backup
wp plugin install https://downloads.www.ads-software.com/plugin/boldgrid-backup.1.15.2.zip

Hi @softpol –

Thanks for reaching out! That’s a very strange error, but we’ll do everything we can to make sure you can get back into your dashboard.

In the first error you listed, the function wp_kses() is not defined, and in the second error, another function (that isn’t named in the log output) is not defined. Since wp_kses() is a core WordPress function, my first suspicion is that you may be missing some WordPress core files.

Did you recently perform an update to WordPress core? Version 6.0.3 was released just a few days ago with important security updates. Sometimes during an update, if the update process was interrupted, it can cause you to be missing some files.

Here are a couple of things to check. You mentioned you have the ability to comment out lines and rename folders, so I’m assuming you have SSH or FTP access to the site, that’s good news.

Check that the file wp-includes/kses.php exists and matches up with the core file from the official repository.

If you have SSH access, you can also use the WP-CLI command wp core verify-checksums to make sure all your core files are intact.

Since you can log in while the plugins are disabled, you may be able to re-install your current WordPress version through the dashboard. Go to Dashboard – Updates and look near the top for the button to reinstall your current version.

If you can’t log in, you can also reinstall your core files with FTP or WP-CLI using these great instructions from DreamHost.

Hi Gary @1851stamps –

Thanks for the updates! The table tool is a pretty new addition to the Post and Page Builder, so I could be wrong about this, but when I tested with a very large table, these screenshots show what happened to that toolbar when I swap between small- and full-screen editing:
Small Screen Table Tools
Full Screen Table Tools
In any case, I agree with you that it’s annoying to have those tools way down at the bottom in cases like yours, so I’ve created an bug ticket for our developers to improve the experience.

Hi Gary @1851stamps –

Thanks for the update, sorry I missed your first reply!

Those table controls do normally show up at the bottom of the table, but there is a workaround you can use.

If you switch to the Full-Screen editor style, the table controls will show up at the top of the screen and float along with you while you scroll. Look for the icon next to the device sizes in the top toolbar, or use the shortcut Ctrl+Shift+F to toggle the full screen editor.

Hi @1851stamps –

Sorry to hear about the trouble! We’ve seen a similar issue before in sites that are running both Post and Page Builder along with Advanced Editor Tools (previously TinyMCE Advanced). Are you using both plugins?

Since they both rely on the TinyMCE table editor functions, some of the tools you’d normally find in the Table toolbar are in the TinyMCE drop-down menus instead. We’ve tried to ensure that both play as nicely together as possible, but to achieve the best compatibility some of the tools are in TinyMCE Advanced’s menus, and some are in the Post and Page Builder menus.

If you’re not using TinyMCE Advanced, can you let us know if there are any other active plugins that might be interfering? You can easily get a list to paste here in your Tools – Site Health – Info – Active Plugins menu.

Another thing to check is your browser’s JavaScript error console. In most browsers you can open it with the Shift+Ctrl+J shortcut. Check your console while editing a page and clicking into the table as you described, and let us know if you see any errors appear.

Hi Mike-

Sounds like progress!

1- is it ok to exclude all these files?
Yes, I think you’ll be just fine excluding these. They’re protected by the system for Managed WordPress. The whole reason they’re owned by root is so that they can prevent any unauthorized changes to them. They’re probably actually symbolic links to a protected, central set of WordPress Core files that the Managed System regularly checks and maintains.

2- index.php and index.html with 0 byte filesize?
I betting that if you take a look in the log for that backup, in Total Upkeep – Tools – Logs you’ll actually find an error reading them, as well as the fatal error writing them in the restoration log. This was just a warning, so it didn’t prevent the backup from being taken.

I think it’s probably a good idea for the plugin to recognize these and skip restoring them without failing. I went ahead and added a feature request for our developers to add in the future.

3- Is there any way to specify these files to exclude on the restore instead of the backup?

No, there isn’t right now. I added that to the feature request as well, I think it’s a smart idea. That being said, I wouldn’t expect that file list to change in the near future, since WPCORE covers all of the existing WordPress directories. That’d take a major refactoring of WordPress’ core structure and the project tends to avoid drastic changes like that.

Hi @mhartste

Thanks for checking out Total Upkeep!

First thing, GoDaddy Managed WordPress disallows many backup plugins, and while Total Upkeep isn’t specifically mentioned in that list, you may find that the 30-day backups already included with that hosting plan meet your needs.

That being said, my suspicion is that you may not have direct access to any of your core files. That’d be a pretty normal security measure for a Managed WP plan, to keep you safe from hacks and make sure you’re always up-to-date. If that’s the case, you can still use Total Upkeep by excluding the WordPress Core files from your backup files.

When you make a backup, or set up scheduled backups, click the Custom Backup option. You’ll see the default included and excluded files and folders. Simply delete WPCORE from the includes, and add it to the excludes.

This will make sure that your Database and wp-content folder (plugins, themes, and uploads) are still backed up so you can always restore from a bad update and keep your media files safe, while letting GoDaddy manage your core files.

Hi @littlepellizza

I wanted to let you know that we’ve just released Post and Page Builder 1.21.1 which improves compatibility between Advanced Editor Tools and Post and Page Builder.

Because both plugins use TinyMCE’s native table tools, if you choose to use both plugins some of the steps are a little different. Normally, the insert row and column buttons appear below the table, but if you’re using both plugins you’ll still need to use the Tables drop-down menu to insert rows and columns.

Tables that you’ve created with Advanced Editor Tools’ controls don’t respond to all of the customization tools in Post and Page Builder, but we’re working to improve the compatibility more in future releases. At least for now, they should at least work together without completely breaking the editor.

• This reply was modified 2 years, 7 months ago by Jesse Owens. Reason: update copy/pasted message to make sense

Hi @zenbob1

Thanks for reaching out and letting us know about the conflict!

I tested this plugin out, and I do see what you mean. We’ve been working on a few improvements to the “default editor” behavior, especially with other plugins that create Custom Post Types, but in the meantime there’s a couple easy ways you can fix it.

In your Admin menu, go to Post & Page Builder > Settings and you’ll find that the settings for the default editor for each post type is empty. Simply select PPB for the post types you want to use it for.

If you ever find yourself in the WordPress Editor (Gutenberg) on an individual post, click the “three dots” Settings menu at the top-right and you’ll see an option to swap to Post & Page Builder.

Hello @washingtonhdmf

Thanks for reaching out, I’m sorry to hear about the error viewing your stored backups.

The specific issue here is with the Total Upkeep Premium extension, which isn’t hosted here on the www.ads-software.com forums, so I urge you to get in touch with our Premium Support Team at https://www.boldgrid.com/central/account/help/premium or by emailing us at support (at) boldgrid.com. Due to the WordPress forums guidelines, we can’t support our premium products here on the forums.

That being said, we did have one other user report a similar error and they were able to resolve it by deleting and re-installing the Total Upkeep Premium plugin. You can download a fresh copy of the premium plugin from your BoldGrid Central account, at https://www.boldgrid.com/central/plugins.

If you have any more trouble, please reach out to our Premium Support Team and we’ll be more than happy to help you out further.