HiveNest docs
Compatibility Check.
HiveNest includes a Compatibility Check screen in WP Admin → HiveNest → Compatibility. It analyses every rule and gives each a clear status so you can spot why a rule is not behaving before you go hunting on the front end.
What it checks
Missing attributes
Confirms the trigger attribute and every child attribute in a rule still exist in HivePress. Attributes get renamed or removed over time; a rule pointing at one that no longer exists can never match.
Trigger values
Checks that the value your rule compares against actually exists as an option on the trigger attribute. This is the most common cause of a rule that never fires — see the note on Select2 term IDs below.
Child attributes
Verifies the fields a rule shows are real, editable attributes assigned to the relevant listing category, so HivePress actually renders them on the form.
Submit / edit form scope
Each rule targets the listing submit form, the listing edit form, or both. The check flags a rule whose scope will not match where you expect the fields to appear.
Common warnings
Attribute not found
The trigger or a child attribute was deleted or renamed in HivePress. Edit the rule and re-select the correct attribute.
Trigger value has no matching option
The value in your rule does not match any option on the trigger attribute. Re-pick the value from the rule editor so it stores the correct term.
Child field not on this category
A child attribute is not assigned to the listing category being submitted, so HivePress never renders it. Assign the attribute to that category in HivePress.
Rule scope may not apply
The rule targets a form (submit or edit) different from where you are testing. Adjust the rule scope or test on the matching form.
Select2 and term IDs
Many HivePress attributes are dropdowns (Select2) backed by taxonomy terms. On the form, the selected value is submitted as a numeric term ID even though the label reads, say, "BMW". HiveNest matches term IDs, slugs, and labels, so a rule set to Manufacturer = BMW still fires. If the Compatibility Check flags a trigger value, re-select it from the rule editor so the correct term is stored.