500 Internal Server error when indexing all custom fields

  • Resolved Joe Alberts

    (@joe-alberts)


    8 years, 5 months ago

    There’s a number of variables at play here, and I haven’t tracked down most of them, but I’m seeing an Internal Server Error (500) on a site running Cornerstone (a page builder) when trying to save through that interface. The changes to the page thus fail to save.

    Of particular note, however, is that it’s only happening when indexing all custom fields. I’m using a number of hidden custom fields throughout a couple of CPTs on this site. It looks like it’s completely fine if I pass a list of (at least some) of the fields. I suppose it’s possible that it’s having a problem with one or two particular fields.

    I didn’t remember having this problem before, so I rolled back from v.3.5.4 to v.3.5.3. Rebuilt the index with the same settings (all custom fields), and retested it without any 500 errors. So the only conclusion I can draw is that there’s a bug (or conflict with Cornerstone) with a change that happened in the v.3.5.4 release of Relevanssi.

    Any suggestions on additional info I could provide to help track down this apparent bug?

    • This topic was modified 8 years, 5 months ago by Joe Alberts.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mikko Saari

    (@msaari)

    3.5.4 indeed has a bug that causes indexing to fail if you have an array in a custom field.

    Here’s a new version of indexing.php. If you replace the current one with this, does the problem go away?

    Thread Starter Joe Alberts

    (@joe-alberts)

    I’ll test it out first thing tomorrow.

    Several of the fields are serialized arrays, and I neglected to test passing one of those to the custom field index. So, it stands to reason that this is the problem I’m seeing.

    Will update with test results.

    Thread Starter Joe Alberts

    (@joe-alberts)

    So far, so good. Just updated my test site to 3.5.4, overwrote the indexing.php file, and things are saving successfully through the page builder interface. No 500 errors!

    Thanks!

    Plugin Author Mikko Saari

    (@msaari)

    Good! This fix will be included in the next version.

    Thread Starter Joe Alberts

    (@joe-alberts)

    Glad to hear!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘500 Internal Server error when indexing all custom fields’ is closed to new replies.