× Joomla Facebook Connect support forum

Topic-icon Could not install the SourceCoast Social LIbrary

Active Subscriptions:

None
11 years 11 months ago #23539 by jefvs
Hey SCer's,
I was just upgrading my JFBC and after trying to install it a few times (just having to change directory permissions etc and repeat) I've got everything to install just fine except the SourceCoast Social Library.

Could anyone point me in the direction of where the SourceCoast Social Library is installed to so I can set the permissions and allow it to create the folder or so I can put the file in manually?

Thanks!
J

PS. It may be solved in 4.2 (I haven't been able to check yet) but in 4.0, it said that I didn't have community builder installed but in fact I did. Does something need to be enabled or do I need the JFBC CB Plugin in order for it to actually detect CB?
The topic has been locked.
Support Specialist
11 years 11 months ago #23543 by alzander
J,
Hopefully the CB issue is fixed. I honestly don't recall that being a problem in 4.0, but that's not an issue we've heard of at all in the last 6 months that I can think of. If you do have issues with it, let us know.

As for the SourceCoast Library, it's installed into the /libraries/sourcecoast directory (creating the /sourcecoast part). The /libraries folder is a root folder of Joomla and definitely should already be there.

Hope that helps!
Alex
The topic has been locked.
Active Subscriptions:

None
11 years 10 months ago #24642 by czyky
FYI, I downloaded and started a new install today and the directory rights were an issue. Got similar errors about unable to create directory and/or copy files for the Authentication and Social Library. The directories in question were 755s (rights) and setting them to 777 made everything okay. This particular joomla setup was installed by cPanel, so I don't know who (cPanel or joomla install) was responsible for the directory creation, but looking at the joomla install, most directories have 777 rights, but some are 755, which caused errors for the jfbconnect install. Now, I am wondering if I should change the directories in question back to 755 after the installation and testing. Anybody have an idea if I can just leave them 777, or am I courting evildoers? :-!
The topic has been locked.
Support Specialist
11 years 10 months ago #24654 by alzander
777 is generally discouraged. While it *can* be ok, it's almost always safer to go with 755. The reason is that, if you are on a shared server from your host, if another site is hacked on that server (unrelated to yours), a perpetrator could *possibly* access and modify your files if they are set to 777. That last 7 means 'anyone with access to the server can write to the file'. If you have a dedicated server where it's only your sites, 777 is generally ok.. but I'll never say 'go for it'. You'd need to know your setup and understand the risks more fully.

With that said, going back to 755 shouldn't be a problem. Once the files are written, they shouldn't need to be modified again (until you need to update). Directories like /tmp, /log, /cache, and /image may need to be 777 so that normal file writing can occur there, but the /components, /libraries, etc directories (generally) shouldn't be written to through normal operation of your site... hence, 755 is a good recommendation for directories and 644 is good for files.

Hope that helps explain a very difficult subject to grasp!
Alex
The topic has been locked.