After moving to a new host, Image Gallery admin now shows wrong taxonomy terms
ToonDawg - September 29, 2009 - 03:22
| Project: | Image |
| Version: | 6.x-1.0-beta3 |
| Component: | image_gallery |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
After upgrading to Image 6.x-1.0-beta3 from beta2, when I go to administer the Image Galleries (/admin/content/image), the taxonomy terms from my Story type content are listed instead of the Image taxonomy terms. I can still add Image Galleries, but I have to do it by adding a term in the taxonomy administration section.
#1
I apologize - after moving hosts (not upgrading - I was already on beta3) and importing my db into the new host, I am having this issue.
I changed the category from bug to support request.
#2
I have experienced a similar issue. In my case, the Image Galleries vocabulary is getting mixed up with the Forum vocabulary, so that when i go to
/forumor/forum/*, I get the image galleries – but themed as the forum.The modules I am using which might have something to do with it are:
Pathauto
Image
Forum
Taxonomy
#3
Note: I am using the lates dev version of image.module.
Attached an image of what my pathauto settings look like. As you can see, the place where "Image galleries" should be, now shows "Forum", in addition to the separate "Forum" container further down.
This might very well be a Pathauto issue. I'll look into it some more later today.
#4
Check the value of the image gallery vocab variable too. It may have got confused and be pointing you at the wrong vocabulary.
#5
I am still a little new to Drupal - how would I go about checking the variable value? Thanks for your help.
#6
Install the devel module, use the variable editor.
I don't remember the exact name of the variable, but it's fairly obvious which one you'll want -- has 'gallery' in it.
#7
The variable was the source of my problem. Updated it (i had to update both the forum variable and the gallery variable), and everything works.
#8
#9
Thanks, that did it for me!
#10
It would be great if someone who's foudn this problem and fixed it could add a brief note to the troubleshooting page: http://drupal.org/node/470724
#11
Done - although it was already in there.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.