PRweb: Giving Credit Where Credit’s Due
2008
I’m sure it’s no secret that I’m not a fan of PRweb. However, even little old me can give credit when it’s due. So just a quickie today:
Someone pointed out an issue on a release posted to PRweb with live links. To write even remotely properly you’ll occasionally have to include a comma after a URL (such as possibly in the call to action of your release, where the site URL has to be clear).
PRweb sends links live automatically when the full URL is listed in the release. The problem is that (similar to some word processors and editors) if a comma appeared in the text after the URL, the live link would include the comma and return a 404 Not Found error.
Well that’s a pretty big problem when you’re getting people to pay hundreds of dollars to post a release with you with backlinks being a strong selling point.
I remembered Joe Beaulaurier being rather receptive to suggestions and constructive criticism in the past, so I contacted him directly this morning. I very quickly received a reply that the IT department is going to be looking into it and fixing the issue for all releases, regardless of release dates (I found quite a few with the problem, so that was nice to hear).
It’s not fixed yet, but I just wanted to give Joe some public credit for a legitimate interest in fixing the problem for their customers, and for starting to address it so quickly.
I just figured today was a good day to be fair to a company I’d ripped into in the past. I really do try to take notice and give credit where and when it’s due. I don’t have to be a bitch every day. (She’ll be back tomorrow.)




Jenn,
You’re too kind. I’ve posted an update in the DP forum.
Regards,
Joe Beaulaurier
Thanks for looking into it Joe. Do let me know when / where you’ve posted to DP. I didn’t see it in the thread in question (which is actually located in their directories forum), and I’d like to follow along with what’s being done if and when it can be resolved.
Nevermind. I see it now. Thanks.
A fix is now in place. I’d greatly appreciate it if you would check out all the locations you’d seen this problem and let me know if there are any surprises resulting from this fix or if, in fact, it’s been fixed all around.
Thanks Joe. I’m glad to see it fixed so quickly.