Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • By the way @rfischmann,

    The Merge request was approved and merged. It should go live with version Gutenberg 8.9.

    Gutenberg is now at version 9.0 on their own plugin install. I tested and the plugin DOES hold my change and works.

    Although, it seems like WordPress itself does not load the full latest Gutenberg. WP Team seems to pick what should go core and what shouldn’t. I do not know when/if this will exactly be available in WP Core. My changes are not in the latest version (Sept 1)

    For now, you should be able to add the Gutenberg plugin and have the changes working.

    You could apply them at your install, but I would not advise you so. I am trying to escalate this so it gets merged before end of September.

    I am a Web Dev, working as one. But I am not pretty advanced in React itself, which Gutenberg is built mostly with.

    There is some PHP around it, but most of Gutenberg is built over React, which is a JavaScript Library.

    I checked to see if I could build a plugin on the side, that would change the query param, but to no avail. It might be because I know not enough in React, or because I gave upjust too soon. I thought the fix should be core first, since it was an error in implementation, not a “feature” or “improvement” my situation called for.

    Calling for infinite (all) tags is an error if you are to display/offer only 20.

    I still do not think we could inject ourselves into Gutenberg query param easily, I did try, but did not achieve it.

    To note: I am specialized in server side language, not frontend.

    Nope.

    My branch works perfectly, limited the AJAX call to 1 per search (blur event, after 3 character entered) and did put a minLenght to 3 characters. But the Merge request (https://github.com/WordPress/gutenberg/pull/23841) is still on going. I’m struggling to get this approved.

    I pushed a new fix 2 days ago, both dev checking it are like “Sure, good, but change a constant there”. We’re in the fine tuning phase I think.

    I too would like to see this go live. This is a major problem to us, and probably our last one.

    To that last editors replies, around the number of tags VS the number of requests:
    I created a bug on the bug tracker of Gutenberg, seems like it is separate from WP.

    https://github.com/WordPress/gutenberg/issues/20734

    I was in the same situation as @ddrager, @rfischmann, @plagiarismtoday and @bob447 amongst others.

    I already have a contributor commenting on possible solution. In the meantime I am trying to AT LEAST have the React components doing the Autocomplete to be set at minLenght:2 OR to cancel the following requests (perpage:100).

    Sidenote, I would not recommend increasing the page size for blogs…as this might just be kicking the can down the road. A contributor suggested infinite scrolling or the tags list, that would be a great idea IMHO.

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