Fatal error appears, site crashes

Hi @joelmellin,

Thank you for your patience!

I understand that you’re experiencing a fatal error on your site. Let’s get this sorted out.

Upon careful investigation, this can be caused by a couple of reasons:

• The Pixel Manager wasn’t fully installed
• Your server doesn’t load everything properly, which indicates a server-side issue.

With this, I suggest reinstalling the Pixel Manager first.

If that doesn’t work, what’s best is to reach out to your hosting provider and ask them about this.

Let us know how it goes.

Hi,

I have rolled back to the earlier version and that works perfect. So it is your new update that causes the problem. You need to look into how to fix that bug.

Hi @joelmellin,

Thank you for your prompt update, and I appreciate your diligence in addressing the situation. It appears that the issue stemmed from an incomplete installation of the new update, leading to the fatal error you experienced.

With this, there’s most probably some missing files due to the update not being fully installed.

That said, I recommend updating the Pixel Manager once again. This should resolve the issue once the plugin is updated without interruption.

Feel free to reach out if you encounter issues after updating again.

Sorry to say, but it still does not work. I updated it again, but then the problem returns. When a new order is made in the webshop it just shows a white screen instead of the order confirmation page, and I get back the following fatal error code:

2024-01-29T08:56:14+00:00 CRITICAL Uncaught Error: Class ‘WCPM\Classes\Helpers’ not found in /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/wgact.php:545 Stack trace: #0 /home/mellins/public_html/wp-includes/class-wp-hook.php(324): WCPM::declare_woocommerce_compatibilities(”) #1 /home/mellins/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #2 /home/mellins/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /home/mellins/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php(701): do_action(‘before_woocomme…’) #4 /home/mellins/public_html/wp-includes/class-wp-hook.php(324): WooCommerce->init(”) #5 /home/mellins/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #6 /home/mellins/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/mellins/public_html/wp-settings.php(643): do_action(‘init’) #8 /home/mellins/public_html/wp-config.php(95): require_once(‘/home/mellins/p.. i /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/wgact.php p? rad 545

Hi @joelmellin

CRITICAL Uncaught Error: Class ‘WCPM\Classes\Helpers’

This indicates that the file class-helpers.php was not installed, although it is part of the package.

Or it has not been loaded by the autoloader, which has been working fine for a long time. There were no changes recently, and it works fine on tens of thousands of installs.

So, we must assume that the file was not installed properly.

Since you’re the only one reporting this issue, it is clear that something goes wrong during the update process on your server when installing the update of the Pixel Manager.

The Pixel Manager is not in control of the update process. WordPress and the server entirely control that.

The only option you have is to use an FTP client to upload the update to your server. This normally circumvents any issues that happen during the automatic update process.

However, it probably won’t fix the problem longterm.

If the FTP fix works, but you keep experiencing the issue with the next automatic updates, you will have to seek support from your server provider.

Kind regards
Aleksandar

I now tried to upload manually over FTP. However the same problem occur anyway even if the installation was fine. This is the only plugin I have this problem with and it works fine when I roll back. As you can see in the picture the pixel is not firing when I made a test buy. Also a new fatal error happens:

2024-01-29T10:01:45+00:00 CRITICAL Uncaught Error: Class ‘WCPM\Classes\Pixels\Pixel’ not found in /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/pixels/google/class-google.php:17 Stack trace: #0 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/lib/autoload.php(106): include_once() #1 [internal function]: {closure}(‘WCPM\\Classes\\Pi…’) #2 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/pixels/class-pixel-manager.php(70): spl_autoload_call(‘WCPM\\Classes\\Pi…’) #3 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/pixels/class-pixel-manager.php(47): WCPM\Classes\Pixels\Pixel_Manager->__construct() #4 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/wgact.php(397): WCPM\Classes\Pixels\Pixel_Manager::get_instance() #5 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adword i /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/pixels/google/class-google.php p? rad 17

The error shows again that some files can’t be found.

If you did the FTP correctly, which I believe you did, the files must be there.

As I mentioned in my earlier reply, it also could be related to the autoloader.
But again, the autloader did not change for years.
And the files that can’t be found were not removed or added recently (but might have had changes to them, which would not explain the issue).

Another possible issue that comes to my mind is some sort of server-side caching, possibly OP cache that was not deleted after upgrading to the new version.

This would explain why the new version keeps getting errors, but not the previous version (since still the old cache is in place).

1. Try installing the new version. Then delete all server-side cache (OP cache and similar server-side code optimization caches).

Then try the Pixel Manager again.

2. Try installing and testing the Pixel Manager on a different server (locally, or other provider). Make sure to disable any type of Opcode caches. I’m 100% the Pixel Manager will work fine (as it does for ten thousands of other sites).

Bottom line. I’m 99.9% sure that it is some issue with your server. I’m 100% it’s not caused by the Pixel Manager.

Yes the files are there. I just pasted the whole plugin-map with all the files, so no file could be missing.
I have deleted all cache (with WP rocket) after the installation, but that does not help. This problem started to occur with your new version update. I have had this plugin for more than a year without a problem before.

There is no possibility for me to test on another server, I don’t have those resources. If you could not help more I will just stick to the previous version and hope the next update will work, or just stick with the old as long as it works.

I have deleted all cache (with WP rocket) after the installation, but that does not help.

WP Rocket is not Opcache. Please consult with your server provider.

If you could not help more I will just stick to the previous version and hope the next update will work, or just stick with the old as long as it works.

Sorry. I can’t help as it is clear to me that it is not an issue caused by the Pixel Manager. It only surfaces a problem that you have with the server. Testing this on a different server would prove this to you and would help you understand that you have to pick up this issue with your server support.

I will just stick to the previous version and hope the next update will work, or just stick with the old as long as it works.

That might be solution for now. But if I’m right about the server Opcache, you will keep running into the same problem.

Now I have managed to clear OPcache via a PHP-script after having updated your plugin:

To be sure I also used the OPcache-plugin t flush it:

However this did not change anything. This time I got this fatal error:

2024-01-29T14:47:09+00:00 CRITICAL Uncaught Error: Call to undefined function WCPM\Classes\Admin\as_has_scheduled_action() in /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/admin/class-ltv.php:578 Stack trace: #0 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/admin/class-ltv.php(376): WCPM\Classes\Admin\LTV::schedule_complete_vertical_ltv_calculation() #1 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/admin/class-ltv.php(312): WCPM\Classes\Admin\LTV::calculate_pmw_order_values(Object(Automattic\WooCommerce\Admin\Overrides\Order)) #2 /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/wgact.php(232): WCPM\Classes\Admin\LTV::horizontal_ltv_calculation(15095) #3 /home/mellins/public_html/wp-includes/class-wp-hook.php(326): WCPM->{closure}(15095) #4 /home/mellins/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NUL i /home/mellins/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/classes/admin/class-ltv.php p? rad 578

This time it says call to undefined function. This error happened when I wanted to trash a test order. After this I rolled back the plugin again, flushed the OPcache and everthing works just fine again.

Ok. This is a different issue.

Here’s what’s going on:

The Pixel Manager uses the Action Scheduler’s as_has_scheduled_action function, which has been part of the Action Scheduler since version 3.3.0.

The Pixel Manager ships with the Action Scheduler version 3.7.1.

The Action Scheduler is built in a way that loads the latest version if several plugins ship different versions of the Action Scheduler.

However, as I discovered during my investigation, this only works reliably for versions 3.2.1 and onward.

On your website, a plugin with an older version of the Action Scheduler must be present.

Here’s a troubleshooting article from WooCommerce that explains exactly the problem you’re facing: Deconflicting Different Versions of Action Scheduler

I will build a safeguard into the Pixel Manager to prevent the same error from happening when as_has_scheduled_action is called.

You should follow the troubleshooting guide mentioned above, identify the plugin with the old version of the Action Scheduler, and update it (or get the developers to release an update with a newer version of the Action Scheduler).

• This reply was modified 1 year, 1 month ago by alekv.
• This reply was modified 1 year, 1 month ago by alekv.

I created a new beta version with a safeguard that fixes your problem.

Here’s the updated version: download

You’ll have to download the archive and install it manually. Or wait until the next public release.

I checked now using the troubleshooting guide, but I have version 3.7.1:

Have you installed the update?

Do you still get the error?

Now I tried to install the update, and it works.

But I still don’t understand if the action scheduler was the problem or not since I had version 3.7.1.