Yvonne Smith said:
> Firstly, what the heck do I do if people are nuts enough to repeat the > *same* story link multiple times on a page? At least two sites I use > do this, and it drives me nuts. You read the story once, and later on > in the same scoop you get to read it again because they've decided > it's important enough to reference it multiple times. help? > Interestingly, both of these problems have happened on sites where > I've had to cheat to get the printable page. The printable URL doesn't > relate in any way whatsoever to the original URL, so I create a three > level site with the story URL being the printable version. I don't > *think* this has anything to do with it grabbing the story multiple > times, since I'm presuming it'd do that even if it were a two-level > site and the story link was repeated multiple times, but I don't > really know. Actually, I think what's happening is that sitescooper is presenting the 2nd-level page, and the story-level page in the scoop. A kludge to fix it is to use a ContentsStart and ContentsEnd pattern that cut out all the text except the printable link; or alternatively, see if you can simply get all the "normal" (non-printable) story pages using StoryFollowLinks: 1 (assuming the problem is that the story is split over multiple pages). > My other problem is, I've got a handful of sites that simply do not > update. I mean, the page changes, but sitescooper completely fails to > realise this and doesn't scoop the new stories. Most notably, anything > I'm trying to grab off the zend php site. It scoops fine when I run > it the first time, but refuses to grab the new stuff when it turns > up. I generally have to rescoop the page with refresh on to get it to > see the stories, and then of course it grabs the rest of the stories > as well. Could you send me a site file that demo's this and I'll take a look? --j. _______________________________________________ Sitescooper-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sitescooper-talk
