Ticket #163 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Livejournal feeds aren't updating if update.php is called with ?silent

Reported by: gregarius@… Owned by: sdcosta
Priority: normal Milestone: Gregarius 0.5.5
Component: BUGS Version:
Severity: normal Keywords:
Cc: gregarius@…, sdcosta

Description

Summary says it all..

A sample LJ feed I use is: http://www.livejournal.com/users/zhaspersblog/data/atom

I ran the update manually to see if it gave me an error, but instead it refreshed all the feeds and pulled in 40 new items.

Change History

Changed 3 years ago by mbonetti

Hmm, this works fine for me. Anything specific in your setup (non-MySQL, peculiar config settings) that could explain this behavior?

Changed 3 years ago by gregarius@…

yet again I only stumble across a comment by serendipity.. some way of being notified of comments on tickets I'm interested in would be... nice..

Only thing I can think of offhand - all my LJ feeds are private, the cronjob that updates isn't logged in..

Don't think that matters though, up until late last week the LJ feeds were being updated as well from the same cron job.

Config items taht are non-default: dateordering autologout datedesc rating rss.config.resfreshafter=15 tags.delicious rss.output.lang=english noreaditems numitemsonpage=25 showfeedmeta (the ones i've not mentioned a value for are boolean, so you should be able to guess what the values are ;)

Changed 3 years ago by mdodoo

I can confirm this behavior. All my LiveJournal? feeds are also private, as they use digest authentication, which I suspect may be the problem.

Changed 3 years ago by anonymous

  • owner changed from mbonetti to anonymous
  • status changed from new to assigned

Changed 3 years ago by sdcosta

  • owner changed from anonymous to sdcosta
  • status changed from assigned to new

Changed 3 years ago by sdcosta

  • cc sdcosta added

Changed 3 years ago by sdcosta

  • status changed from new to closed
  • resolution set to fixed

It appeared that none of the private feeds were being updated. This should be fixed with [876], [877]

Note: See TracTickets for help on using tickets.