Why not allow cron do the synchronization (adding new terms from nodes, possibly deleting non-existent ones if the user requested it), rather than have to synchronize manually?

Comments

Zen’s picture

Zen commented

The sync function, in my experience, is used just about once - when NAT is enabled on a site that contains pre-existing nodes. There might be a case for using cron to temper the number of nodes sync-ed on each run, but this can probably be better handled via the batch processing feature of 6.

-K

Zen’s picture

Zen commented
Status: Active » Closed (works as designed)
vacilando’s picture

vacilando commented
Version: master » 5.x-2.1
Status: Closed (works as designed) » Active

I am adding token [nid] to the title which, using NAT, creates a taxonomy entry.

The problem is that for new entries, there is no nid - probably because in the moment NAT ran token could not supply it yet. So an incomplete term is created in the vocabulary.

Q1: Is there a way to have NAT run later than token?

Q2: Based on this example - can you reconsider adding a cron for the synchronization? If I could run cron every few minutes, the proper terms (with nids) would be created in the vocabulary.

Thanks for looking into this.

Zen’s picture

Zen commented
Status: Active » Fixed

You can probably modify execution order via the "weight" field in the system table. Google for module weights on d.o. There might also be a module to get this done.

Cron synchronisation also only works for nodes that do not have associated terms.

-K

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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