Ticinoforum wrote: ↑
Tue Jan 21, 2020 9:22 pm
Naguissa wrote: ↑
Tue Jan 21, 2020 6:24 pm
In your case, update was performed without disabling extension, right?
A major update has important changes and maybe they affect to this plugin, if not disabled.
Yes, I confirm...first time did not "disable" my extension!
But in second test, 3.2.8->3.2.9->3.3.0 I made "as per manual"!
So, I think that if you have spare time to checks difference between core files on 3.2.9 amd 3.3.0, maybe you understand better the "notify data" problem.
This because, I confirm again, with 3.2.9 all works fine with current master version of your ext.
No, I updated old local copy (probably 3.2.8, but maybe earlier) to 3.3.0 disabling all extensions and I had no problems.
It was performed in a linux system, so it's worse tolerating capitals, and even so it was performed flawlessly (leaving aside services.yml and empty notifications).
I have to test it on a Windows 10 (cheap chinese) tablet and a portable server, but I expect far less problems on that machine, as it doesn't distinct between leter cases.
I suspect about db migrations between 3.2.x and 3.3.x when extensions are not disabled. But that doesn't fit to phpbb migration rules...
But still, it doesn't solve the "empty notifications problem".
I have a fix idea: as notifications are called twice, one with data and other without, I can create a static object to store data and try use it on 2nd call. But I need some spare time, I will take it from wherever I can....