today, new problem, nothing is saved
Wed, 13/05/2009 - 09:55
I tried accessing my prosepoint site today and I wasn't able to change any of the settings. each time i tried to change a setting or upload a story or perform a backup, it didn't go through. When I would press the "save" or "submit" buttons the page would just reload showing me once again the original settings. Trying to edit a story gives me the same effect. What in the world could be causing this?
Wed, 13/05/2009 - 10:54
#2
ok
I poked around my server's knowledgebase, mediatemple.net, and they had a generalized fix for "php sessions do not work as expected." They advised me to make a custom php.ini file for my account and gave me instructions to do it. So I followed the instructions and everything has been fixed. They said that php variables are usually saved in a global php /var directory but the custom php.ini pointed php to a local /var directory. Problem solved. Incidentally they also gave me instructions on how to increase the php upload limit to 20 megabytes or more. I hope this means I can upload raw 4 megabyte jpgs straight from our cameras now.
Wed, 13/05/2009 - 11:00
#3
Good to know it's fixed and
Good to know it's fixed and it's not a bug I have to chase up in ProsePoint :)
However, your description doesn't explain what happened recently to cause the breakage. Did your hosting provider change their server's configuration and that had unintended side effects or something?
Wed, 13/05/2009 - 12:40
#4
They do have a maintenance
They do have a maintenance notification that they sent out, it was scheduled for yesterday at 2pm my local time. They said they were going to perform server upgrades during that time. I don't remember using the web site yesterday afternoon, only yesterday morning, so it might be the result of their server upgrade. But that's all I can tell you.
Hi,
Very hard to say, but if it was working yesterday, and then not working today, then I would suggest something has changed recently which has broken.
Can you check your PHP error logs?
Maybe even check your web server access logs to see that when you click a button, a page request is actually being made to your web server?