Help! Cannot re-install...

[belindab]

Hi. Bad problem. Tried to update to the latest SVN, but my FTP program cannot update the files, it always fails (previously I have always done a new install). Assume it is something to do with ownership. Not to worry, did a backup of everything yesterday, so will do a re-install instead.
So then I created the zip file, uninstalled and went to do a new install. Error message
/media/install_4746dcff6af34/fabrik_connection.class.php does not exist!
Now there is no fabrik component. Tried recreating the zip in case it was my error, now the directory is in use. Deleted the fabrik directory, tried installing from previous known good zip file. Same problem!
Ouch!!!!
Later: Have now managed to get a new installation by doing everything again, but now there are no tables, no forms, no groups, no elements .... I thought that the database was unaffected by uninstall/re-install, so what has happened? I would like some advice before I go any further.....
Belinda

 

[cheesegrits]

Uninstalling Fabrik uninstalls everything. We do warn about this on a regular basis, and this is why it says in the SVN instructions:

"If you are upgrading an existing Fabrik install DO NOT use the Joomla installer."

When did you last back your Joomla database up? Assuming you have a recent backup, you can just restore all your Fabrik tables from that. If not ... :-(

-- hugh

 

[belindab]

Hi Hugh,
I had backed up my database the evening before and I have now successfully restored the fabrik tables using PhpMyAdmin (didn't need to do the formdata ones, as they were still there) and all is ok. Does re-inforce the message that it is always worth taking a backup before making changes ;D

A side issue to this (why I got myself into this pickle) is that FTP will not allow me to upload the new SVN files. I can upload single files from within JoomlaXplorer ok, but that's tedious. Is there a way that I can upload a whole directory?

I did appreciate your timely response on this holiday weekend and all those cups of coffee. :-*
Hope you enjoyed the break.
Belinda

 

[cheesegrits]

*phew*

I'm very glad you had a backup. And yes, it does re-inforce the need for regular backups.

Your issue with FTP is because of the way Joomla installs extensions, which is via the web service (usually Apache httpd). Which means everything has to be created being owned by the user/group that httpd runs as (typically 'nobody' or 'apache'). This is why you can upload files using JoomlaExplorer, because that's running as an httpd process. But when you log in as yourself on ftp, you don't have permissions to write the files, because you aren't logged in as the httpd user.

The "solution" is to set the file and directory creation permissions under the Server tab in Joomla's Global Configuration. Set files to 666 and directories to 777. This will set how any new components are created, and also offer to change existing directories and files. You will then be able to ftp your files to the server.

HOWEVER ... this is a HORRENDOUS security hole. Those permissions basically give "the world" write access to everything in your components folders. If anyone manages to get any kind of foothold on your server, Joomla is then wide open to them, and they can use it as a bridgehead to totally take over your server. So the thing to do, although it is tedious, is set the perms when you need to upload something, then set them back to 644 and 755 when you are done uploading. If you leave them set to 666 and 777, you are inviting disaster.

-- hugh

 

[belindab]

Thanks Hugh,
I'll give that a try. As you say, it's a security nightmare to leave it with open write access, so I'll make sure I set it back afterwards.
B
x

 

[cheesegrits]

Just FYI, I think they've finally fixed this issue in 1.5, or at least given you the option of fixing it, by having Joomla itself use ftp for installing components. You can optionally provide an ftp user/password for it to use, and it'll then essentially ftp to itself after you upload the component, so the dir/files get created with your specified username, instead of as the httpd user.

-- hugh