We’ve been experiencing issues with token gating eligibility on our Shopify shop recently.
For a newly launched collection, we configured gating rules for all products based on “Filter by attribute” (as shown in the screenshot). However, token holders with matching metadata attributes are facing eligibility issues when trying to purchase the product.
For testing purposes, when we try using the gating rule with “Select individual token” and specify a particular token ID, it correctly shows the holder as eligible based on the matching token ID. However, this isn’t ideal, as we need to apply the gating rule using “Filter by attribute” (e.g., Card Name: XXXX).
We’ve already tried the same procedure on a different store, and the results were the same. It shows no eligibility for any rules configured with filter by attributes for that specific contract address.
On another note, there are two specific token’s metadata attribute that still do not appear in the “Filter by attributes” list for configuring the token gate rule based on. We’ve already tried refreshing the metadata, but still, they’re not showing up in the list.
It would be really nice to have these issues sorted as soon as possible.
Thank you!
Hi, looks like some tokens are missing metadata indexing/attributes. Have you tried to click the refresh metadata button for the collection on that shopify configuration page?
Note, we’re also investigating the lack of attribute indexing on our side atm.
Thank you.
It would also be helpful to look into the eligibility issues mentioned in the main post, as they’re affecting all other configured products in the same collection.
We’ve recently noticed that the tokengating eligibility issue is still occurring with some of our collections, and holders aren’t able to purchase products from the shop.
Also, it’d be helpful to understand why this issue occurs randomly for certain gated products and if anything can be done to prevent it from happening.
Ok, we identified the issue. Whenever this happens, you should go attempt to refresh the collection attributes. Looks like there’s no metadata indexed for some of these tokens. A refresh should fix it in the future. Do you know how to do this?
Wait a second, did you guys update the contract such that the uri changed? If so, that would explain the issue. Whenever you do this, you need to refresh the collection metadata
Ya, ok, so the reason this is happening is because the base uri was set after some of these tokens were minted, causing us not to have proper indexed data. For example, contract “0x69f032e57348eb34605f98c2f1c331cc9e473d26” token 1 was minted on Oct 28, 2024, but the base uri wasn’t properly set until Oct 31, 2024.
Whenever you update your metadata uri, you need to trigger a metadata/attribute refresh.
Wait a second, did you guys update the contract such that the uri changed? If so, that would explain the issue. Whenever you do this, you need to refresh the collection metadata
Yes, you’re right about token uri, it was set after minting some of those admin card tokens.
Seems like refreshing the metadata for token on Chimpers Marketplace did the trick.
