Brad Markle

Hi @ikfb90,

Thank you for providing the screenshots. However, the JavaScript console displays information specific to the website you’re currently on. The screenshots you sent are from mail.google.com. Could you please try again, but this time open the console while on your website where the issue is occurring?

To clarify, is this your first time using Sprout Invoices? I’d like to determine whether this was previously working for you and has since stopped or if it has never worked.

TRANSLATED:

This is a crappy plugin!
Guys, don’t download this crap! It messed up my access to the WordPress admin panel. I thought my site was done for. Managed to somehow get into the admin, had to thoroughly clean up all these artifacts. No access to the database, the site is down. Cleaned it up through the FTP file manager and got in. A night of frustration, but I’m glad I successfully restored everything and decided to curse these idiots here for it.

Hi @antihryukva We sincerely apologize for the challenges you faced with W3 Total Cache.

We’d really like to help, however without specific details about the issues you encountered, it’s challenging for us to address them directly. We take user feedback seriously and are committed to improving our product. If you or anyone else experiences similar issues, please reach out to our support team with more information. We are eager to assist!

We appreciate your patience and understanding. Thank you for bringing this to our attention, and we look forward to assisting you further.

It sounds like you’re encountering a unique issue with your menu fonts, especially after making adjustments to your menu structure. To help you more effectively, it’s essential to understand the specific changes you made to the menu structure. Could you provide details on what was modified? This information will help pinpoint the cause of the font discrepancies you’re observing.

Regarding the issue with capital “A”s appearing differently, this might be related to HTML encoding issues. Sometimes, characters like “?” can appear due to encoding problems, where the browser misinterprets special characters or symbols. This can result in unexpected font styles or sizes being displayed.

To address HTML encoding issues, here are a few steps you can take:

1. Review HTML Code: Check the HTML code of your menu items for any unusual characters or encoding. Ensure that your website’s encoding is set to UTF-8, which is the most widely used character encoding for the web.
2. Font Consistency: Ensure the font you’ve selected is applied consistently across all CSS files. Sometimes, specific CSS rules might override your menu font settings, leading to inconsistencies.
3. Clear Cache: After making changes, clear your browser and website cache. Caching issues can sometimes cause old styles to persist even after updates.
4. Use Web-Safe Fonts: If the issue persists, consider using web-safe fonts or ensure the font files are correctly loaded and accessible by your website.

If these steps do not resolve the issue, please provide further details about the changes you made to the menu structure and any other relevant information. This will help us offer more targeted advice to fix the problem.

Hi @anjampie We just released Total Upkeep 1.15.5 and we think it should fix this issue. When you have some time, please upgrade and let us know how it goes!

Hi @anjampie. I believe we have a fix for this issue. We should be releasing a patch for it this week, and we’ll keep you updated.

Hi @anjampie, sorry for the delay and I appreciate you reaching out to us on this issue!

I have a few questions to begin the troubleshooting:

1. Has this ever worked correctly, or are you setting it up for the first time? If it did previously work, has anything recently changed with your site? (e.g. new theme, plugin, etc)
2. Is it the same exact backup being uploaded multiple times, or does each one have a unique filename?
3. In your settings, are you using Cron or WP Cron for the scheduled backups?

The wp_clear_scheduled_hook function that we’re watching shows us that the crons are stored in the “cron” option, and are retrieved using the _get_cron_array() function.

What this means is that technically something may be bypassing wp_clear_scheduled_hook() directly and instead just editing the “cron” option directly.

I updated the snippet (here’s the new snippet). It watches for any changes to the “cron” option. If the old value contains “boldgrid_backup_wp_cron_run_jobs” and the new one doesn’t (e.g. it’s being removed), it’ll add it to a Total Upkeep “update_option.log” log (instead of pre_clear_scheduled_hook.log)

Can you try the new snippet?

Hi Mike.

The log files goes from 2022-09-01 16:10:38 UTC to 2022-09-01 16:10:50 UTC, a total of 12 seconds.

The first time boldgrid_backup_wp_cron_run_jobs was cleared, it was because you were deactivated the plugin, and the next time because you activated it. On activation, it’s intended that it first clear crons before adding them back.

What I was hoping for was that you activate the plugin, and leave things as is (in a working order)… Then, when you notice the cron has been removed (I’m not sure how long that usually happens), we can look again at the log to see what removed it.

Hi @scamrp1ckleballclub – I’m really sorry to hear about the fatal error. I have a few questions I was hoping you could answer.

1. Was this working previously, or is this your first time setting up Total Upkeep? If it was working previously, has anything changed recently?

2. Usually the emails have an error message. Is there more to the email that you can share?

Hi Richard,

Sometimes I can get stuck going down rabbit holes, and lose my direction when troubleshooting. I think our first focus, instead of “Why is my backup not starting?”, is now “Why am I getting permissions related warnings?”.

One of the errors you received is:

file_get_contents(/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/archive-1621495700.log): failed to open stream: No such file or directory

The file that has this error message, is it “archive-1621495700.log”? It seems strange that the file that apparently doesn’t exist, actually exists and includes an error message that it does not exist lol.

—-

Also, both warnings are referring to the “logs-b729045a-5a6f4f0ff6f73145” folder.

/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/archive-1621495700.log
/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/retention-local.log

You did not create “logs-b729045a-5a6f4f0ff6f73145” correct? If not, Total Upkeep created the folder. That means Total Upkeep can create folders but not files?

—-

Can you confirm what the permissions are to that “logs-b729045a-5a6f4f0ff6f73145” folder?

Also, to rule out whether or not this is a permissions issue, can you please:
1. Take note of the current permissions for that folder
2. Change the permissions to 777 and try another backup. Has anything changed?
3. Revert the permission changes

Thanks,
– Brad

Hi @richy66,

I’m sorry to hear about the issue you’re having creating a backup.

The last 2 items in the log you provided are Warnings, not fatal errors, so those errors themselves would not cause the backup process to crash.

Is this the full error log?

If you look at these two lines in the code:

https://github.com/BoldGrid/boldgrid-backup/blob/master/admin/class-boldgrid-backup-admin-core.php#L3064-L3065

$logger->init( 'retention-local.log' );
$logger->add( 'Beginning core::enforce_retention...' );

The first line is trying to initialize the “retention-local.log” log file, and the second line is trying to add a message to the log – but that message is not showing in the log you provided.

At first glance, it does look like a permissions issue. You mentioned Updraft doesn’t restore backups – do you have any error messages from that attempt? I’m curious if both Updraft and Total Upkeep are getting permissions related warnings.

Thanks!
– Brad

Hi @ipapagi, we just released Total Upkeep version 1.14.11. Are you able to upgrade, test, and let us know if the warnings have stopped showing?

Hi @softwaredancer, thanks for taking some time to test the new branch, and I’m sorry it wasn’t working right away for you.

As you stated, the new changes are in javascript. Are you able to clear your cache and test again? I’m pretty sure the new changes should resolve the issue, we just need to make sure the new javascript is being loaded and not the old. IE When you go to yourdomain.com/wp-content\plugins\boldgrid-backup\admin\js\boldgrid-backup-admin-backup-now.js you should see the new js.

The way I tested is that I installed the patch version in a free WordPress testing environment. If you click this link and then click “try it” (no need to sign up), it’ll install a new WordPress site with the branch.issue-445.202102111509 branch of the backup plugin installed. From there, I created a backup on the settings page, and my database was backed up.

Hi @codimex, I’m sorry we’re having some trouble getting this resolved for you, but I might be able to help further. We just released Total Upkeep 1.14.10 and it has additional logging to help with failed “Download links”. I created a video that walks you through the troubleshooting:

Basically, try to use the Download link feature. If it fails, go to Total Upkeep > Tools > logs > and click the transfer-archive.log file to get a more detailed error message.

If you can, please upgrade to 1.14.10 and give it another try, and let us know how it goes.

Thanks!
– Brad

Hi @firefliespilots,

We don’t need all of exec, shell_exec, popen, proc_open, pcntl_exec to be available, just one of them. If Total Upkeep finds one, it uses that.

Are you able to test and let us know if this helps?

Thanks,
– Brad