Hi,
I tried today to unpublish two albums. I get the same result if I use the bulk action or tick them in the album properties, but when I apply the browser returns a blank white screen. If I reload the page I get put back tot he Albums tab with the following in a red banner:
"savealbumorder' Cross Site Request Forgery blocked.
Never seen that before and baffled by the message?
All other album functions work fine. I have only noticed this since the recent upgrade.
Regards
Deljones
Comments
Im a photographer first and formost with plenty of computer experience but by no means an expert hence the request for help. If I knew what I was doing then I would not be here...:)
Im not aware of making any changes to authentication. My log in details have been the same for ZenPhoto and for my database ever since I started using ZenPhoto. It might be more useful if you coud help me what and when I made these changes. The only thing I have done with ZenPhoto recently is to do the recent upgrade which went without any problems at all. Good work guys... Everything is working as I expect apart from this error when I tried to unpublish an album today.
As for php server error logs I have no idea where to obtain this. Im sorry, as i say I take and distribute photos. My system is a Qnap NAS with phpMyAdmin. Im guessing I will find the error log there somewhere? or will it be in the Zenphoto tree?
I would be grateful if you could help me some more information as Im not sure how I may have caused this error.
Best wishes
Deljones
If you are running some kind of server you need to find out where the server logs are. No, they are not in the Zenphoto tree and we cannot answer where it is. That is different on every server/host, those are actually just text files.
Some hosts have them in a directory above and outside the web root (on my local MAMP server they above the root in a folder named /logs so maybe search for such a folder), some give only access via their backend. I have neither experience with a Qnap NAS nor do I exactly know what that is for. So you probably need to contact its vendor or refer to the manual to find those logs.
Once cause might be file/folder permissions but as said without that error log all is basically guessing.
Thanks.. I will go for a look
D
Reloading the page after an error would be a possible cause of the above, so I guess you will have to find the error logs to see what is the problem.
Sorry for mistaking you for the user who was changing the authintication handling. I see so many user ids that they tend to blend together. But as you can see, such a change would be suspect.