Really like this module but what I am getting 2 list by term instead of one attached is a picture of what it looks like. any help would be great.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | cat's.jpg | 122.64 KB | tsavino |
| indexpageserror.jpg | 137.25 KB | tsavino |
Really like this module but what I am getting 2 list by term instead of one attached is a picture of what it looks like. any help would be great.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | cat's.jpg | 122.64 KB | tsavino |
| indexpageserror.jpg | 137.25 KB | tsavino |
Comments
Comment #1
nancydruWow, the dust hasn't even settled...
Are you sure you don't have two separate vocabularies names "usehpdocs?" I certainly don't see this on any of my 11 content types.
Can I see this on the live site? If not, can you cut and paste the output below
<div class="indexpage-node-index">, please.Comment #2
tsavino commentedSorry you can not see the site its behind a firewall:( but below is the code you wanted... if there is anything else you need just ask. Attached is a pic of my vocabularies names.
Comment #3
nancydruWow, that's not what I expected. But it shows you're right. And it's the basic "page" type. Very strange.
Comment #4
nancydruI think I have an idea. Can you tell me if you have another content type with "page" in the type (not the name -- e.g. book is the type, "book page" is the name)? I'm guessing you do, and it also uses the same vocabulary.
This can be fixed.
Comment #5
nancydruIt will be in the -dev version at noon GMT (8am ET).
Comment #6
tsavino commentedYes I did have 2 that had the ending with page so what I did was change the machine-readable name and now its fine thanks for the help and this module rocks so does the other modules you have done....thanks:)
Comment #7
nancydruThank you. I did make a change that should prevent this. For whatever reason, the original author used a LIKE clause in the SQL SELECT rather that an =. It took a little time to figure it out. And the funny thing is that I actually had almost the same situation on my site. I had two types with a matching string in them, but they weren't using the same vocabulary. But I didn't see that until after I had made the change.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.