Thats interesting, I've just posted a similar issue a couple of days ago, thought it was my multi server setup that was the causing it.
What version of PHP are you using and have you made any changes to the php.ini file? The only change I made (can't remember whether it was enabled or not by default), was to enable the curl extension.
This is a fresh machine to my understanding and I haven't made any changes to the php.ini. I haven't had to do anything like that in a long while. I will see if curl is enabled but it usually is when I check the info on it. I don't know what else to check and I don't see anything else online that would elude to this particular problem.
I always feel like when I post questions on here are they too trivial to answer or is no one else running into this? This is very frustrating.
nothing is trivial on this list! but you could be correct that:
1) no one is running into this
2) no one knows how to fix it
3) those who know just have not seen your question.
this was TSGal's answer on the other thread by ajk:
1 of 1 people found this helpful
I could see the error.
The result is array, so you can't echo it. Use print_r($array) instead.
It seems default setting of IIS/php is a bit hard to debug.
Thank you for your posts.
This is nearly identical to the other recent post by Community member "ajk".
Although there is no update from that report, I have also attached your posts to that report. When I receive any feedback from either Development or Testing, I will let you know.
Testing would like to know if you are able to get the PHP test page to render.
Using the other customer's file, Development was able to replicate the issue but have a solution.
Open the php.ini file under ...\Web Publishing\publishing-engine\php
error_reporting = E_ALL & ~E_DEPRECATED
error_reporting = E_ALL & E_DEPRECATED
That is, remove the "~" in front of "E_DEPRECATED".
Wait a little bit after saving or restart the (virtual) machine. You should get a proper return from:
Let me know if this works.
I can't believe this "solution" comes from who know what does "~" mean, whether it works or not...
& ~ is a bitwise operator that does and not, so & ~E_DEPRECATED turns off the debrecated warnings no matter what the previous setting is. Removing the ~ should essentially enable php debrecated warnings.
If need to enable E_DEPRECATED, the operator should be changed to "OR", keep it "AND" doesn't make sense.
I agree with user19752's opinion.
"error_reporting = E_ALL & E_DEPRECATED" means "error_reporting = E_DEPRECATED".
Where is other error_reporting level?
TSGal's workaround is not suitable for server operation.
I didn't see this till now. I did get the value lists working by putting the following at the top of my PHP Web Page:
Everything is working on both the Mac and PC platforms.
Thank you for your input.