I discovered (much to my chagrin) that a first-time install of the Ad module on a Drupal install with at least 1 existing taxonomy will cause problems. Specifically, it will assign itself the taxonomy with vid 1, which means that it will use whatever happens to be in that taxonomy as its ad groups. In addition, any new taxonomies created after the ad.module install will encroach on existing vocabularies by taking over their tids.

I managed to narrow the problem down to the sequences table, where after numerous exports, drops and imports I discovered that a critical row is not created until later in the DB upgrade: vocabulary_vid. Once I added that row and assigned it a value higher than my highest vid, the problem went away.

If this is a bug that others can duplicate, I'll take over the issue and submit a patch.

Comments

jeremy’s picture

jeremy commented

Are you saying that you only have this problem after you are manually editing the database?

jeremy’s picture

jeremy commented
Component: ad.module » ad module
Status: Active » Fixed

No further feedback. I set up a test environment in which I created a manual vocabulary first and assigned various nodes to it. Then I enabled the ad module, and it set up a second vocabulary for ad groups, no problems. From your comments above, it sounds like you may have been editing the database directly, which likely would have caused your problem.

I am unable to duplicate your problem.

Anonymous’s picture

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

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