-
We have a large site built in GP including several custom post types and taxonomies. On a custom post type of ‘Products’, we are using a Query Loop block to bring in related press releases (‘post’ post type). When trying to use the default ‘tag’ taxonomy and add a term, the list goes transparent and shakes. If you try to type in a tag name, the block throws an error.
Screencast of issue here: Video
-
Hi Noc,
If you type the slug or the ID of the tag, does it work?
-
No, which is demonstrated in the screencast (I think). Typing it in if that flyout is shaking causes a crash as well.
-
Hi there,
its a known bug and we are working on a fix for that in the next update.
If possible, increase the height of the browser or reduce the zoom, to avoid the Select Box list from hitting the bottom of the browser which is what causes the error.
-
Any idea when there may be a fix? We have this reported by a client and it is hindering their ability to finish importing content in their site and launch.
-
No definite time frame as yet, these kind of editor bugs are a headache to fix. But we are working in it.
Can you try the zoom out on the browser so the select doesn’t hit the browser edge for now ?
-
I did try that, and even at 50% zoom it still hits the frame as it’s a pretty long list.
-
Odd, as the List is meant to be limited to a set number of results. Which browser are you working with ?
Also, Let me talk with the team to see if theres a short term fix.
-
I am in Chrome (latest version) on Mac OS Ventura. I am not sure what our clients are using but I am pretty confident it is Chrome as well, most likely on Windows.
Having tried it again zoomed out it does look like that is working. Apologies, I ran through so many different things to make this stop I must not have zoomed out enough. We did pass that tip on to our client and hopefully that’s an acceptable workaround until there’s a fix.
Thank you!
-
OK, let us know how you get on. We will get a fix out as soon as we can.
Apologies for any frustration caused. -
No worries, appreciate your assistance.
I’m not going to mark this as resolved yet, since there’s no fix in place, only a workaround (zooming out). Once a fix is in place I’ll resolve this thread. Thank you for your time!
-
We have the issue listed in our GitHub so you can close this topic is its not required for us to track the issue.
- You must be logged in to reply to this topic.