So nothing worked on the new update, Calais insisted on creating new taxonomy tables for no reason known! My old taxonomy is broken as a result, I would gladly recrawl everything should Calais provide a simple way of recrawling the site, documentation is insufficient because I don't have a PhD in Computer Sciences or whatever the coding gods demand we understand because of course they will never ever stoop down to our levels.

God help me. And good luck to Drupal.

Comments

irakli’s picture

irakli commented

Heh :) The best issue one can get on a Monday morning.

Which version did you update from? There was no database change between 3.2 and 3.3. Not to sound like pointing fingers away, but you sure it was OpenCalais that broke your taxonomy?

Thanks

deltab’s picture

deltab commented

yup! pretty sure. else i would not get two "cities" and "anniversaries" tables, instead of one, right? So yup, I am pretty sure, went from 3.2 to 3.2 and what have you? Two tables in Taxonomies for each in Calais, and two in Variables as well!

Besides, I updated nothing else, only Calais, and henceforth this nightmare. I don't have many modules, only feedapi, calais and views in my site.

deltab’s picture

deltab commented

To add, I tried some other modules, like activitystream and stuff, but those were nowhere near production grade, so removed them, I just have feedapi, calais and views; so Calais broke my site again.

irakli’s picture

irakli commented

When you did the update of the module, did you "uninstall" old version and then "re-install" the new one or did you just overwrite new files?

Also, if you have "devel" module installed can you, please paste here the value of "calais_vocabulary_names" variable? You can also get the same by putting following code in your page.tpl.php:

<pre>
<?php print_r(variable_get('calais_vocabulary_names', FALSE)); ?>
</pre>
deltab’s picture

deltab commented

Okay, fixed the database, I anyway need to recrawl the site, read this: http://drupal.org/node/409630 installed calais_bulk_import.php and ... nothing, the database reads:

calais_bulk_import_last_processed N;
calais_bulk_import_nodes_completed b:1;

what needs to be done here? I had run admin/settings/calais/bulk-process a long time ago.

febbraro’s picture

febbraro commented

Have you tried just using the standard Bulk Process script that ships with the module? Or only the external script?

In the next month or so we plan to revamp bulk processing to be able to slice/dice your nodes for selective (or total) bulk processing running via cron/drush. This will make things easier (especially if you have a ton of nodes) However, you should try the stock bulk processor that uses the Batch API first and if that does not meet your needs, then get a little crazier.

febbraro’s picture

febbraro commented

Oh and BTW you said you fixed the core issue for this module. What was your fix, were you able to determine what happened?

deltab’s picture

deltab commented

Thanks, I had some errors in the Watchdog saying Calais could not find already created tables, and on install, it still showed as Version 3.2 after install (I ran the update check twice manually, and it still showed that way). So I unloaded the module (don't know what is the correct word), not uninstall, i.e., delete all tables and completely remove it; and then reloaded it. After this I found duplicated tables. However, I did not remove old Calais tables.

I tried the external script, but it stopped with "Processed through record . 0 remaining." and the two tables appeared as mentioned above. The standard Bulk Process has a Invalid URL error if I leave Semanticproxy on, so for now trying nothing. Hopefully the revamped bulk processing will allow Semanticproxy and storing of semanticproxy data in CCK fields?

deltab’s picture

deltab commented

My fix was to (a) manually change the ID of all Vocabularies in Calais; and (b) delete all the new tables.

Do you know if I can get the external script working? I saw some observations about "calais_bulk_import_last_processed N;" but I am not a coder, so a nicely rolled Cron script might help.

deltab’s picture

deltab commented

@febbraro, by the way, can you remember to make Calais save nodes on update in such a way that they get queued for reindexing? I use Apachesolr now, and notice a manual edit of calais tags (node/##/calais) or /admin/settings/calais/bulk-process do not reindex taxonomy terms as changed.

febbraro’s picture

febbraro commented
Status: Active » Fixed

Added the nodeapi update invocation on calais tab saves. Thanks for the idea about a decade ago. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.