Find tech advice for business here
iWeb '09 cannot connect to FTP servers
MacFixIt previously reported on a problem with iWeb '09, wherein users were having problems publishing their sites to their hosting services. While all the credential and URL information was entered correctly and running the connection test seemed to work, iWeb would report an error when users tried uploading their sites.
Apple has recognized this problem in a Knowledge Base article, and, apparently, it is an issue with the built-in FTP server in iWeb that is incompatible with some Windows-based FTP and web servers. Previously, MacFixIt suggested that users have their hosting providers switch their accounts to a Linux or Unix based server, if available. If Linux/Unix is not available, or if it would be too difficult to do, users can still publish to a Windows server using another FTP program.
There are a variety of third-party FTP clients, but some popular ones are:
Users can publish their iWeb sites to a local folder, and then use the FTP client to upload the contents of the folder to their web servers.
Resources
I will continue to publish to a local folder and optimize and upload with Web Site Maestro. How else can you get an iWeb built site to load in Internet Explorer unless you have almost zero media content?
FTP is not the only problem. File conversion from '08 to '09 changed the names of my .mov files by adding a hyphen and a different number and is producing a lot of other discrepancies.
Publishing has become more complicated and no really useful features added.
Once again, the iWeb development team is using us as beta testers.
If anyone knows why the .mov files have -# after their names I would love to hear it. This one has messed me up a little as I have links to these movies from other places not in iWeb.
This happens mainly with text although I have had images go missing on occasion.
I change text, save and publish to a local folder. Sometimes the published version is OK - sometimes not. When I quit and relaunch iWeb it has reverted to the previous version.
The only way to guarantee that changes will take place is to delete the item, quit iWeb, restart my Mac, add the changed text or image, save and publish.
Publishing to a local folder turns all the pages blue. When you relaunch, all the pages are red again.
This is all happening with files converted from '08 to '09. Do I have to rebuild all my sites yet again as I had to do with the disastrous introduction of iWeb '08?
Nice work Apple. I really enjoy doing all this testing for you!
- by snowball77 March 3, 2009 7:21 PM PST
- i hope they fix this. I just did the ilife update March 2009 and it still has the problem. In my case I am using macdock an all mac server solution and I still can't update using the ftp option in iweb, So I published to a folder and used fetch to post it. What a hassle. I also noticed that when I posted to the Me Account certain pages would not load in the browser, neither Firefox nor Safari on 10.5.6 with a 256kb/sec wireless connection. The same pages load on the macdock site. I guess that is a traffic problem? The pages don't load very fast on the mobile me account. the pages in question are the blog pages in iweb. Why won' they even display in an Apple browser on an apple site. Seems like a rip off. So everytime I make a change I have to publish to a folder in iweb and then FTP using fetch the whole site to a non-apple site where the pages will load. Thanks for the comment about getting the media down to minimums for IE. I am away from my PC computers to test the site. I mistakenly announced the site to friends where the site is on Mobile Me and doesn't work. Kind of makes a fool of me. Why do I pay for mobile me? Why doesn't the FTP tool work in Iweb after this long of time to work out the bugs. Disgusted.
- Like this Reply to this comment
-
(4 Comments)