|
Page
1
of about
1
First
| < Prev
| Next >
| Last
|
Messages in Topic
|
I'm trying to append a source reference to the blog posts passing through the following pipe of mine:
http://pipes.yahoo.com/pipes/pipe.edit?_... I have tried two methods, out of which both fail in different ways, seeingly both due to different bugs in different Pipes modules. It should be mentioned that these two methods both work fine with some feeds, but not with some other, e.g. the one in this example. The suspected bug discussed in this post is in the Regex operator module. I'm trying to append a source reference to the body (item.description field) of each item, by using the following replace operation in the regex operator module: In item.description replace (.*) with $1<br><br><br>Källa: <a href="http://www.falkblick.nu">Falkblick (importerad blogg) And the "s" switch (checkbox) is also selected for this regex replace, which should make certain that the (.*) regex consumes the entire body of the item.description field. BUT, the entire body is NOT selected after all, but rather only the first row of it, which is exactly what the "s" switch should prevent! Again, this works with some multi-row posts from other feeds, but not some, e.g. this one. The best way to see the problem is to watch the debugger output of the item.description field before and after the Regex operator module in the example pipe above. This must be a bug in the Regex operator module, right? Rating :
![]() ![]() ![]() ![]() (1 Rating) |
![]()
34/Male |
|
I'm not disputing that there is a problem with the "s" switch, but I would like to make 2 points.
1. To append data to the end of a string you should use $ instead of (.*) and get rid of $1. $ specifies the end of the string. In a similar way you can use ^ to prefix data. 2. Instead of using the "s" switch you can use (?s) in your regex e.g. (?s)(.*). Rating :
![]() ![]() ![]() ![]() (No ratings) |
![]()
58/Male |
|
Thanks hapdaniel, both the methods you suggest are valid workarounds for this bug it seems!
Just as you agree though, this IS a bug in Yahoo Pipes, so it would be great if a Yahoo Pipes staff member could confirm here that they have noted this bug, and will fix it? Please also see the other bug I reported at the same time: http://discuss.pipes.yahoo.com/Message_B... Is the Yahoo Pipes team even reading this forum anymore btw? I haven't gotten any life sign from them for several months on any of the bug reports I post here, which feels a little thankless. :( Rating :
![]() ![]() ![]() ![]() (No ratings) |
![]()
34/Male |
|
Page
1
of about
1
First
| < Prev
| Next >
| Last
|


