Comments on: Guide:: Fixing FTP with SSPU. (Site Studio Publishing Utility)

By: admin

admin — Wed, 27 May 2009 16:19:45 +0000

What version of SSPU are you using?

By: T Biehn

T Biehn — Wed, 27 May 2009 15:58:45 +0000

^filterset type=”filter” path=”.*\.css”^
^filter type=”cmd” use-input-as-output=”false”^
cmd /c bypass.bat “%%fi” “%%fo” “%%u”
^/filter^
^/filterset^

By: T Biehn

T Biehn — Wed, 27 May 2009 15:57:26 +0000

Had a trouble where siclone was munging CSS to ridiculous relative links anywhere i had ‘url(”")’ patterns.
Had to make a ghetto bypass…

in sitestudio.config under

…

cmd /c bypass.bat “%%fi” “%%fo” “%%u”

…

with bypass.bat containing:
wget -O %2 -o output.txt %3

wget from: http://gnuwin32.sourceforge.net/packages/wget.htm
Grab the dep. packages.

Can be used to bypass URL munging on any, unfortunately SICLONE doesn’t give us the temp file name, so it can’t be done w/o grabbing (unless you want to iterate over the /offer/NNN/ for download*.tmp files, this is cleaner and easier though.)

Ahem.

By: admin

admin — Wed, 28 May 2008 08:19:58 +0000

I see the zip bundle in the /offers/id/ZFS being constantly recreated with the static site every 10-20 seconds. This is with 10g Release 3 (10.1.3.4.0)

But when I check the ftp site its dumping the files to; its empty.
I probably need to do a bit more investigating.

But as a quick fix, I used to above solution which works for me or does what I thought SSPU should do..

I`m sure SSPU 7.x has similar problems.

I don`t understand why you think SSPU is working as intended.
——————————————-

I`m going to retry on a clean win 2003 WM instance..
and see If I can get the site to transfer succesfully manually. to a local FTP

By: Troy

Troy — Wed, 28 May 2008 00:14:24 +0000

Odd, I managed to get the FTP “working” (in dev) with out too much drama.
I use the term working loosely tho. As it is sending the site bundled as a zip.
The really strange thing; it was sending the same zip every three minutes.
This is with the manual publish set.
Press button, publish site, it keeps sending.
Publish again, it sends the new site wholly and continuously.
We found no options or settings that would cause this (we did not look very hard).
Decided it was ‘working as intended’ and went back to the client.