IndexPress no longer works, in particular, with custom post types in WordPress 3.5
The developer is aware of the issues, but updates are on permanent “back burner” status. This plugin can be considered more or less abandoned.
]]>Nice plugin – thanks!
Unfortunately, the plugin seems to pick up instances of a word within the theme primary navigation bar – not just from the main content loop
]]>not working with custom post types?
]]>This plugin is a cool idea. I actually looked for the plugin after seeing a similar tag page on a blog (though I don’t think that blog used this particular plugin).
Anyways, this was the result:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 30346370 bytes) in:
/…/…/…/wp-content/plugins/index-press/index-press.php on line 388
For my site: Hive Health Media
]]>Good plugin – but here’s a suggestion.
– Allow the user to limit the index output to a certain parameter, IE: words that fall within ‘<h1>’ or ‘<h2>’ or anchors. This would allow business orientated pages to have an auto-updating index with little fuss.
For example, say it does its thing and you have it limited to H2 headings and master pages. It finds two h2 headings on the About Us page, one of them has an anchor .. It’d output:
A:
About Us (this is the master page link)
– Locations (has no anchor, so it uses the About Us page link)
– History (has an anchor, so it appends that onto the About Us page link)
It’d also need to be able to do the entire string between the headings, so if it was <h2>History of Our Company</h2>. It’d output all four words.
Just a thought. I haven’t found a plugin that does this automatically yet if you’re using anchors instead of complete subpages.
]]>I received a memory allocation error indicating this plugin after updating to 3.2.1 and attempting to edit an existing post. I disabled the plugin and all was fine.
]]>Have you an idea when your plugins support the custom post type ?
thanks.
what a crazy list, why would anyone want to index by every word in every post? was hoping for a simple index of posts by title, this is overkill.
]]>