Calais - Port to D7

There is work being done as we speak to upgrade it to D7. We dont have anything usable yet as the introduction of Taxonomy as Fields has complicated the problem a bit. We are working on it in github, https://github.com/phase2/opencalais and will hopefully have something people can start using soon.

Hi, do you have some news if the module will be useable with Drupal 7 in the foreseeable future yet?

Greetings

We are still working on it, the experimental branch has the most up to date functionality. The thing to note is that the module files are getting renamed from calais.module to opencalais.module to match the folder. Beyond that it is an entire rewrite b/c the handling of taxonomy terms and their relation to nodes has changed completely. So, feel free to try using it, fork it and fix bugs/extend if you'd like, but I would say that the functionality is currently pre-alpha and could change dramatically any day as we discover the right way to provide this functionality (and more) in D7.

Ok, thanks for the update!

+suscribing

+subscribing

subscribing. This sounds awesome!

+1

+1

sub

subscribing

+1

+1

Subscribing

Title update for our sanity :)

sub

Subscribing

subscribing

subscribe

subscribing

I'm glad to see some action going on over on Github. I'll be downloading and testing it in a couple of weeks. Keep up the good work.

Initial port is in the 7.x-1.x branch. It is not perfect by any stretch. Alpha quality at best. jec006 deserves all the credit here, good work helping figure out the maze that is field api.

Hi Guys,

Great work on getting the 7.x release out. Attached to this comment is your first patch.

I tried out the module and I was getting errors from Entity in the Drupal core. When I had a look into this I found a similar issue which was logged with the Migrate module. When creating a field the "allowed_values" setting was changed to take a machine_name. The fields that were being created were being linked to a vocab which didn't exist and this caused problems when it came to saving the tags.

I had a look through the code and through a bit of trial and error found the areas which needed to be changed for this to work.

Have a look through the attached patch file and let me know what you think.

Sorry, forgot to remove one bit of code which was commented out.

Attached is v2 of the patch.

Diff did mark some lines as edited when there wasn't any change made in the end, ignore those :)

subscribing

awesome, thanks akoepke,

Let me take a look at the patch and i'll get it committed as quickly as possible.

I appreciate the work

I am trying to implement using SemanticProxyService for tagging RSS feed items from publishers.

I am not sure how this is supposed to be configured, but I have kludged the scripts to get it working. I would like to know how it should be done. I am not sure how to get my code out of these modules.

Along the way I have bumped into a few coding fixes. Should I post them into this thread?

in SemanticProxyService.inc, I am not yet sure what "flatTriples" are, but I wrapped this condition on the assignment
in public function analyze($content)

  if (isset($this->processor->flatTriples)) {
    $this->flatTriples = $this->processor->flatTriples;
  }

I added this empty function to stop an error
function analyzeHTML($content) {}

and fixed a typo in
public function analyze($content) {
add "$"
from:
$url = content;
to:
$url = $content;

To use smanticproxy, I forced this configuration in opencalais.module

// $opencalais = opencalais_api_get_service();
$options = array('host' => 'service.semanticproxy.com');
$opencalais = opencalais_api_get_service($options, 'semanticproxy');
//$tags = $opencalais->analyzeXML($node->title, $body, $date);
// $tags = $opencalais->analyzeHTML($body);
//$tags = $opencalais->analyze('http://www.bbc.co.uk/go/rss/int/news/-/news/world-south-asia-14190552');
$tags = $opencalais->analyze($node->field_url['und'][0]['value']);

I have no experience making patches, but could figure that out. The main thing is that I have no confidence about these changes, or how this should work.

Applied the wabn_v2 patch. Thanks again akoepka. http://drupal.org/commitlog/commit/5830/39c6970a0a4460f647deffd91b67cd9a...

Hi js,

Without looking into it too much, it appears like we need to add some configuration options so the admin can choose which proxy to use. The $ fix looks good though. Would you mind creating a patch for those two fixes that prevent errors?

I'm creating a new issue for this so we can keep better track of it: http://drupal.org/node/1232458 so go subscribe and post anything you find there.