Comments for Wes' Blog

Comment on Drupal’s Aggregator Module: A Complaint by assaund

assaund — Sat, 13 Mar 2010 23:05:25 +0000

I just spotted some type of strange letters all around the websites, in case that its critical I merely considered I’d tell you. It shows this with all kinds of different words after it, similar to Error: Cannot modify body string … and so forth. It is almost certainly my browser though, mainly because I still previously had no time to update so am continue to employing google Chrome 2 but my personal web site [url=http://cheapflightstomaui1.info/ ]cheap flights to maui [/url] along with the important sort such as, yahoo.com and bing.com show up ok for me, hence that is a bit weird.

Comment on Drupal’s Aggregator Module: A Complaint by Bret Gibson

Bret Gibson — Sun, 21 Feb 2010 23:06:48 +0000

I really like when people are expressing their opinion and thought. So I like the way you are writing

Comment on Drupal’s Aggregator Module: A Complaint by Wes Wise

Wes Wise — Sun, 10 Jan 2010 06:00:56 +0000

Thanks for the feedback, Kyle.

I’m not sure what the problem is with the Aggregator module in Drupal. It works one minute and not the next. I’ve been playing around with Drupal 7 and I haven’t seen much improvement in that regard. Of course, Drupal 7 is not a done deal at this point.

I’ve played around with both the Feed API and the Feeds module. I currently like the Feeds module. It doesn’t have the confusing Feed API configuration (such a designating one node type to create your feeds and so forth). I currently have a project that will require a lot of RSS feeds, and I’m leaning towards the Feeds module for reliability. With my experimentation, it has been working well, but I need to tinker around with it more. I’ll let you know if I come across the feeds + taxonomy thing. I haven’t needed that yet, but taxonomy is such a useful thing in Drupal that it really should be applicable to everything within Drupal.

Comment on Drupal’s Aggregator Module: A Complaint by Kyle

Kyle — Sun, 10 Jan 2010 05:42:06 +0000

Hey Wes! Thanks for the post. I’ve been playing around with Drupal for a while because I want to build an aggregation site, and am definitely having some issues.

I agree with you about Aggregator: kinda clunky and just didn’t perform 100%. Lately, I’ve been using the Feeds module since everyone says it’s replacing FeedAPI and all the other RSS importers for Drupal. It’s working alright, but one of my biggest issues is that I can’t figure out how to assign a taxonomy term to the feed items I create, and have that taxonomy term be assigned to the nodes that feed creates.

That would allow me quite a bit of flexibility in managing and viewing the feed nodes on my site. If you hear of any ways to accomplish that, or hear any more news about Feeds, let me know.

Keep up the good site!

Comment on A Review of FreshBooks by Rayanne Langdon

Rayanne Langdon — Wed, 06 Jan 2010 22:56:45 +0000

Hey Wes! Thanks for the good words about us and for taking the time to see if we’re right for you. We’re here to grow with you, so it’s great that you’re able to get a feel for FreshBooks’ whole functionality with the one, big project you’re working on.

Feel free to drop me a line if you ever have any questions.

Rayanne Langdon — Queen of Hearts, FreshBooks.com

Comment on I Got My Google Wave Invite by Wes Wise

Wes Wise — Sat, 19 Dec 2009 05:40:17 +0000

I have no idea, Shawn. When I got my Wave invite you were already in the contacts list. So, it wasn’t me who sent you the invite. I did send to two other people earlier today. Well, what do you think about Google Wave so far?

Comment on I Got My Google Wave Invite by Shawn

Shawn — Sat, 19 Dec 2009 05:33:25 +0000

I’m still trying to figure out who invited me.

Comment on First Impression of Aptana Studio by Peter Severin

Peter Severin — Wed, 04 Nov 2009 18:20:07 +0000

The best thing about Aptana is that it benefits from the vast ecosystem of Eclipse plugins. I am developing a wireframing plugin for Eclipse and it also on Aptana without any effort from my part. It’s really a win-win situation, for plugin developers on one side and plugin users on the other.