Hi Ally,
well, on my TestBoard all the Plugins from me are also installed but I additionally installed the Social Like Plugin from Fragz and tested again.
I was still not able to reproduce that error, everything still worked fine.
I just added now "preventive" an additional Check if the Plugin Class was loaded correctly before accessing it in all the hooks for the Header.
Like I said this could normally never be the case because the Class-Init is the first thing the forum is doing.
But if a scenario like yours happen - however it happened on your board - the Plugin should be able to catch that error.
So I uploaded Version 1.0.1 now. I suggest if you install it to remove the v1.0.0 first completely, clear your board cache and reinstall the plugin completely new in case something like a missing read/write Permission or a stuck cache file was the cause in your forum why this error occured. Because I still don't know why you got that error, I couldn't recreate it under any circumstances in my test environment. But I hope the preventive code in the plugin now will stop that from ever happening again in your forum.
Sincerely,
Chris
@All
Ich habe im ersten Post dieses Threads die Version 1.0.1 hochgeladen. Diese enthält lediglich einen präventiven Code um noch einmal zu prüfen, ob die Plugin Klasse geladen wurde oder nicht. Bei Ally gab es im Forum so einen Fehler der aber nicht reproduziert werden konnte. Ist also ein optionales Update. Mit CF4.1 oder höher könnt Ihr das Plugin "drüberinstallieren", aber ich empfehle zunächst zu deinstallieren und ganz neu zu installieren falls Ihr das wollt und nach Neuinstallation oder Update kurz noch den Cache vom Forum löschen (ACP Startseite => Cache leeren).
well, on my TestBoard all the Plugins from me are also installed but I additionally installed the Social Like Plugin from Fragz and tested again.
I was still not able to reproduce that error, everything still worked fine.
I just added now "preventive" an additional Check if the Plugin Class was loaded correctly before accessing it in all the hooks for the Header.
Like I said this could normally never be the case because the Class-Init is the first thing the forum is doing.
But if a scenario like yours happen - however it happened on your board - the Plugin should be able to catch that error.
So I uploaded Version 1.0.1 now. I suggest if you install it to remove the v1.0.0 first completely, clear your board cache and reinstall the plugin completely new in case something like a missing read/write Permission or a stuck cache file was the cause in your forum why this error occured. Because I still don't know why you got that error, I couldn't recreate it under any circumstances in my test environment. But I hope the preventive code in the plugin now will stop that from ever happening again in your forum.
Sincerely,
Chris
@All
Ich habe im ersten Post dieses Threads die Version 1.0.1 hochgeladen. Diese enthält lediglich einen präventiven Code um noch einmal zu prüfen, ob die Plugin Klasse geladen wurde oder nicht. Bei Ally gab es im Forum so einen Fehler der aber nicht reproduziert werden konnte. Ist also ein optionales Update. Mit CF4.1 oder höher könnt Ihr das Plugin "drüberinstallieren", aber ich empfehle zunächst zu deinstallieren und ganz neu zu installieren falls Ihr das wollt und nach Neuinstallation oder Update kurz noch den Cache vom Forum löschen (ACP Startseite => Cache leeren).
