Hi @charlesgodwin,
Sorry to hear this. Unfortunately we were forced to namespace the PHPSpreadsheet library to our own namespace; to avoid collisions with other plugins that use the same dependency. It is therefor not advised to use underlaying packages of the plugin.
In order to avoid breaking changes for customers who use the old namespaces, we create aliases for the old namespace to the new one. It is possible this is interfering with your plugin.
Could you test if removing the creation of these aliases fixes your problem? (it can be removed from the main GravityExport Lite plugin file).
If that works, please let me know; I can make these aliases optional.
We do check if the classes can be aliased; which probably means our plugin is loaded before the other one.
So, maybe you can change the order of which they are included?
In any case, if you have influence on the CBX plugin, that should probably also scope PHPSpreadsheet into their own name space. The problem that can arise, and has arisen, is that multiple versions of the same library are active. And those can conflict with each other. Therefor a custom namespace is best to avoid those collisions.
thanks for the advice. It may be a couple of days before I can test your suggestions but I will let you know
I was able to test.
First, I ensured I had latest version of CBX plugin.
Then I made a one change in GravityExport Lite.
before
gfexcel.php:64: $is_build = true;
after
gfexcel.php:64: $is_build = false;
My plugins now work as before.
I also tested GravityExport Lite and it too works.
Thank you. I can’t advise a permanent fix, but this will do for now and we’ll make sure GravityExport Lite plug in is not autoupdate.