Pb with nnslashdot

Pb with nnslashdot

[Julien Gilles]

When I try to enter a nnslashdot group, I have the following error :

 "Slashdot HTML has changed. please get a new version of nnslashdot"


Using debug-on-error, I have the following backtrace  (HTH...) :

Signaling: (error "Slashdot HTML has changed; please get a new version of nnslashdot")
  signal(error ("Slashdot HTML has changed; please get a new version of nnslashdot"))
  cerror("Slashdot HTML has changed; please get a new version of nnslashdot")
  apply(cerror "Slashdot HTML has changed; please get a new version of nnslashdot")
  error("Slashdot HTML has changed; please get a new version of nnslashdot")
  nnslashdot-lose((search-failed "Posted by "))
  nnslashdot-retrieve-headers((1 2 3 4 5 6 7 8 9 10 11 12 13 14) "Mars Lander Probably Lost (99/12/07/090211)" "" t)
  gnus-retrieve-headers((1 2 3 4 5 6 7 8 9 10 11 12 13 14) "nnslashdot:Mars Lander Probably Lost (99/12/07/090211)" t)
  gnus-select-newsgroup("nnslashdot:Mars Lander Probably Lost (99/12/07/090211)" nil nil)
  gnus-summary-read-group-1("nnslashdot:Mars Lander Probably Lost (99/12/07/090211)" nil nil nil nil nil)
  gnus-summary-read-group("nnslashdot:Mars Lander Probably Lost (99/12/07/090211)" nil nil nil nil nil nil)
  gnus-group-read-group(nil nil nil)
  gnus-topic-read-group(nil)
  gnus-mouse-pick-topic(#<buttondown-event button2>)
  call-interactively(gnus-mouse-pick-topic)
  recursive-edit()
  byte-code("..." [pop-to-buffer debugger-buffer erase-buffer t 50 print-length print-escape-newlines standard-output backtrace debugger-mode re-search-forward "\n[* ] debug(" 1 debugger-reenable debugger-args (lambda debug) "Entering:\n" debug backtrace-debug 3 delete-char ?\* 0 exit "Return value: " debugger-value prin1 ?\n ?\  error "Signaling: " "Beginning evaluation of function call form:\n" nil message "" buffer-read-only inhibit-trace recursive-edit] 3)

--
Julien Gilles.

Re: Pb with nnslashdot

[Eric Marsden]

This is a real obstacle to the successful use of HTML washing backends
(I have been thinking about this since I wrote a package for washing
search engines and once for translation engines, and I am already sick
of putting out updates for these regular HTML changes).

For stuff like nnweb and nnslashdot to be useful over the lifespan of
a stable Gnus, I believe that some sort of automatic update mechanism
will have to be put in place.

-- 
Eric Marsden