Unable to manually assign a vendor to a listing

General HivePress
1

Hi, I’m unable to assign/change the Vendor field on a Listing from wp-admin — the field (select2) stays greyed out / locked to the current WP user’s own vendor profile. This affects both new Vendors and a Vendor/Listing pair that was working correctly for weeks before (confirmed functional previously, broken now).

Already verified without success: Listing status Draft; target Vendor’s linked WP user has Contributor role; Vendor correctly linked to its WP user via the Vendor’s “User” field; Vendor has a category assigned; no JS errors in browser console when interacting with the field; rolled back HivePress from 1.7.26 to 1.7.15 — issue persists identically on the older version too.

Since the older version doesn’t fix it, this doesn’t seem to be a simple version regression. Could this be related to a server-side capability check, a conflict with another plugin, or something else entirely? Happy to share more details/screenshots.

Site: WordPress [versione], Kadence theme, HivePress (currently 1.7.15 after rollback), Contact Form 7, Rank Math SEO, Iubenda, SiteGround Speed Optimizer + Security Optimizer active.

2

Thanks for your message — our team will reply shortly.

In the meantime, you can also get instant help from our AI Assistant, familiar with all the docs and solutions we’ve shared over the years.

3

Hi @samuele,

I just tested reassigning a listing to another vendor via the WordPress back-end, and the changes were applied successfully after saving. The front-end reflected this as well.

I am also using SiteGround for my hosting, so that helps rule out anything on their end as the culprit.

I began my HivePress journey using the Kadence theme. However, it isn’t 100% compatible at the moment (or at least when I last checked), and I found many alignment and styling issues, alongside problems with the header.

Ultimately, I switched to ListingHive to save any more headaches and avoid fighting a conflict. I did request that the Kadence team consider adding better compatibility, but I am not sure if they ever got round to it.

The Kadence company was also bought out recently, and, sadly, their best developer has now left the team.

You can, however, use Kadence Blocks. The only bug I have found is that whilst editing a page in the back-end, if you set a row width to full width, it does not position itself correctly on the editing screen. It still works as intended on the front-end, though.

It does not sound like you have many plugins active at the moment, but to rule them out as conflicts, you could try deactivating all non-HivePress plugins to see if the issue persists.

You can then reactivate them one by one to figure out where the conflict stems from.

Similarly, you could also try switching themes temporarily to see if this resolves the issue.

I hope this helps!

Cheers,
Chris :victory_hand:

4

Hi Chris,

Thanks for the detailed reply and for sharing your own experience with Kadence — really appreciated. Wanted to give you (and anyone from the dev team who might pick this up) a full update, since this has turned into a fairly deep investigation.

Theme test result: I switched to the default Twenty Twenty-Four theme to test your Kadence compatibility theory. The issue persists identically — so in this specific case it’s not a Kadence conflict. Good to rule that out with certainty, though I appreciate the heads-up regardless, since it clearly is a real issue in other setups.

Full list of what’s been ruled out so far, for anyone jumping into this thread:

  • Listing status: confirmed Draft

  • Vendor’s linked WP user role: confirmed Contributor

  • Vendor-User linkage: confirmed correct via the Vendor’s “User” field

  • Vendor category: was empty (never populated), created and assigned one — no change

  • Reserved attribute field names: no custom Vendor attributes exist at all, so this isn’t it

  • HivePress version: rolled back from 1.7.26 to 1.7.15 via WP Rollback — issue persists identically on the older version too

  • Theme conflict: tested both Kadence and default Twenty Twenty-Four — same behavior on both

  • Plugin conflicts: isolated every active plugin one at a time (SiteGround Speed Optimizer, Contact Form 7, Rank Math SEO, Iubenda) — issue persists with each individually disabled

  • Browser extensions: tested in Incognito mode — same result

  • Browser console: no errors at any log level (including Verbose), no matter how I interact with the field

  • Network tab: with cache disabled, clicking the Vendor field generates ZERO HTTP requests — not a failed one, none at all

  • JS loading: checked the Network tab filtered to JS during a full page load — didn’t spot any HivePress script returning a 404 or failing to load

  • Hosting-side: SiteGround checked their end directly — no mu-plugins, no cache drop-ins (advanced-cache.php, object-cache.php, db.php), no relevant entries in PHP error logs, and Speed Optimizer isn’t even registered as installed on their infrastructure side

The most useful clue is probably the Network tab result: since no request is ever sent, whatever is preventing the field from being editable is being decided entirely client-side, before any AJAX call would even be attempted. That suggests some condition or flag evaluated on page load (rather than a live permission check against the server) is what’s blocking initialization of the field as editable.

One more relevant detail: this isn’t limited to new Vendors. A Vendor/Listing pair that was working correctly for weeks stopped working after HivePress auto-updated itself (auto-updates had been disabled on purpose, got re-enabled by accident). The rollback to 1.7.15 didn’t restore the old behavior though, so it doesn’t seem to be a simple version regression either.

If it’s helpful, I’m happy to share the exact HTML/attributes of the greyed-out field, or dig into any specific JS variable or hook you can point me to — just let me know what would be useful to look at.

Thanks again for all the help so far,
Samuele

5

Hi,

Thanks for the details.

In order to change the vendor, the listing needs to be published first. Once it is live, the vendor field will become active and you will be able to assign the desired vendor.

You can assign the vendor once the listing is published, and then change the listing status back to draft if you want to keep it hidden.

Hope this helps

6

i Kseniia, Thank you so much — this was exactly it. I tested it a few minutes ago: published the listing, the vendor field became editable immediately, assigned the correct vendor, then switched it back to draft (and separately confirmed that setting visibility to private after publishing also keeps the field’s assignment intact once it’s been set). For anyone finding this thread later with the same symptom (vendor field greyed out, zero network requests on click, persists through plugin rollback/reactivation): this is the fix. The field only initializes as editable when the listing is published and public at page load — draft/private listings load it in a locked state by design, not as a bug. Really appreciate you and Chris both taking the time on this.

Thanks again

2 Likes
7

Glad to help! And by the way, welcome to the community :herb:

If you find HivePress useful, we would really appreciate it if you could take a moment to leave a review on the WordPress repository or Trustpilot. Your feedback means a lot to us and makes a real difference in helping us grow.