Skip to content
Data Where
Settings reign_options['wcfm_option'] (the 1.x key; only values that differ from the default, plus _v)
A member’s favourites User meta rwcfma_favourite_products (the 1.x meta), a list of product ids, capped at 200
Activity entries BuddyPress activity, types wcfm_product_create, wcfm_product_review, wcfm_order_create
Favourite request AJAX action product_mark_favuorite (the 1.x name, spelling included; login and nonce required)

| Purchase clean-up flag | Option reign_wcfm_orders_hidden, set once after the one-time hide of purchase entries posted by earlier versions | | Upgrade marker | _v inside reign_options['wcfm_option']. On the first load after updating from 1.x, a switch that 1.x left unset and whose 2.0.0 default is on is stored as off, so the site keeps what it had. | | Profile tabs | BuddyPress nav slugs favourite (position 80) and store (position 81) | | Activity contexts | Entries are registered for the activity, member, member_groups and group filter contexts | | Assets | Style and script handle reign-wcfm-addon (the reign-wcfm handle belongs to the theme). Loaded only where a heart or a profile tab prints. |

The heart posts product_id, favourite (1 to add, anything else to remove) and the nonce to admin-ajax.php. Possible answers:

Status Message Meaning
200 none Saved. The reply carries the new state.
403 This page has expired. Refresh it and try again. The nonce is stale.
403 Log in to save favourites. Logged out, or Favourite hearts is off.
400 This product cannot be added. The product is missing or not published. A product can always be removed.
409 Your favourites are still saving. Try again in a moment. Another heart of the same member held the per-member lock for 5 seconds.

The heart itself shows “Could not save. Try again.” when the request fails.

Nothing moves on update: 2.0.0 reads the same keys. A saved reign_wcfm_store_layout value is left in place and ignored. Deleting the plugin keeps all saved data.