When I configure Google maps and save the configuration the modules folder and all the contents becomes inaccessible. I did as I was told and changed the permissions to 777. I then went back to gedview and changed the configuration with the key etc. On return to change the permissions back to 644 the module cannot be seen by Filezilla. Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-11-07
The recommended permissions according to the WIKI ( [ )
is 777 for the /modules folder and sub-folders; and 666 for the files if using Apache, or 711 and 644 if using CGI. See if that helps.
Otherwise, it may be a permissions vs ownership issue. For that you'll have to talk to your web host / server management.
Thanks Kiwi_pgv. trouble is that having set permissions to 777 i then go back to the PGVGEDVIEW and enter the Google key etc. Then I return to the files and am denied pemission. Filezilla can see them but denies their existence. Back in PGVGEDVIEW admin the Googlemap config is also not their. The PGVWiki that I have says set module and contents to 777. There are over 1200 files in the modules directory and to change them differently from the directory would take forever.
I have restored the Module directory three times now and all goes well till I configure Googlemaps in the gedview. It then disappears each time.
John H
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
John… that is odd behavior by the googlemaps config software. If I were in your shoes my first step would be to download a fresh copy from sourceforge and upload the fresh copy to your server. If you haven't done that already it's a quick and painless thing to try.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all. I uploaded the googlemap module. Total disaster. So I rolled my sleeves up and climbed into the files via my server. I restored the original Modules folder and set the permissions to 775 (the highest my server would allow) and started again in PHPGEDVIEW. All went well until I reset the permissions to 644 as told to do so on page 4 of the wiki. It all went pearshaped again and I couldn't access the configure googlemaps to put in the place locations. Sleeves rolled up again and reset permissions to 775 and LO! it's all there again. I think the instruction to reset the permissions to 644 shouldn't be on page 4, but much later. I have no idea why filezilla couldn't read the module.
I've set a few placenames and I'll come back later if it all works.
John H
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I generally recommend that file and directory permissions be set to 755 - this seems to work best.
Of course, the "/index" and "/media" directories, and all their contents, need 777. That's why we recommend that the "index" directory be relocated to be outside the web-addressable file space on the server, and that the media firewall be enabled so that media files can also reside outside the web-addressable file space.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What works best may depend on server settings.
Many webservers run with the UID of an account dedicated to the webserver. But some run with the UID of the account that owns the files.
Anyway, if you have command line access, and the server is Unix or close, one way to give directories a different setting than files is
> cd <directory>
> find . -type f -exec chmod 644 "{}" \;
> find . -type d -exec chmod 755 "{}" \;
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I configure Google maps and save the configuration the modules folder and all the contents becomes inaccessible. I did as I was told and changed the permissions to 777. I then went back to gedview and changed the configuration with the key etc. On return to change the permissions back to 644 the module cannot be seen by Filezilla. Any ideas?
The recommended permissions according to the WIKI ( [ )
is 777 for the /modules folder and sub-folders; and 666 for the files if using Apache, or 711 and 644 if using CGI. See if that helps.
Otherwise, it may be a permissions vs ownership issue. For that you'll have to talk to your web host / server management.
: http://wiki.phpgedview.net/en/index.php?title=Setting_File_Permissions](http://en.wikipedia.org/wiki/Special:Search?search=LINK)
Thanks Kiwi_pgv. trouble is that having set permissions to 777 i then go back to the PGVGEDVIEW and enter the Google key etc. Then I return to the files and am denied pemission. Filezilla can see them but denies their existence. Back in PGVGEDVIEW admin the Googlemap config is also not their. The PGVWiki that I have says set module and contents to 777. There are over 1200 files in the modules directory and to change them differently from the directory would take forever.
I have restored the Module directory three times now and all goes well till I configure Googlemaps in the gedview. It then disappears each time.
John H
John… that is odd behavior by the googlemaps config software. If I were in your shoes my first step would be to download a fresh copy from sourceforge and upload the fresh copy to your server. If you haven't done that already it's a quick and painless thing to try.
Thanks vhhawk, I'll give it a go. The Googlemap files I have came with my upgrade to PGV4.2. I will do as you say and see what happens.
Regards & thanks.
Hi all. I uploaded the googlemap module. Total disaster. So I rolled my sleeves up and climbed into the files via my server. I restored the original Modules folder and set the permissions to 775 (the highest my server would allow) and started again in PHPGEDVIEW. All went well until I reset the permissions to 644 as told to do so on page 4 of the wiki. It all went pearshaped again and I couldn't access the configure googlemaps to put in the place locations. Sleeves rolled up again and reset permissions to 775 and LO! it's all there again. I think the instruction to reset the permissions to 644 shouldn't be on page 4, but much later. I have no idea why filezilla couldn't read the module.
I've set a few placenames and I'll come back later if it all works.
John H
It works…it works. Thanks everyone.
Regards and good celebrations this Christmas.
John H
I'm glad that things are now working for you.
I generally recommend that file and directory permissions be set to 755 - this seems to work best.
Of course, the "/index" and "/media" directories, and all their contents, need 777. That's why we recommend that the "index" directory be relocated to be outside the web-addressable file space on the server, and that the media firewall be enabled so that media files can also reside outside the web-addressable file space.
What works best may depend on server settings.
Many webservers run with the UID of an account dedicated to the webserver. But some run with the UID of the account that owns the files.
Anyway, if you have command line access, and the server is Unix or close, one way to give directories a different setting than files is
> cd <directory>
> find . -type f -exec chmod 644 "{}" \;
> find . -type d -exec chmod 755 "{}" \;