Hey there,

I just upgraded a test site to 4.7 and then installed category module on top of taxonomy.

I activated the wrapper module and category legacy to import my terms to category module and all went well...

The I activated category wrapper module to make sure all other modules that depend on taxonomy are still working.

I notice that all my forum terms and vocabs have been saved and tranfered, even even though I selected the redirect paths option, My forum module now shows empty categories. I know the terms are there ( in the category admin section) but they don't show at all in the forum module settings page.

Any ideas what could have went wrong??? How could I make the new category module reinsert the categories in the forum module like they were before?

Thanks

Comments

patchak’s picture

I should add that when I choose to add a forum topic on the site, the categories are there, so the link between content types and the categories themselves work...

The only thing that failed to redirect correctly is in the forum module itself as it shows like it is empty (no categories and no containers...)

Thanks

patchak’s picture

I'm sure there is an easy way to upgrade a forum to category module, would anyone just take a couple of minutes to try and help?? Thsi is the last thing that I need to fix before moving to category module bu tI can,t understand how it is possible that it's so difficult to upgrade a forum to be used with category module.

Thanks for any help.. getting really desperate here

Jaza’s picture

Version: master » 4.7.x-1.x-dev
Component: Wrapper modules » Category_legacy
Category: support » bug

I just tried importing a set of forums into category from taxonomy, using category_legacy. You're quite right: they don't show up in the 'forum' or the 'admin/forum' pages. This is because category_legacy does not update these two variables in your site's 'variables' database table:

- forum_nav_vocabulary
- forum_containers

This is a bug - category_legacy should take care of things like this, and I will fix this bug as soon as I get a chance. In the meantime, you can update these variables manually, by changing the relevant rows in your database's 'variables' table, using a tool such as phpMyAdmin. For example, if your old forum vocabulary was '50', and your new forum vocabulary (i.e. container) is 61, then change forum_nav_vocabulary from i:50; to i:61;. If you had two containers (i.e. terms) 66 and 67 on your site, and they're now containers (i.e. categories) 81 and 82, then change forum_containers from a:2:{i:0;i:66;i:1;i:67;} to a:2:{i:0;i:81;i:1;i:82;}. Once you've made these changes, empty your site's 'cache' table, and everything should work.

tkgafs’s picture

Jaza,

could you expand on your workaround for instances where there were no previous forums and I am trying to create a container and some forums from new

Tkgafs

patchak’s picture

jaza, thank you so much for the fix!

I really love the category module, I could not understand that this was not actually working.

Thanks again,

patchak

patchak’s picture

Jaza,

I just don't get what are the variables to change!

Check out my forums variables line:

a:21:{i:0;i:30;i:1;i:34;i:2;i:39;i:3;i:42;i:4;i:45;i:5;i:48;i:6;s:2:"30";i:7;s:2:"30";i:8;s:2:"34";i:9;s:2:"39";i:10;s:2:"45";i:11;s:2:"42";i:12;N;i:13;N;i:14;N;i:15;N;i:16;N;i:17;s:2:"30";i:18;i:60;i:19;s:2:"30";i:20;s:2:"60";}

From what I can understand my forum containers (categories) are terms 30 and 60... But the thing is I have sub categories as well.. But the numbers in this line do not match the subcategories... Do I need to change the sub-categories (forum categories) or only the references to the forum containers (categories?).

Like I said I don't get all those extra number that are there, because they don't match with the sub categories terms numbers I had on the site...

Should I just change every reference to 30 and 60 to the new terms?? would that be enough?

thanks

patchak’s picture

Update:

The new forum containers (categories) are for ancient term 30 > now 151 and ancient term 60 > now 161.

I tried to replace every reference to 30 with 151 and to 60 with 161 and it gives huge series of errors,

* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
* warning: in_array(): Wrong datatype for second argument in /homepages/46/d117124046/htdocs/jedebogue/www/chienTEST2/modules/forum.module on line 705.
______________________________________________________________

Could you for the sake of a good example post the new modified line that should work here please?

OR: when do you think the bug will be fixed so I could just wait till the bug is fixed instead of just wasting time doing it by hand?

Please note that the same bug applies to image module but the fix is more simple you have to edit the variables for the image module vocab and the image_gallery_vocab. That worked right away, but I'm confused with the forum variables, as my line seems way longer and more complex that the one in your example, and, like I sais replacing all occurences of term 30 and 60 to 151 and 161 does not work at all.

Thanks for your time,

Patchak

patchak’s picture

update 2:

Ok I managed to erase all the crap on my containers variable line, and leave only the two containers I actually have, like in your example. I also pointed the good forum_nav variable to the good node.

So far so good, I can actually navigate to the forums, and see all my containers and categories there, like it was before.

There is still a problem though, all the threads have been moved!!! I can't access any thread because besides all threads there is a link saying "this thread has been moved" (ce sujet a été déplacé) in french...

All the threads inside a specific container have been actually redirected to the forums's original alias... And when you click on the link you get to the node itself of the forum but outside the forum system...

This is getting pretty complicated as the nodes themselves are there on the system and well interlinked together, BUT they are not integrated in the forum system, they actually look like articles nodes or whatever.

I tried to upgrade the forum and to transfer it to category module with path redirection and also without path redirection and it is always the same problem. INSIDE the forum system, the threads are ALLL redirected to the forum's home page...

I hope this is clear enough so you can help, are you still looking at this Jaza? It seems like a major bug in the system if I can,t transfer my forums smoothly!

Thanks

patchak’s picture

Component: Category_legacy » Wrapper modules
Priority: Normal » Critical

I changed this issue to critical, as for the moment, it seems simply not possible to transfer a forum from taxonomy to category module.

All the threads in the forums are redirected to the containers's URL, which makes no sense.

I think category module is not usable to upgrade on a site that was using taxonomy and forums at this point, I have not been able to transfer a single forum correctly from more than 10 different try outs on different sites.

I even tried on a fresh install:

http://jedebogue.com/test2/?q=forum

as you can see here, category module looks up the containers and forums ok, but all the threads are redirected to what it seems is the old taxonomy term ID.

But if you go and browse the term forums itsels, all works and the threads are not redirected so this seems to be a bug in the communication between forum and category module.

http://jedebogue.com/test2/?q=node/49 --> as you can see here, you can actually browse the forums and the threads correctly, but not inside the forum's system...

Feedback on this issue would be appreciated

btipling’s picture

Has anyone fixed this yet?

patchak’s picture

Actually I found a way to workaround this bug... You have to go in the edit menu for a node, and then check the "leave link to message" or whatever it says exactly... By clicking this, your threads will become active and redirected to the forums interface...

It's not a fix but seems to work fine.

JirkaRybka’s picture

Status: Active » Closed (fixed)

This is a really old issue. Yes, the Category legacy code didn't import forums well. This was partially fixed on 5.x code in #158683: Import from Taxonomy - Forums (making this a duplicate), although I'm unsure whether it was officially released. For 6.x version, see #370631: Port category_legacy to D6.

Since 4.7.x is no more supported, I'm closing this one.