PHP Strict Standards errors and new version problems.

[MetaTunes]

I have been using the old version of Pommo (obtained via Softaculous) for some years, but am not a developer. I recently downloaded the new version to deal with Strict Standards errors arising after my hosting service moved to a new version of PHP. However, there still appear to be some untrapped errors, namely Pommo_Helper::timeToStr() called in classes/Pommo_Subscribers.php and Pommo_Pending::isPending() called in update.php. I have modified these (to add static) in my copy and that seems to work OK. I also notice that, although I kept the same database when migrating to the new version, the admin sign-in no longer works. I can (just about, through the cloud of error messages) sign in using the old version and then switch to the new version. I assume the solution is to create a new admin and delete the old one? Finally, I cannot access the mailing history from the new version - it just hangs. EDIT PS - just tried to add a new user - entered details in pop-up, but it fails to add it.

[MetaTunes]

Further PS. There seem to be quite a few Strict Standards Errors elsewhere too. Eg in the mailing template. I could fix these on my copy, but the more fundamental problem is that the new version does not actually launch the mailer properly. I have had to revert to the old version and am wondering whether I'm better off going back to that and correcting the Strict Standards Errors there. I'm not really happy with that as I will just end up with my own "personal fork". I'd rather stay with the master fork, if someone is looking after that?

[soonick]

Hello @Ncorch,

Thanks for reporting this issue. I have been busy with other projects lately and I'm not actively maintaining this project anymore.

You might find the solution for your login issue here: https://github.com/soonick/poMMo/blob/master/docs/user/troubleshooting.md

There are a lot of Strict Standards Errors all over Pommo codebase. These should be fixed but you should be able to suppress them changing the error logging level in your .htaccess file.

For your mailer issue I really have no ideas of why this would happen. If you want to look into this I would do my best to help you figure it out.

Regards, Adrian