Hello, Alex.

I write about this problem on http://drupal.org/node/115049 and http://drupal.org/node/123062.

I try to say so more information as possible.

1. I have test project (on localhost). It contain php 5.2.1, mysql 4.1.12, Apache/1.3.37 (Win32) PHP/5.2.1 and Drupal 5.1
2. My project intensely use a leech module. There are 10 feeds with more than 500 items (news) per feed. My project is a travel news accumulator (mainstream)
3. I must note, what i don't have critical errors while leech module worked.

4. I have "fat" and highspeed internet access from my work and home.

But there are a few problems when I try to create feed on my work (public) server. Lets see a feed (http://turist.ru/export/article_yandex.rss.xml). This feed fine work (and create) on localhost without any problems and errors. There are many items leeched from this feed. But on my real server I cant create feed even. When I edit feed url - after a few second "additional option" blocked and grayed. (See attach http://drupal.org/files/issues/td-cut5.jpg)

I see to souce code of module (i small know php and js) - but not found a code where it is testig connection to this url.

I try increase value of variable $ connection->timeout = '25'; but without a positive result.

This problem arises with 3 feeds.

Comments

alex_b’s picture

What are you running on your work server?

toologic’s picture

O, sorry
On work server is set up next software - Drupal 5.1, Apache 1.3.x, PHp 5.2.1, MySQL 5.0.24a.

arsart’s picture

Hi all,

I've same issues with many FeedBurners RSS feeds.
For example well formed http://feeds.we-make-money-not-art.com/wmmna (or even direct http://feeds.feedburner.com/wmmna) give me no Additional Options in leech publishing and stops leeching data after it "force publishing".
Sometimes FeedBurners leechs well , like http://feeds.feedburner.com/reluct
Can't get why? Does FeedBurner make some dodgy jobs with feeds?

That's annoying because many of cool sites have a FeedBurner feeds but not core engines:(

alex_b’s picture

toologic,

There is mostly likely some issue with php5/myslq5. Although Aron just told me that he has leech running on php5/mysql5 without problems, it's not the environment we usually deploy it on.

It would be great if you could set out to track down this error by yourself and post back here what you are finding.

Please understand that I do not have the bandwidth to go after issues like these myself.

Alex

alex_b’s picture

arsart, I don't have problems with the feeds you posted. they all add and download fine. probably i miss a point and you want to follow up with a more thorough explanation of what's going on. in that case, please open a seperate issue, because i think you problem is not related to toologic's. Thank you.

aron novak’s picture

Assigned: Unassigned » aron novak
Status: Active » Needs review

Alex is right, I tested the feeds in my dual test environment (both PHP 5 and 4 in almost identical configuration). In case of PHP4 everything works smoothly, in case of PHP5 I can reproduce the bug.
The problem is fixed in leech 5.x CVS.
But the solution is only a workaround.
Regex masters, please tell me what can be the problem:

//if (preg_match('%<(rss|rdf:rdf|feed|channel)[^>]*>(?=.*</\1>)%siU', $connection->result->data, $matches) < 1) {
// I use this less strict checking because of some PHP4 - PHP5 annoyance
if (preg_match('%<(rss|rdf:rdf|feed|channel)[^>]*>%siU', $connection->result->data, $matches) < 1) {
arsart’s picture

Alex_b, It's a pity I don't get any errors on this, just feed became useless and "Additional options" hides, as I get that's a PHP5 problem and fixed in CVS version, am I right? Anyway I'm using official release.

alex_b’s picture

arsart, did you try the solution Aron posted in #6?

arsart’s picture

I'm using last CVS version leech.module (v 1.4.2.21), yes the problem has gone. Issued feeds works well... but also I had a problem with non utf-8 described here http://drupal.org/node/125755 :(

aron novak’s picture

Status: Needs review » Fixed

I double checked and the bug has really gone away. I'm going to check the other ticket w/ the encoding problem.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.