JFTP::write: Bad response when editing theme html/CSS

[bawalker]

I get the following error when I simply go in and try to change the color scheme of the "rhuk_milkyway" theme:

* JFTP::write: Bad response
Message
* Operation Failed!: failed to open file for writing.

I have all files in the rhuk_milkyway set to chmod 777 as well as the templates folder itself set to chmod 777.  Is this some sort of bug??

[infograf768]

the file params.ini has to be writable.

Works, with another little cosmetic issue in last SVN 8239

[bawalker]

I actually updated to the latest SVN package release tonite, made sure every folder/file inside of /templates was chmodded to 777.  Yet when I have rhuk_milkyway set to default, click on the name of the template, I see the following:

Menus:  Cannot assign Default Template

Also when I try to change the color theme, I still receive the following errors:

* JFTP::write: Bad response
Message
* Operation Failed!: failed to open file for writing.

[infograf768]

I actually updated to the latest SVN package release tonite, made sure every folder/file inside of /templates was chmodded to 777.  Yet when I have rhuk_milkyway set to default, click on the name of the template, I see the following:

Menus:  Cannot assign Default Template

Also when I try to change the color theme, I still receive the following errors:

* JFTP::write: Bad response
Message
* Operation Failed!: failed to open file for writing.

Have you re-installed?
The only error I still get is here http://forum.joomla.org/index.php/topic,196120.0.html

[bawalker]

I reinstalled (keeping only the configuration file) and after making the /templates folder 777 writeable, I'm still getting the same JFTP issue as before.  I installed using the SVN nightly build from tonite.  params.ini is writeable, as well as the entire rhuk_milkyway folder.

[bawalker]

Has this issue been investigated or duplicated yet by anyone else?  I will be trying to duplicate on a second hosting account.

[kelb]

I think this is not an issue for latest SVNs.

[elfling]

I had this error aswell.

Turned out the ftp folder was wrong. It should look something like this in the configuration.php file (along with the rest of the ftp details being filled in).

var $ftp_root = '/httpdocs/

or /public_html/

etc

[bawalker]

The only temporary way I've found around this is to create a blank configuration.php file, upload it and give it 777 permissions. Then at the end, copy the configuration settings that joomla gives and post it into the configuration.php file itself. It stinks that this is a work around, but at least it does work... for now.

[derekmwright]

I noticed this started happening to me when I goofed with my FTP server settings. Some unix FTP services like proftpd will force a homedir ~ and jail you to it. So a path of

Code: Select all

/www

or

Code: Select all

/public_html

will jail you to

Code: Select all

/home/user/www

or

Code: Select all

/home/user/public_html

. If your FTP server isn't forcing this "jail" then using a path like

Code: Select all

/www

may be cause the FTP client in Joomla to try and open

Code: Select all

/www

on the server instead of

Code: Select all

/home/user/www

. You can try using the absolute path if you know it, ie:

Code: Select all

/home/user/www

or make the path relative by dropping the first backslash:

Code: Select all

www/

...

Hope this helps anybody who lands here via google!

[Gleyd]

Eu resolvi este problema apenas colocando o nome de usuário e o diretório raiz e funcionou
I to resolved the problem, I was put
For example:

Code: Select all

 /usuário/public_html/

Code: Select all

/user/public_html/

not put the name /home

[simonron]

Beware - for some reason the FTP details cant be updated in J1.5.9 ( and some lower issues) using the backend. I get :-

* JFTP::write: Bad response
* JFTP::delete: Bad response
* JFTP::write: Bad response

* An Error has occurred! Unable to open configuration.php file to write!

So, I tried setting FTP details by hand in to the config file ( which WAS writable) - and , once I ensured I had the syntax right, it worked!

NB... I may have had more trouble than most as my host uses suPHP protection - which IS a good thing but takes ages to get working correctly.

[viks]

When i am going to install any of the module or components on my website then i am getting these errors. Can anyone explain me what should i do i have tried lot with the file permissions or changes in config.php files. Just have a look in the attachments.

I am getting these messages.

Thanks in Advance.

[swettling]

I'm somewhat new to all of this as well and have been wrestling with this issue for several hours now.

What I do know is that chaning permissions on some, or all of the files in your web file system is a horrible security hole. Don't do that unless you are just testing on a local server or something.

Some solutions say to give the server ownership of the files. This option most likely won't work on a hosted website as you don't have that level of permissions (i.e. you don't have the ability to assign permissions to the account that is running Apache)

My original Joomla install did NOT use the FTP service, but this was a mistake. Without using it you will very likely run into permissions issues (unless you are running the server yourself and have max permissions).

I then enabled the FTP. Naturally, I couldn't use the online system to update it because I was getting the bad response error and the system didn't have enough permission to edit my configuration.php file. This was a frustrating battle also, so I just edited it locally and uploaded it back up with the changes I made below.

I was able to log into my system with no problem using an FTP or other clients, but for some reason it didn't want to work via Joomla.

Then the light went on. Remember that every FTP account that you create can be assigned a root, or starting folder. When you log into the system with one account it may drop you into one folder and with another account into another folder. This is by design, but it is critical that the Jooomla FTP settings mesh with the FTP account that you are using.

Once I updated the FTP Root on my system to public_html/j1 (j1 is the joomla folder for this particular test, public_html is the public root of my website) it worked great.

Notice, though, the absense of a preceeding /

This is because the folder is being referenced relatively from the root of the FTP login that I have specified. I could create an account that would log me right into the public_html folder at which point I would only have to put j1 in the FTP Root setting.

If I put a preceeding "/" character, it is going to reference the folder from the root of your whole account, so putting in /public_html/j1 will never work because that folder doesn't exist.

Anyhow, this may seem totally obvious to many of you and you're probably laughing that i had so much trouble, but it was nothing short of frustrating for me. I hope this helps a little bit.

[michael_king]

Briefly, when using 1.5.9 we found that we needed to include the trailing / For example /public_html/subfolder/

Without the trailing / we could not save configuration settings

[mcsmom]

Are you using IIS or Apache?

[DJoh]

I was also having this problem, immediately after the default Joomla install v. 1.5.10.

I could add users and such (which i think is a database operation), but couldn't change timezone or other "Global Settings".
I'd get this error:

Code: Select all

JFTP::write: Bad response
An Error has occurred! Unable to open configuration.php file to write!

The default install had set

Code: Select all

Enable FTP = YES

So I disabled FTP, since the mouseover says "Enable FTP upload capabilities instead of the normal method". The normal method appears to give me no problem, I can change now my timezone etc.
My problem is solved as far as I can tell, by disabling FTP.

I still cannont turn the FTP on, or I get these errors:

Code: Select all

JFTP::write: Bad response
JFTP::delete: Bad response
JFTP::write: Bad response

An Error has occurred! Unable to open configuration.php file to write!

And I think I know why:
using my hoster's user/pw they gave me, I can SFTP & SSH (terminal etc.), and access any directory.
but if I FTP I am locked into one directory, which is NOT my Joomla dir (since the Joomla install is a development site, not a live site right now).
So If I try to tell Joomla to use FTP, it can never access the directory it needs to, regardless of what path I give it.
This is after getting my hosting guys to change all the permissions on the joomla directory to my user . The permissions used to be user:group = root:root, which meant i couldn't make any new folders/files, so even if FTP had worked I would have still have write-permissions problems with the Joomla FTP settings.
If Joomla had built-in SFTP, then it would work, but it only has non-secure FTP, which my hoster is more restrictive of.

You can probably find out what your problem is by manually FTPing into your site: use whatever FTP program you like, type in the user/pw your joomla site has in it's "Global settings" page, and see what directory your hoster starts you off in.
Then try to find your joomla directory (the one with configuration.php in it).
Then try to create a folder and/or delete that folder inside the joomla directory (to check your permissions on the dir).

If all those go well, then you now know the host, user, pw and directory you need to type into the Joomla settings page.
If you have problems with any of those, they you may as well disable FTP (someone could enlighten me as to what features I lose by disabling FTP, I'm a j00mla n00bie) OR SSH in/tell your hoster to correct your permissions, or type in the correct path you needed to get to you Joomla directory, or whatever you found was the problem.


PS. I also found that I can easily change the FTP settings, before re-enabling FTP, when "Enable FTP" = NO. Then, using the "nromal" mehtod, I can set FTP settings, then enable FTP when they are correct. That might help some of you.

[sf_gabe]

I'm somewhat new to all of this as well and have been wrestling with this issue for several hours now.

What I do know is that chaning permissions on some, or all of the files in your web file system is a horrible security hole. Don't do that unless you are just testing on a local server or something.

Some solutions say to give the server ownership of the files. This option most likely won't work on a hosted website as you don't have that level of permissions (i.e. you don't have the ability to assign permissions to the account that is running Apache)

My original Joomla install did NOT use the FTP service, but this was a mistake. Without using it you will very likely run into permissions issues (unless you are running the server yourself and have max permissions).

I then enabled the FTP. Naturally, I couldn't use the online system to update it because I was getting the bad response error and the system didn't have enough permission to edit my configuration.php file. This was a frustrating battle also, so I just edited it locally and uploaded it back up with the changes I made below.

I was able to log into my system with no problem using an FTP or other clients, but for some reason it didn't want to work via Joomla.

Then the light went on. Remember that every FTP account that you create can be assigned a root, or starting folder. When you log into the system with one account it may drop you into one folder and with another account into another folder. This is by design, but it is critical that the Jooomla FTP settings mesh with the FTP account that you are using.

Once I updated the FTP Root on my system to public_html/j1 (j1 is the joomla folder for this particular test, public_html is the public root of my website) it worked great.

Notice, though, the absense of a preceeding /

This is because the folder is being referenced relatively from the root of the FTP login that I have specified. I could create an account that would log me right into the public_html folder at which point I would only have to put j1 in the FTP Root setting.

If I put a preceeding "/" character, it is going to reference the folder from the root of your whole account, so putting in /public_html/j1 will never work because that folder doesn't exist.

Anyhow, this may seem totally obvious to many of you and you're probably laughing that i had so much trouble, but it was nothing short of frustrating for me. I hope this helps a little bit.

That was exactly what I was looking for, I've been banging my head up against it for hours.

Note for others: This was causing a problem in Phoca Gallery thumbnail creation for me or else I wouldn't have noticed it.

[tosaha33]

This might help someone:

http://forum.joomla.org/viewtopic.php?f=470&t=411326

[jcsarmento]

Men,!!!

found it for apache: use the root path ftp: "httpdocs/" and configuration.php must have write access.

that´s it.

enjoy jcsarmento

[iminovermyhead]

Hello All,

So i tried all the various methods.

Manually edited the config.php file, upload via ftp client. tried with the preceeding / and without.

what i realized was that i could edit and change my templates and global configs prior to setting my ftp settings.

i changed enable ftp to 0. and now i can edit my html, and global configs.

so the question is, what is the benefit to having ftp set to yes? that is if you can configure it correctly.
and what is the disadvantage of having it set to no?

aloha

[charleyhankins]

I was getting JFTP::write: Bad response when attempting to upload extensions or save settings. my "var $ftp_root = '/public_html/~sacc';" was that. so, I removed the "~sacc" and presto! Save-o!

CH

[jcsarmento]

forget my previous post about writing access , it´s not secure.

change de owner of the file to apache and it´s solved.

[olyma]

I finally figured it out in my case too. To be able to write to the configuration.php file and make the FTP work in Joomla, I changed the host to just be the site URL I’m working with, and when I checked the root directory from the host-provider specifically within my FTP program, unlike another provider I’ve used, the root was simply a / , so I changed the root directory in the configuration.php file to simply be a / .

varftp_host = 'name-of-my-site.com';
var $ftp_root = '/';

And now the FTP works! Yeah!!!!!!

[conort77]

I had the same problem, it turns out that my language files hadn't installed properly. I copied them over from a previous installation and it's working like a charm.

[junbernardo]

I finally figured it out in my case too. To be able to write to the configuration.php file and make the FTP work in Joomla, I changed the host to just be the site URL I’m working with, and when I checked the root directory from the host-provider specifically within my FTP program, unlike another provider I’ve used, the root was simply a / , so I changed the root directory in the configuration.php file to simply be a / .

varftp_host = 'name-of-my-site.com';
var $ftp_root = '/';

And now the FTP works! Yeah!!!!!!

Yeah, this worked for me also. I retained varftp_host at 127.0.0.1 but changed ftp_root to "/".

I am now wondering how changing the root will affect the site since I want a separate folder for ftp. Anyway, thank you for the post olyma.

[sandrineleplen]

Check your sites error log to see if there is more information. You are going to have to dig into this one since it is an environment (site) issue. There must be something different about this site from the other.

The save should be like all the other saves in the theme options.