Why would TSS stop functioning? [#144189]

This module stopped working for me when I upgraded Localizer 1.7 to 1.9

It seems apparent that it is a change with Localizer installation/operation that has caused this however I am just seeking assistance from this side as it might be a simple tweak that is needed to remedy the issue.

Obviously the TSS module depends on the Taxonomy module and Localizer has changed something here. Before one had to patch the Taxonomy module (and TSS worked), now one doesn't patch it instead a patched version of the Taxonomy module is provided and one must place it in the sites/all directory (along with other patched modules). So it seems to override the standard Taxonomy module.

You can probably tell I have no absolute understanding of the working - more like investigative guesswork!

Any ideas why this would have happened and whether there is a simple adjustment or workaround?

Comments

Comment #1

bobdalob commented 15 May 2007 at 15:22

I have just tried messing around a bit to see what's what.
-I've tried deleting the tss settings in the db variable table, clearing the cache afterwards.
-I've reset the content type for each vocabulary
Nothing

I messed around editing the vocabs by toggling 'required' & 'free tagging' in various permutations and that actually brings back the option buttons but neither follows any logic to do so (can't repeat) nor does it do so with the required settings for the respective vocabularies.

I switched back to a backup site (Localizer 1.7 and same version of TSS and all is well and rock solid). The breakdown is a direct result of upgrading Localizer however I do not know if the reason is being a victim of Localizer's manipulation of Taxonomy and/or a frailty of TSS - therefore I have also posted the error as a Localizer support request (http://drupal.org/node/143665)