The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Hi,
I run a PHP Photo Gallery on my website - and recently have noticed that the gallery has stopped working (with no changes made by me). I contacted the author of this code, and he told me:
--------------------------------------------------
"Why do I get this error: Warning: fopen(".../albums/team/album.dat.lock","a+")?
This typically happens when your ISP makes a change in your environment (like upgrading PHP or moving things around) without telling you about it. In a nutshell, some of Gallery's files wind up being owned by the wrong user and their permissions become set such that Gallery can no longer write to them. I've never found this to be the result of a bug in Gallery. To fix this, you can change the permissions on your Gallery data files so that Apache can read the files again. This should only happen on Unix. If you have shell access, you can fix it like this:
% cd /path/to/albums
% cd ..
% chmod -R 777 *
If you don't have shell access, you will probably need to ask your ISP for help. "
--------------------------------------------------
Since I don't have shell access, you guys think Freeola would be kind enough to do the following unix shell commands for me?:
% cd /freeola/users/9/0/sr0191709/htdocs/albums
% cd ..
% chmod -R 777 *
Best Regards - Anjum
I run a PHP Photo Gallery on my website - and recently have noticed that the gallery has stopped working (with no changes made by me). I contacted the author of this code, and he told me:
--------------------------------------------------
"Why do I get this error: Warning: fopen(".../albums/team/album.dat.lock","a+")?
This typically happens when your ISP makes a change in your environment (like upgrading PHP or moving things around) without telling you about it. In a nutshell, some of Gallery's files wind up being owned by the wrong user and their permissions become set such that Gallery can no longer write to them. I've never found this to be the result of a bug in Gallery. To fix this, you can change the permissions on your Gallery data files so that Apache can read the files again. This should only happen on Unix. If you have shell access, you can fix it like this:
% cd /path/to/albums
% cd ..
% chmod -R 777 *
If you don't have shell access, you will probably need to ask your ISP for help. "
--------------------------------------------------
Since I don't have shell access, you guys think Freeola would be kind enough to do the following unix shell commands for me?:
% cd /freeola/users/9/0/sr0191709/htdocs/albums
% cd ..
% chmod -R 777 *
Best Regards - Anjum
You don't need a shell to do that. Just put the following code into a .php file then navigate to it (unless you don't actually own the files any more, which would be extremely odd)
--------------------
$exec = "chmod -R 777 /freeola/users/9/0/sr0191709/htdocs/*";
echo "Executing command \"$exec\", output:
";
echo `$exec`;
?>
--------------------
That should do the trick.
--------------------
$exec = "chmod -R 777 /freeola/users/9/0/sr0191709/htdocs/*";
echo "Executing command \"$exec\", output:
";
echo `$exec`;
?>
--------------------
That should do the trick.
Hi,
I run a PHP Photo Gallery on my website - and recently have noticed that the gallery has stopped working (with no changes made by me). I contacted the author of this code, and he told me:
--------------------------------------------------
"Why do I get this error: Warning: fopen(".../albums/team/album.dat.lock","a+")?
This typically happens when your ISP makes a change in your environment (like upgrading PHP or moving things around) without telling you about it. In a nutshell, some of Gallery's files wind up being owned by the wrong user and their permissions become set such that Gallery can no longer write to them. I've never found this to be the result of a bug in Gallery. To fix this, you can change the permissions on your Gallery data files so that Apache can read the files again. This should only happen on Unix. If you have shell access, you can fix it like this:
% cd /path/to/albums
% cd ..
% chmod -R 777 *
If you don't have shell access, you will probably need to ask your ISP for help. "
--------------------------------------------------
Since I don't have shell access, you guys think Freeola would be kind enough to do the following unix shell commands for me?:
% cd /freeola/users/9/0/sr0191709/htdocs/albums
% cd ..
% chmod -R 777 *
Best Regards - Anjum
I run a PHP Photo Gallery on my website - and recently have noticed that the gallery has stopped working (with no changes made by me). I contacted the author of this code, and he told me:
--------------------------------------------------
"Why do I get this error: Warning: fopen(".../albums/team/album.dat.lock","a+")?
This typically happens when your ISP makes a change in your environment (like upgrading PHP or moving things around) without telling you about it. In a nutshell, some of Gallery's files wind up being owned by the wrong user and their permissions become set such that Gallery can no longer write to them. I've never found this to be the result of a bug in Gallery. To fix this, you can change the permissions on your Gallery data files so that Apache can read the files again. This should only happen on Unix. If you have shell access, you can fix it like this:
% cd /path/to/albums
% cd ..
% chmod -R 777 *
If you don't have shell access, you will probably need to ask your ISP for help. "
--------------------------------------------------
Since I don't have shell access, you guys think Freeola would be kind enough to do the following unix shell commands for me?:
% cd /freeola/users/9/0/sr0191709/htdocs/albums
% cd ..
% chmod -R 777 *
Best Regards - Anjum