Plugin Author
alekv
(@alekv)
Hi @andersi913
We introduced an optimization into the Pixel Manager, which makes it load faster that uses the Composer function setApcuPrefix.
This function was introduced into Composer six years ago.
In your install, one of your other plugins is loaded before the Pixel Manager, and it is using a Composer version older than six years! This is why the function setApcuPrefix can’t be called and causes a fatal error.
The simplest solution would be to update that plugin which uses that ancient Composer ClassLoader.php
I will also look into finding a workaround for this.
Please try updating all plugins and retry using version 1.30.0 of the Pixel Manager. Then, let us know if that fixed it.
If you want I can give you instructions on finding the plugin that causes the problem.
Kind regards
Aleksandar
-
This reply was modified 3 years, 4 months ago by
alekv.
-
This reply was modified 3 years, 4 months ago by
alekv.
Hi Aleksandar
That does not sound to bad I am struggling to figure out which plugin that could be so yes if you would please instruct me.. 🙂
I dont feel like I have any ancient plugins installed and I had all plugins updated yesterday. :/
Kind regards
Anders
Plugin Author
alekv
(@alekv)
I dont feel like I have any ancient plugins installed and I had all plugins updated yesterday. :/
It just requires a plugin that hasn’t updated its Composer files for over six years, even if other parts of the plugin were updated.
And it could also be the theme.
Method 1:
Update the Pixel Manager to version 1.30.0
Disable one plugin after the other, and each time test to see if the error still occurs. Once the error goes away, the last plugin you disabled is the one causing the issue.
Method 2:
Go to each plugin’s /vendor/composer/ directory.
Open the ClassLoader.php file.
Search for the string setApcuPrefix.
If you can’t find the string, then that is the plugin/theme causing the issue.
Plugin Author
alekv
(@alekv)
@andersi913
I created a version with a workaround for this issue.
Here’s a beta version that contains the workaround: downlaod
Please try it out and let me know if this fixes it.
@alekv I have the exact same problem.
*EDIT* The beta version has fixed the issue for me.
-
This reply was modified 3 years, 4 months ago by
AlanM04.
Plugin Author
alekv
(@alekv)
@alanm04 Could you download and install the beta with the workaround and let me know if that works: download
-
This reply was modified 3 years, 4 months ago by
alekv.
Hi @alekv, yes the beta version has worked for me.
@alekv Will this change be included in the next offical update release or will we have the same problem again when it next updates? Thanks
Plugin Author
alekv
(@alekv)
@alanm04 Yes, I’ll include the workaround in the next release.
Hi @alekv
I looked through all my plugins as you mentioned in method 2 in you first workaround answer. And I did not find any issues.
Sounds good I will try the beta version tomorrow night when I have low traffic on the website. 🙂
I will tell you how it works.
Thank you for the quick response.. 🙂
The beta version did not work for me..
I tried it but it made all images disappear from my website visually/at-the-frontend as a visitor but worked fine when moved around on the site as a admin. 🙂
Not sure what that is caused by.
Kind regards.
Plugin Author
alekv
(@alekv)
@andersi913 Please take a look at the error log. And if you find anything related to the Pixel Manager after you installed the beta, post it here for analysis.
Plugin Author
alekv
(@alekv)
@andersi913 Btw. That error doesn’t sound like it’s caused by the Pixel Manager, because there was no recent change in logic that differentiates between admin and front-end output.
Plugin Author
alekv
(@alekv)
@andersi913 and @alanm04
I’ve released version 1.30.1 which contains the workaround for the setApcuPrefix function. The fatal errors should be gone.