"Jaakko Paakkonen" <[EMAIL PROTECTED]> writes:
> Hi
>
> First of all, thanks for great piece of software. And I am sorry to address
> you directly but I don't know where else to turn to.
The right place to turn to, as is documented, is [EMAIL PROTECTED] I'm
cc'ing this reply there.
> There seems to be a bug in -p option, or either recursive get, I don't know
> which. Given situation that a web page consists of several frames, which
> have pictures in them. If you are not getting page recursively, but only
> with page requisite option, the pictures inside the frames are not
> retrieved. The example I have is a company intranet page I tried out wget
> on, so I cannot send you and example, sorry.
This is not so much a bug as an oversight. I am not a big fan of frames
(they're usually misused) and don't think about them all that much. It
didn't occur to me that the "one more hop" wouldn't be enough if the first
page were a <FRAMESET> page.
Don't have time to fix this at the moment (and I think it'll take more than
a trivial amount of coding because at the place where we increment the
recursive level, I don't believe we know that the last tag we followed was a
<FRAME> tag).
In the meantime, you can get a frameset and all requisites for the frames by
simply adding "-r -l1". For instance:
% wget -r -l1 -p http://www.site.tld/index_frames.html
The -r -l1 will go from the <FRAMESET> page to the <FRAME> pages, and the -p
will get the requisites for the <FRAME> pages.
Anyway, thanks for bringing this up -- I'll update the documentation to note
that you need to do this when using -p on a <FRAMESET> page.
---------------------------------------------------------------
Dan Harkless | To help prevent SPAM contamination,
GNU Wget co-maintainer | please do not mention this email
http://sunsite.dk/wget/ | address in Usenet posts -- thank you.
