subextraction patterns with no content no longer picking up whole extraction?

I am on version 5.5.2.

Prior versions of screen-scraper would give me blank results when content was unavailable, but now I'm not getting any at all. This is a pretty big deal for me, and I just want to know if it's a bug or a feature, and either way how I might address it.

<tr><td class="firstcolumn">foo</td><td class="secondcolumn">bar</td></tr>
<tr><td class="firstcolumn">ack</td><td class="secondcolumn"></td></tr>
<tr><td class="firstcolumn">foo</td><td class="secondcolumn">bar</td></tr>
<tr><td class="firstcolumn">foo</td><td class="secondcolumn">bar</td></tr>

With an extraction pattern (no regex on any variables) of:

<tr><td class="firstcolumn">~@MYDATA@~</td><td class="secondcolumn">~@MYOTHERDATA@~</td></tr>

Used to yield"

"foo,bar"
"ack,"
"foo,bar"
"foo,bar"

But now that gets me

"foo,bar"
"foo,bar"
"foo,bar"

However, if I add a regex for Non-HTML tags, it works again.

Thoughts? I just created my 1016th scrape, so going back and modifying might be a tough fix for me. :)

Further Update: Ok, now I'm

Further Update:

Ok, now I'm not sure about the version. I installed 5.0 at home (fresh box) and the extractions worked as expected. But one of our boxes here is a linux box and the properties file says "5.0" and it *doesn't* work. Not sure if that helps or not.

Hoping for a solution, things are getting a little stressy here. :)

That would be a bid deal. So,

That would be a bid deal.

So, on when run in the older version, 1) what older version do you refer to, and 2) was there in RegEx in the token?

We only recently started

We only recently started seeing this, so it's possible it was working in 5.0 or even 5.5 -- will try and nail that question down.

No RegEx in the tokens, no.

Update:

Confirmed that 5.0 behaves as I would expect, 5.5 and beyond do not. (They miss the data when there's a blank)

We've resolved this issue

We've resolved this issue outside of this thread, but for the benefit of those who follow, this turned out to be a backward-compatibility bug that was fixed in version 5.5.4a of screen-scraper. We also deemed it significant enough to roll into the 5.5 installers, which we've done and re-issued.