Luc, the developer is active here and he has answered questions. He also is continually updating the program. He has put it out free and opensource with a donation button that I am sure is used rarely. Lets be easy on this. Opensource depends on an active community doing their part. One observation is that the problem appears to be an issue with REST API but it may not be. I have tried using 4.8 on a clean site and all is well. It does not work on my site and I am not sure why– yet. The REST API issues is not helping me. So, it is a matter of finding the offending plugin, contacting the author, and getting an update in most cases. So, rolling back is a temporary solution to keep your site running until all other plugin’s are up to speed. Then there are also my own functions, I have to scout through those and find where there may be errors that conflict. In the case of my own functions it is my problem not the authors. The fact that my code has worked for years does not mean it is compatible with newer standards. When you find the offending plugin or code, report your solution here for all to know. That makes opensource work better. And, as I understand, part of the reason for 4.8 is to make it more secure, that is a good thing. So, roll back, as a temporary solution and do the hard work of finding the offending plugin or code, get that changed, then update to 4.8. It would be foolish to just stay at 4.7 if a more secure version exists.
-
This reply was modified 7 years, 5 months ago by cravaus.