This is the same update, to my knowledge. The update to PHP 7 from a few months ago still works and we are referring people to carry out that update that are still noting problems now. Are you referring to a different PHP update? If you can point me to what you're referring to, I'll look into it.
I did point to it above. That was how this thread restarted. The problem was "resolved" a few months ago (not really resolved but an employee did it manually as a kindness; I didn't ask). Then it started up again, hence my post. You responded to my post by telling me to manually update PHP. I'm not making this stuff up.
My post was Wed Jun 03, 2020 2:41 pm
Your reply was Wed Jun 10, 2020 4:55 pm
Plus here you are threatening us that our Wordpress installs may stop working altogether.
It was never my intent to imply that with anything I wrote. What did I say that made you think that? I specifically noted that the reason why we require this manual step is to prevent old Wordpress sites from stopping working.
"The alternative is that older wordpress installs might fail to work as we update the "default".
by kbenson » Sat Jun 13, 2020 12:00 am
Unless the context is otherwise, my use of "you" is plural and refers to Sonic staff.
That said, in a reply to you regarding this issue in early March, williamt noted:
I updated our oneclick installer today to install the newest version of wordpress. It also upgrades installs running older versions of wordpress to the newest version and updates their install to run php7 instead php5.x.
Did you try this?
Did you see my post from June 3rd in this thread? It includes a screenshot that makes it very clear that your claim that this has been fixed for months is untrue. As does your very own post on June 10th that tells us to do a manual install.
It sounds like what you're asking for, but given your recent comments, I assumed it didn't work for some reason, or you are unable to use it because of the circumstances of your sites. If it failed for some reason, we would like to know what happens, perhaps we can fix the problem to make it work correctly.
I was pretty clear on June 3rd as I posted a screenshot of the error message. As for "what happened," I can't tell you, as I have no access to the back end like you do.
That said, someone has made some changes in the last couple of days. I just now checked two of my sites again so I could provide you with current screenshots and they have updated. So thank you to whoever did that.
But please stop trying to convince me that there was no problem. Do you think I saved an old screenshot and just pretended it came from June 3rd? Obviously there was an actual problem on that date. If it's resolved for good, hallelujah! But your responses are really off the mark. A simple "thank you for your report, we have now made the change so your sites will upgrade" would have been perfect.