Alphabetical indexes are no longer accessible in 2.2

Ben, this might be a duplicate of http://drupal.org/node/441288. See the steps in comment #2 for a solution that usually works.

Thanks for the reply. I had seen that thread, so I deactivated the module, deleted it, unpacked a new copy from the tar.gz, and then re-enabled. No luck, unfortunately.

Maybe I'm misunderstanding "uninstall" and "reinstall"? (It wouldn't be the first time I got something simple wrong...)

Deactivating the module and deleting it is not sufficient to "uninstall" it. After disabling it, and before deleting it, you must click the Uninstall tab on the Modules page and Uninstall the module there. This deletes any database tables and entries that the module has constructed. When you re-enable the module, the tables will be rebuilt, and you can start over from scratch. You should be able to upgrade to the new version before you re-enable the module if you want.

Thanks for your continuing help with this. The "Uninstall" step had slipped my mind.

Unfortunately, there's clearly something I'm still not getting my head around: Since I had gone back to 2.1, I deactivated 2.1, uninstalled it, then deleted the module. Then I unpacked the tarball for 2.2, ran update.php, then activated 2.2... and then got stuck in a loop in which I kept getting referred to update.php to update the database to Vocabulary Index 2.

After a lot of trial and (mostly) error, I did get back to 2.1 again, where it's going to have to stay at least until next week when I have more time to work through what I've done wrong.

I'm changing the category to "support request," since I really think this is a mistake I'm making, rather than an actual bug. I'm also changing its status to "postponed," since I don't want it cluttering up anybody's issue queue if I'm not going to be able to respond for a few days. (I'm expecting that, once I actually have some time to sit down with this and work through it more deliberately, I'll be able to move it to just-plain closed, with apologies.)

This is definitely a bug of some sort with the "Alphabetical" view option in 6.x-2.2, so I've changed the status back (hope this is okay with you, Ben).

Here's what I did (Ben - note order of #2 and #3):

1. Disabled 6.x-2.1 and Uninstalled it
2. Uploaded 6.x-2.2 and enabled it
3. Ran update.php after enabling module, but it did not take any action on Vocabindex module.
4. Built an Alphabetical view, and the link to the path resulted in Page Not Found.
5. Disabled 6.x-2.2, Uninstalled it, then renabled it.
6. Built a Browsable view, and it worked fine.
7. Changed to Tree view for same vocabulary, and again it worked fine.
8. Changed to Alphabetical view, and the link to the path again resulted in Page Not Found.
9. Disabled and Uninstalled 6.x-2.2 and re-uploaded 6.x-2.1 and enabled it, configured an index for the same vocab using an Alphabetical view setting, and it worked as expected.

(Setting Cache Lifetime to zero and clearing cache did not help in any of the above steps.)

If you keep seeing a message telling you to update from version 1 to 2, this is certainly a bug, although perhaps not the one you thought it was.

The step by step instructions are great! However, we need a solid way to reproduce these problems with a clean install, you could you rewrite the instructions using 6.14 and 6.x-2.1 and upgrade to 6.x-2.2 in the process?

Thanks very much for this--as I said, I'm going to be away for a few days, but will look to see if I can reproduce the issue when I get back next week.

I will try to do what I've posted in #5 again as requested in #6, but first I've got to upgrade my "clean install" testbed to 6.14, so it might take a day or two...or three...or...

A clean install means an install from scratch. Best and easiest is if you set up a local web server (Just install Xampp/MAMP locally) and install Drupal there.

I all, I have the same issue.

Steps I've done are the following:

1) Upgrade to Drupal 6.14
2) Upgrade to Vocabulary index 6.x-2.2

Results:

All works fine eccept when i set alphabetical visualization. Only in this case I receive a 404 page not found

Browsable view -> ok
Tree view -> ok
Alphabetical view -> doesn't work: i can't view the page (error 404)

I also tried to disable/unistall/reinstall module but with not success.

Thank you for your work

MXT

"could you rewrite the instructions using 6.14 and 6.x-2.1 and upgrade to 6.x-2.2 in the process?"
"A clean install means an install from scratch"

Okay, I have tried to do exactly what Xano has asked in the above quotes from #6 and #9. Note that unlike what MXT has reported in #10, I am describing a completely virgin install, from scratch, not an upgrade from 6.13 and/or 2.1.

1. Created a new, empty mySQL database
2. Uploaded 6.14 and installed it to a new directory under public_html, set up .htaccess and settings.php, ran install.php, all of which went normally
3. Logged in as Admin (user 1) and created new vocabulary (structure not relevant at this point due to errors described below).
4. Uploaded vocabindex-6.x-2.1.tar.gz (note - 2.1, since Xano had asked that we reproduce the upgrade problem.
5. Went to modules page and enabled Vocabulary Index. Did not get any errors, but, as reported by Ben in #4, immediately got the following message in red warning area at top of page:

6. Ran update.php as instructed, got 0/0 results, but "Please proceed to update..." message would not go away
7. Went to /admin page, looked for Vocabulary Index entry so I could configure an index, but Vocabulary Index was not listed on admin page.
8. Went to phpMyAdmin and verified vocabindex table was in database
9. Went to Modules page, disabled vocabindex, uninstalled it, re-enabled it. Same results as already described.
10. Went to /admin/help, found entry for Vocabulary Index, went there, clicked "Create index pages", was taken to /admin/build/vocabindex/pages, but saw screen as attached and could not find a vocabindex configuration page anywhere.
11. Went to Modules, disabled Vocabindex, uninstalled it, removed folder from sites/all/modules, uploaded vocabindex-6.x-2.2.tar.gz, went back to Modules, enabled Vocabindex, and what is described above in steps 5-10 happened again.

Conclusion: Cannot install vocabindex 2.1 or 2.2 on a virgin 6.14 system. Until this bug is fixed, no further testing can be done to try to reproduce the "disappearing alpha index problem" under 6.14.

Over to you, Xano...

Attachment	Size
Build-VocabIndex-Pages.jpg	129.47 KB

I'm renaming this issue because we have gone from a bug in the alphabetical pages to a little too effective upgrade instruction message. I'll fix the problem with a new release this weekend. Thanks for reporting it!

Ladies and gentlemen! We got a patch! This one's for D6, could you please test it?

Attachment	Size
remove_schema_update_d6_00.patch	2.96 KB

Should the patch be applied to 2.1, 2.2, both, either????

Version 2.2. 2.1 is unsupported now that 2.2 is out.

"Version 2.2. 2.1 is unsupported now that 2.2 is out."

Okay, I will try to test the patch against 2.2 within the next 24-48 hours, but since the patch applies only to 2.2, it will not be possible to reproduce the problem as a function of an upgrade from 2.1 to 2.2, as previously requested. I will only be able to test whether the patch fixes the "Alphabetical index page stops working with 6.x-2.2?" problem on a virgin 6.14 + 2.2 install.

Download 2.2 and apply the patch before updating to it.

1. Uploaded and unzipped unmodified vocabindex-6.x-2.2.tar.gz to sites/all/modules on a clean 6.14 installation
2. Uploaded remove_schema_update_d6_00.patch to vocabindex directory
3. Went to vocabindex directory and ran patch -b < remove_schema_update_d6_00.patch > patch_results.txt
4. Patch failed - see attachments

What next?

Attachment	Size
patch_results.txt	196 bytes
vocabindex.module.rej_.txt	1.11 KB

No patch I make can be applied. Something's wrong somewhere. Until I figured it ouy you'll have to apply the changes to vocabindex.module manually.

"No patch I make can be applied."

That's going to make things difficult, both now and in the future. I for one don't want to try to do a manual patch, as the process is time-consuming and very subject to error.

Xano, can you possibly find, or ask for, some help at http://drupal.org/patch/create?

It's just this patch that fails. The reject file is small and simple enough to apply manually.

Subscribing. Have the same problem. Updating to 6.x-2.2 results in loss of alphabetical listing function.

Just to be clear: if nobody tests the patch it can never get committed.

"if nobody tests the patch it can never get committed"

If the patch cannot be applied (through normal means), it cannot be tested. You can't really expect us to apply it manually, as that is labor-intensive and very prone to error, especially if one does not understand or have the time to learn how to read and dissect a patch file. Please provide a patch that works.

@BayouBill: you seem like someone who can apply patches to me. As you might have seen this patch is very small and very simple. I already explained that CVS does not generate a working patch file. This means people can either apply the patch manually and test it or do nothing and the patch will never get committed.

Xano, please email me via my Contact tab, so we can continue this dialog offline (will need your email address, since your Contact tab is not enabled). Thanks.

There is a reason my contact form is disabled: my work here is voluntary. There is the issue queue or IRC if you want to talk to me about Drupal-related things.

There is nothing to discuss here. I'm not angry, I'm not trying to offend anyone. I'm just saying that if any of you want this fixed, I need to know if this patch works or not. I explained why the patch doesn't apply and I also explained that it's an easy one to apply manually. There's nothing that can change that.

Attached you will find the manually patched file (/sites/*/modules/vocabindex/vocabindex.module. Back up the old file, rename this one to vocabindex.module, replace the original with it and test the module. After you're done, you can revert the backup. If anything goes wrong, please provide a detailed a report as possible.

Attachment	Size
vocabindex.module.txt	19.08 KB

The vocabindex.module attached to #27 solves the problem reported as Conclusion: in #11, namely, that the module cannot be installed on a clean Drupal 6.14 system. The module can now be installed.

However, it does not solve the problem confirmed in #5. It is still not possible to construct an alpha index with this version of the module. If an alpha index is constructed, the link to it results in Page Not Found. Tree and Browsable options work okay.

Changed issue title and status to reflect the current situation.

Is this after a clean installation? If not, have you rebuilt the menu by going to the menu page?

"Is this after a clean installation?"

Yes.

"have you rebuilt the menu by going to the menu page?"

After the clean install failed to produce an alpha index, I disabled and uninstalled the module, then re-enabled it. Still could not build an alpha index.

I hope I won't be muddying the waters here, but finally had a little bit of time to devote to this, and wanted to report what I'd seen.

1) Downloaded 2.2 and unpacked it to my desktop.
2) Removed vocabindex.module from the unpacked folder and replaced it with the patched version from #27 (thanks for that--me trying to apply even a simple patch manually would not have been pretty). NOTE: This is all still on the desktop

3) On mirrored testbed version of my live site, deactivated 2.1, then uninstalled it.
4) Moved patched version of 2.2 to sites/all/modules on testbed site, then enabled it.

5) At this point I DID NOT get the "Please proceed to update.php to update your database to Vocabulary Index 2" that BayouBill reported at step 5 in #11, above, but got a friendly green "Vocabulary Index has been enabled. Please proceed to the settings page and set up the permissions to get started."

6) Pondered. Uh, okay... Guess I won't run update.php, just to see what happens.

7) Visited settings page (changed one setting to 0 to eliminate paging), then permissions page (permissions still intact--perhaps persisting from 2.1?)

8) Added a vocabulary index for one taxonomy using the Alphabetical view with node counts. Following the path still produces a "Page not found," as in my original post (and as I think BayouBill also saw in #5 and #28).

9) Tried both Tree and Browsable views, and both worked properly.

So, I don't know... The patch from #27 certainly makes it *appear* that an upgrade from 2.1 to 2.2 went without any hiccups (recall that I never ran update.php, since I never saw an instruction to). But the Alphabetical index issue still seems to be with us.

I'm sorry for the delay in responding on this, but I'll be happy to follow any further instructions for testing (run update.php, perhaps?).

Fact is, that the release 2.2 won't work on a fresh drupal installation if you have already some taxonomy in the database unless you replace the vocabindex.module with the one mentioned in #27.

My vote for committing this immediately.

After installing for the first time this module, I had the same issue. I received the warning that I had to upgrade to "version 2" by going to update.php. Going to update.php obviously didn't help.

After replacing the original .module with the one provided in comment #27 the problem resolved.

The instruction message issue has been moved to #601138: Upgrade instruction message is too persistent. We will continue here with the alphabetical index problem. Thank you for pointing out these two issues were not related.

I tried reproducing the issue with a clean install of the latest Drupal 6 and Vocabulary Index 6.x-2.x and creating an alphabetical index went without problems. Could you do the same with a clean installation next to your current website and see what happens? Something may have been changed in the latest development version that fixed this issue as a side effect.

I'll set up a clean install on my testbed machine to check it out. I'll try to do it tomorrow (Monday, October 12), but it might have to wait until Tuesday.

I'm afraid I have nothing good to report:

I just installed a clean instance of Drupal 6.14, created a new vocabulary, and installed Vocabulary Index 2.2-dev. The install appears to go successfully, but when I go to the page to create a new Vocabulary Index, I get a red error box at the top that says this:

That was a new one on me. Vocabulary Index 2.2-dev is the only contributed module installed.

Please let me know if there's more testing I can do on this.

After some more thinking, I realized I wasn't 100% sure what Xano wanted tested against a clean install in #35: 2.2 with the patch from #27 or 2.2-dev. So I should also report:

Before trying out 2.2-dev (as described in #37), I had first installed a clean instance of Drupal 6.14, created a new vocabulary, and installed 2.2 with the .module file replaced by the patched version from #27. The installation went fine, but the Alphabetical index wouldn't work. Tree and Browse views were fine, but no luck with Alphabetical index. So I didn't have the same luck that Xano reported in #35.

After this attempt with the patched version, I deleted the entire instance of 6.14 and dropped the database so that I could start from scratch. What I described in #37 was thus on a totally new install with a new database.

So I guess I have two things to report:

1) The patch from #27 doesn't seem to have quite solved the alphabetical index problem in my tests; and
2) 2.2-dev seems to create a different problem with a clean install of Drupal 6.14.

I'm happy to do more tests, if somebody will point me in a direction.

The path from #27 has been committed and now has an issue of its own: #601138: Upgrade instruction message is too persistent. This was done between comments #34 and #35. This means that the upgrade message no longer appears if you download 6.x-2.x-dev.

I will check out the errors reported in #37 asap.

Ah, okay--sorry if that slipped past me. (I can confirm that I didn't see the upgrade message when using 2.2-dev. But then you knew that!) Thanks for your work on this.

I have a same problem!
Browsable view -> ok
Tree view -> ok
Alphabetical view -> doesn't work: i can't view the page (error 404)

I just tried again with a clean installation of Drupal and Vocabulary Index, but the alphabetical indexes do work. I'm sorry, but if I can't reproduce the problem unfortunately I cannot fix it.

Xano, do you have any sense of issues that might be coming in to play when dealing with an upgrade from 2.1 to 2.2 when dealing with an existing vocabulary? (I mean as opposed to a clean installation.)

If things are working with clean installations, then that should cover anyone coming to Vocabulary Index for the first time. It sounds like several people are in the position I described initially, though: using 2.1 on a live site, and unable to upgrade to 2.2 because of disappearing Alphabetical indices. Any further information we could provide to help you see what's going on? It sounds like it must be a pretty elusive problem, and I appreciate all the work you've put into trying to track it down.

I missed that part. Marking this as active. I'll test some more with upgrading Vocabulary Index.

Thanks very much--if there's any information I can provide, please let me know (though I'm afraid you'll have to tell me where to look).

Subscribing. Mine did not work on clean install (v2.2 on drupal 6.14).

I repeat: Use the development version to confirm if a bug still exists or not.

Yes, with the development version all work fine!

Alphabetical view is now visible.

One thing, after running update.php I've obtained some errors (see the attachment please).

I don't know if those errors matters with our issue.

Thanks for your work

MXT

Attachment	Size
screenshot-drupal-update.jpg	117.69 KB

Okay, I'm not sure what's happened since the last time I tried this, but I thought I'd report:

I just updated a local mirror of my existing site using the development version, dated November 9, 2009 and following the steps that Bayou Bill outlined in #5 above...

And it worked. The alphabetical page view appears just fine, and I didn't get the error messages that MXT reported in #48. (Note, this is an existing site with existing vocabularies, as in #43.)

One note: I didn't receive an instruction to run update.php (as per Xano in #39), but ran it anyway (following #5). At least in the case of my site, the dev version sure seems to have solved the problem.

Many thanks to Xano for all the work!