2 replies to this topic

[jarvis393]

I have been practicing uploading websites that have been optimized with WebCrusher.
I have only been successful once.

The websites are primarily jpeg oriented. Very little text.

My workflow is to bring the jpeg into iWeb with image optimization set to OFF in the preferences.
I typically build a few pages, publish to a folder, drop the folder into WebCrusher
and then try to export to my webserver (Network Solutions).

On relatively small sites I usually end up with an error message that says "oops.........child died".

When that happened a few times I continued with dropping the published folder into to Webcrusher but then,
rather than export to Network Solutions, I would drop the "optimized" folder onto an FTP program called Transport.
About a half hour later I would be online.

This evening I tried to test the real deal website.
I don't know what is a big website and what is a small one. This one is 17MB.

The Webcrusher optimization report says that I saved 7.36 MB of 15.66 MB
(Though GetInfo says the folder is still 17+MB in size)
I tried to export the files directly from Webcrusher but both times eneded up with an error message that said:
"tcp error, connection dropped".

My current strategy is to try the FTP transport again.
My expectation is that it will be successful, just take forever.

MY QUESTIONS ARE:

1) What does TCP Error mean?

2) Does optimization work if you don't use the export function from Webcrusher?
i.e., should I start with webcrusher & finish with FTP Transport?

Any insight would be helpful.

For what it is worth, I am running on an Intel Mac with OSX 10.4.1.
The website I am launching to is called: testidea.net.

Any suggestions?

Jarvis

[Jeremy]

Hi Jarvis,

Sorry I cannot answer your TCP question. But I will tell you that you can still optimize and then upload using an external FTP client. All you need to do is press export, then clickon open enclosing folder to access the optimized files.

[RageSW]

I have been practicing uploading websites that have been optimized with WebCrusher.
I have only been successful once.

The websites are primarily jpeg oriented. Very little text.

My workflow is to bring the jpeg into iWeb with image optimization set to OFF in the preferences.
I typically build a few pages, publish to a folder, drop the folder into WebCrusher
and then try to export to my webserver (Network Solutions).

On relatively small sites I usually end up with an error message that says "oops.........child died".

When that happened a few times I continued with dropping the published folder into to Webcrusher but then,
rather than export to Network Solutions, I would drop the "optimized" folder onto an FTP program called Transport.
About a half hour later I would be online.

This evening I tried to test the real deal website.
I don't know what is a big website and what is a small one. This one is 17MB.

The Webcrusher optimization report says that I saved 7.36 MB of 15.66 MB
(Though GetInfo says the folder is still 17+MB in size)
I tried to export the files directly from Webcrusher but both times eneded up with an error message that said:
"tcp error, connection dropped".

My current strategy is to try the FTP transport again.
My expectation is that it will be successful, just take forever.

MY QUESTIONS ARE:

1) What does TCP Error mean?

2) Does optimization work if you don't use the export function from Webcrusher?
i.e., should I start with webcrusher & finish with FTP Transport?

Any insight would be helpful.

For what it is worth, I am running on an Intel Mac with OSX 10.4.1.
The website I am launching to is called: testidea.net.

Any suggestions?

Jarvis

Hi Jarvis,

Does it just say TCP error? Do you not see a number? Most likely your FTP server is entered incorrectly or you have not entered the directory path correctly. Both can be retrieved from your web host.

You can Export to a folder in WebCrusher and use any FTP client to publish your site.

The differences in size for the directories from WebCrusher to the get info window is because of the difference in calculations. If you look at bytes you will see the exact same size. In later versions of Mac OS X (10.6 I believe) the calculations were changed and now you will see the same size reported by both methods. If you are interested, here is a website that talks more about this;

http://reviews.cnet.com/8301-13727_7-10330509-263.html