adammcbeth

Thanks so much for your replies @carolm29 & @serafinnyc.

I was able to figure out what the problem was. We use SendGrid as our email sending service for WooCommerce automated emails: Invoices, Order Confirmation, etc. When we set up SendGrid, we accepted the “Click Tracking” feature that apparently would track clicking behavior on the links in those automated emails. Not sure on the mechanics of it all, but it seems SendGrid was substituting URLS like the ones exampled above in order to track the clicking behavior. Inadvertently, the links they were creating were completely broken and don’t work. As soon as I turned that tracking feature off from the SendGrid backend, everything went back to normal.

I thank you again for your responses! I have no formal education on many aspects of WooCommerce/WordPress so it is always nice knowing there are people who will do what they can to help others.

Here’s the message I received when I went to do a restore:

“The backup archive files have been processed, but with some warnings. If all is well, then now press Restore again to proceed. Otherwise, cancel and correct any problems first.

Warnings:

This database backup has the following non-core WordPress database tables excluded: page_fake_url, ssl_commentmeta, ssl_comments, ssl_links, ssl_options, ssl_postmeta, ssl_posts, ssl_term_relationships, ssl_term_taxonomy, ssl_termmeta, ssl_terms, ssl_usermeta, ssl_users”

Alrighty, I changed a few things in here to generic names, and have included the logs dating back to the first of August (there’s been upwards of 20 backups run in that timeframe) I hope this helps! Thanks!

https://pastebin.com/mkzuSy8v

Good news, I did find the error log for that website in my directory. Are there any security concerns with publishing it here?

Thanks so much

Hey @vupdraft

I’m afraid we’re getting outside of my technical prowess. I’m not sure where my php error logs would be. I’m just not able to execute these steps of troubleshooting. Are there steps potentially? Or am I out of luck?

Thanks so much for the help

Thanks for the response! The resulting file was too large for pastebin so I put it onto Google Drive. I am also unfamiliar with changing permission levels so I couldn’t perform that step? If you have any insight on how to performa that I’d be happy! Otherwise attached is a log of the back up in debug mode.

https://drive.google.com/file/d/1XqAahSoMQda_-7aG0Op_3THDfFhdGBa9/view?usp=drive_link

Just tried reducing the file split to 25mb and it had no effect on erasing the previous backup!

https://pastebin.com/eWRgbpCh

Hey @vupdraft

Here’s the Curl info:

Current SQL Mode: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTIONCurl

version:8.3.0 / SSL: OpenSSL/1.1.1w / libz: 1.2.7

No warnings in site health, just advising on plug in updates (not Updraft) and caching and an inactive theme

Hey @vupdraft,

I’ve deleted the plug in and redownloaded the plug in from the /wp-admin/plugin-install.php twice, and then just downloaded it again straight from the repository. I’ll paste the log here, but it didn’t seem to have an effect. I still see 0158.637 (0) Dropbox: deletion failed

I’ve been wiping the settings, deleting the plug in, and then redownloading for clarification

https://pastebin.com/8xQYTvez

Thanks for any input

Hey there, yes! Thanks so much for the quick reply!

https://pastebin.com/DS0DY9Fq

That looks to be what the issue was. I sincerely appreciate the help!

Thank you very much!

Thanks so much for the response! The plugin is set to back to 1.4.5 right now, when trying to update to 1.4.6 this is what I got:

An error of type E_ERROR was caused in line 75 of the file /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/admin/managers/class-global-font-setting-manager.php. Error message: Uncaught Error: Call to undefined method WP_Table_Builder\Inc\Admin\Views\Builder\Table_Element\Table_Setting_Element::add_settings_section() in /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/admin/managers/class-global-font-setting-manager.php:75

Stack trace:

#0 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/admin/managers/class-global-font-setting-manager.php(23): WP_Table_Builder_Pro\Inc\Admin\Managers\Global_Font_Setting_Manager->manager_controls()

#1 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder/inc/common/traits/class-init-once.php(39): WP_Table_Builder_Pro\Inc\Admin\Managers\Global_Font_Setting_Manager::init_process()

#2 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/core/class-init.php(113): WP_Table_Builder_Pro\Inc\Admin\Managers\Global_Font_Setting_Manager::init()

#3 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/core/class-init.php(76): WP_Table_Builder_Pro\Inc\Core\Init->load_dependencies()

#4 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/wp-table-builder-pro.php(136): WP_Table_Builder_Pro\Inc\Core\Init->__construct()

#5 /home2/thebeto2/public_html/fountains2go/wp-includes/class-wp-hook.php(308): WP_Table_Builder_Pro\WP_Table_Builder_Pro::WP_Table_Builder_Pro\{closure}('')

#6 /home2/thebeto2/public_html/fountains2go/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)

#7 /home2/thebeto2/public_html/fountains2go/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

#8 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/admin/managers/class-freemius-manager.php(64): do_action('wptb_pro_loaded')

#9 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/inc/admin/managers/class-freemius-manager.php(22): WP_Table_Builder_Pro\Inc\Admin\Managers\Freemius_Manager::wptb_pro_init()

#10 /home2/thebeto2/public_html/fountains2go/wp-content/plugins/wp-table-builder-pro/wp-table-builder-pro.php(141): WP_Table_Builder_Pro\Inc\Admin\Managers\Freemius_Manager::init()

#11 /home2/thebeto2/public_html/fountains2go/wp-includes/class-wp-hook.php(308): WP_Table_Builder_Pro\WP_Table_Builder_Pro::init('')

#12 /home2/thebeto2/public_html/fountains2go/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

#13 /home2/thebeto2/public_html/fountains2go/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

#14 /home2/thebeto2/public_html/fountains2go/wp-settings.php(480): do_action('plugins_loaded')

#15 /home2/thebeto2/public_html/fountains2go/wp-config.php(100): require_once('/home2/thebeto2...')

#16 /home2/thebeto2/public_html/fountains2go/wp-load.php(50): require_once('/home2/thebeto2...')

#17 /home2/thebeto2/public_html/fountains2go/wp-admin/admin.php(34): require_once('/home2/thebeto2...')

#18 /home2/thebeto2/public_html/fountains2go/wp-admin/update-core.php(10): require_once('/home2/thebeto2...')

#19 {main}

  thrown

Awesome, thank you very much!

Did a little further checking and when using an android there was no display issue. Seems to be an issue for iOS.