Author Select Issue

  • Resolved hrood

    (@hrood)


    1 month ago

    I’m seeing a Gutenberg author selector bug with Index WP Users For Speed 1.3.1.

    On a site with ~587 author-capable users, searching for an author in the post editor returns the correct users from /wp-json/wp/v2/users, but the Gutenberg Author field displays “No items found.”

    Example:

    • Search: Todd
    • REST response body correctly returns:
      • Todd Meyer
      • Todd Rynaski
    • Response headers incorrectly report:
      • X-WP-Total: 587
      • X-WP-TotalPages: 6
    • Gutenberg’s core data resolver finishes but returns null.

    User permissions and core REST behavior were verified as correct. Disabling Index WP Users For Speed immediately fixes the Author selector; re-enabling it reproduces the issue.

    The problem appears related to the plugin’s rest_user_query / Gutenberg author-selection optimization and possibly its handling of totals for filtered author searches.

    I tried rebuilding the index, and that didn’t change anything. As soon as I disable the plugins, it works as expected.

    Not a huge priority for me, as I think this site can run fine without this plugin (I’m still using your other one), but wanted to share in case anyone else runs into the same thing.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author OllieJones

    (@olliejones)

    1 month ago

    Thanks for the defect report. I’ll check it out. Are you saying you access the REST endpoint directly and it works, but when the Gutenberg editor accesses it, it doesn’t work? Any more information you can offer on how to reproduce this will be helpful.

    I do test this particular path. I’ll try to reproduce your problem.

    Thread Starter hrood

    (@hrood)

    1 month ago

    My apologies, I forgot one important piece. This site runs Bricks for its theme, which does add some Javascript to the block editor. I didn’t catch this the first time, as I thought the error was coming from a core file.

    The REST endpoint works directly, but with the plugin active, opening Gutenberg on a Bricks site triggers a JavaScript error in bricks.min.js (document.body is null). Disabling the plugin prevents the error. Whether the error and the issue I am seeing are connected are directly related remains to be seen, but I am currently unable to test without Bricks on this particular site.

    This appears to be an interaction between the plugin’s REST/editor behavior and Bricks rather than a standalone REST failure.

    • This reply was modified 1 month ago by hrood. Reason: Added link to Bricks
    Plugin Author OllieJones

    (@olliejones)

    1 month ago

    I *think* there’s a change to the way the React stuff in the Gutenberg editor works. I’m trying to track it down now.

    Plugin Author OllieJones

    (@olliejones)

    3 weeks, 6 days ago

    Figured it out. Please see this. https://github.com/OllieJones/index-wp-users-for-speed/issues/33

    Fix forthcoming.

    Plugin Author OllieJones

    (@olliejones)

    3 weeks, 5 days ago

    Please try using version 1.4.1. And thanks again for the defect report!

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.