Field SQL norevisions breaks Taxonomy module

The taxonomy module seems to have a hard dependence on field_sql_storage.

taxonomy_build_node_index() has an explicit check that field_sql_storage is used:

if ($field['module'] == 'taxonomy' && $field['storage']['type'] == 'field_sql_storage')

Check out our fork here, should fix this issue https://github.com/highwire/field_sql_norevisions

I confirm AKAli. I Installed FSNR and it broke taxonomy indexing. please fix it.

Pwaterz, I used your fork, first it worked but then it destroyed my site. please help. non of taxonomy based tables doesnt work.

@tohidd this module has the following on the project page

WARNING: Once this module has been enabled there's no going back :)

I hope you have backups?

The data on my site - including taxonomy included data - was uploaded and imported manually (from my previous site). After installing new site and moving data, I installed Field SQL norevisions. during two last months it was in my site, But today I discovered that the new contents does not effect taxonomy index table, so I googled and installed your fork. then all of my taxonomy based tables and review pages which are based on fivestar gone. I guess my hosting provider keeps a backup. but what could i do now?

--

Update: I copied original version of Field SQL norevisions and executed update, now all of my tables and site are fine. but still there is old bug now, When I create new nodes, there are no update in taxonomy index table. can you help me fix this bug?

@tohidd you can't just swap between the fork and the module without adjusting the values in your field config table.

Looking the code what you'll need to do is to write a script to carefully update the field_config table. All you need to be using the fork and change the storage setttings to have the type equal to field_sql_storage and the module equal to field_sql_storage. I would advise you write a little php script to do this since messing with serialised data in sql queries is not for the faint hearted.

Thanks alex

I will add an update to the fork to fix that.

@pwaterz no longer a fork :) 7.2 version!

Sounds good! I'll create the 7.x-2.x-dev branch.

Hi pwaterz, Do you have an ETA? :)

I will try and get to this today.

7.x-2.x-dev is now up :)

Awesome! Will give it a shot :)

So, is this taxonomy issue fixed in 2.x-series?
We probably need this module in an upcoming project, it might save around 15-30Gb of unneeded revision table data.

bibo yes it is.