Working with two other plugins…

  • I have a question about two plugins, one of which it says it will work with and one that it doesn’t.

    A. TABLEPRESS

    I saw on the plugin site that it works with TablePress, and I got the “expand” and “respect” boxes checked and unchecked respectively. However, another section seemed to imply that if I index a page that has a table on it, but then later add more input to the table, then the index won’t know — if I understand correctly, it indexes the page and grabs the table data that is there, but doesn’t “refresh” if the table data changes.

    So, for example, I have a list of movie reviews at the above link, and so far I only have 8 in the list. Eventually I would like to have a LOT more. But if it indexes now, it will seem to find only the first 8. If I had another 100, is there a way to tell the plugin to JUST reindex a specific page? I have a couple of “index” tables like this.

    As you’ve replied on a few other queries, I’m not even sure I want that tabular data in this one to show up in the search but one of the others I do (it has some data that doesn’t show up in the linked pages).

    Can I index a page? Or do I just decide that once a month or once I do regular updates to those index pages I should reindex?

    B. For NEXT GEN gallery, I initially got a conflict error (it wouldn’t let me upload pics!). But in my indexing options, I changed it to only index post and page and exclude all NGG references, and unchecked NGG in taxonomies. With that done, NextGen went back to working normally. Is there anything else in Rav that is likely to throw conflict errors? I basically want it to ignore NextGen completely.

    Thanks,

    Paul

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Mikko Saari

    (@msaari)

    Correct –?when a TablePress table changes, the post that has the table doesn’t change, so no Relevanssi reindexing is triggered. TablePress doesn’t know which posts have the table, so it’s hard to fix.

    The easiest way to reindex a page is to go edit it and save it. That will trigger reindexing.

    There are couple of approaches for automating this. It’s possible to create a function that updates the post when a TablePress table is changed. The best solution depends on the number of posts involved and so on – if there’s a small number of tables and pages involved, it would be fairly easy to create a filter that would reindex page X when table Y is saved, for a small number of tables and pages.

    As for NextGen, it’s utterly hopeless. Just don’t touch anything NGG with Relevanssi and things will be smooth. If Relevanssi doesn’t index anything NGG related, there should be no problems.

Viewing 1 replies (of 1 total)
  • The topic ‘Working with two other plugins…’ is closed to new replies.