Recent searches

No recent searches

New request page custom work broken after API v4 upgrade

image avatar

Samuel Brown

Posted Jul 17, 2024

Hey everyone!

I've been re-theming our entire help center using the new v4 API, and everything was going great until I hit a snag with the new request form. Before, each list option on the form would grab the ID from the backend, making it super easy to spot and hide list items that weren't linked to a specific product. Here's how it looked before:

<li tabindex="-1" id="123456_administration" role="option" aria-selected="false">Administration Module</li>

With the upgrade, there are no meaningful identifiers on any of the list options. Now, I can't specifically target and hide them based on the product the user has chosen.

<div data-garden-id="dropdowns.combobox.option.content" data-garden-version="8.76.2" class="StyledOptionContent-sc-536085-0 cnRIZV">Training Product</div>

This seems like a massive oversight and I wanted to understand if anyone else is experiencing this issue and how you resolved it.

Cheers!

1

1

1 comment

Date
    image avatar

    Jehan Zebafridi

    It seems Zendesk has taken a step back in terms of customization. Previously there were classe with meaningful names and ids where you can identify/customize easily, and now they all have some random names like StyledField-sc-k7y10k-0 eZAVpC. Come on Team Zendesk. 

    0

    Please sign in to leave a comment.

    Didn't find what you're looking for?

    New post