If you are having problems with installing or activating the latest version of AZIndex (0.7.4), and you are an advanced WordPress user, I need your help in trying to track down the problem.
If you see the error message when you go to the AZIndex settings page:
AZINDEX_PLUGIN_ERROR: The required AZIndex database table – wp_az_indexes – does not exist. Please deactivate then re-activate the AZIndex plugin to correct the problem.
and it doesn’t go away when you try reactivating, I would like to know the following information:
- the version of WordPress you are running
- the version of PHP you are running
- the version of MySQL you are running
- run PHPMyAdmin and take a look at your WordPress database tables — is there a table called something like wp_az_indexes in there? (It might have another prefix like wp_xxx_az_indexes).
If the table does not exist, then there is an additional step I would like you to try, but *only* if you are an advanced user and are confident that you know what you are doing.
Please would you try manually creating the AZIndex database table into your WordPress database using the following SQL statement: (Note: this is not a destructive SQL call, so it should not harm your WordPress database but, again, only attempt this if you really do know what you are doing!!):
CREATE TABLE wp_az_indexes ( name text NOT NULL, idindex int NOT NULL, categories text, tags text, heading text, subheading text, description text, cols tinyint, headingseparator text, itemsperpage smallint, ignorechars text, nlslocale text, nlsequiv text, customcsssingle text, customcssgroup text, customlinks text, customsort text, options set('child-cats', 'include-pages', 'include-pages-exclude-posts', 'multipage', 'multipage-links-above', 'multipage-links-below', 'group-subhead', 'alpha-head', 'alpha-head-page', 'alpha-head-col', 'add-spaces', 'alpha-links', 'alpha-links-unused', 'alpha-links-two-rows', 'ignore-chars', 'non-alpha-end', 'nls', 'nls-equiv', 'nls-locale', 'custom-css', 'custom-css-striping', 'custom-links', 'custom-sort', 'disable-cache'), itemcache mediumblob, linkcache blob, PRIMARY KEY(idindex)) DEFAULT CHARACTER SET utf8;
and if that doesn’t work, please try without the ‘DEFAULT CHARACTER SET utf8’ at the end:
CREATE TABLE wp_az_indexes ( name text NOT NULL, idindex int NOT NULL, categories text, tags text, heading text, subheading text, description text, cols tinyint, headingseparator text, itemsperpage smallint, ignorechars text, nlslocale text, nlsequiv text, customcsssingle text, customcssgroup text, customlinks text, customsort text, options set('child-cats', 'include-pages', 'include-pages-exclude-posts', 'multipage', 'multipage-links-above', 'multipage-links-below', 'group-subhead', 'alpha-head', 'alpha-head-page', 'alpha-head-col', 'add-spaces', 'alpha-links', 'alpha-links-unused', 'alpha-links-two-rows', 'ignore-chars', 'non-alpha-end', 'nls', 'nls-equiv', 'nls-locale', 'custom-css', 'custom-css-striping', 'custom-links', 'custom-sort', 'disable-cache'), itemcache mediumblob, linkcache blob, PRIMARY KEY(idindex));
If my theory is correct, you should get an error message when you try this statement in MySQL (if you are having problems activating AZIndex). If you could report back what the error message is, that would be a great help to me in debugging the problem.
When I upgraded the table wp_az_indexes disappeared
When I reinstalled the azindexes version 0.5.4 the table reappeared in the database, but it remained impossible to ‘add new’ indexes. When I click the button ‘add new’, nothing happens 🙁
I installed version 0.6.3 and hooray! It works again! I only had to recreate the indexes, but since I didn’t change a lot to the lay-out, that was only a matter of minutes.
Excellent plugin (when it works ;-)!
Hey Bart, sorry to hear about your troubles, but I am glad that you’re up and running again.
I have decided that the best way to resolve these missing AZIndex table issues is to overhaul the code that upgrades the database table so if something goes wrong, you can always revert back to the previous version of the plugin without losing the settings. It’s something I should have done ages ago, but nobody ever had a problem before this latest set of upgrades, so I just ignored the issue.