Reploverse Icon

Join Our Community

Issue with Replo: Metaobjects Resetting on Page Republish | Reploverse

Product Support

Product Support

Issue with Replo: Metaobjects Resetting on Page Republish

·

·

Hello! We have a very annoying issue with Replo I am hoping someone can shed some light on. We create landing pages in replo, and we have a pretty custom backend to handle our lander world — it utilizes metaobjects which get tied to the pages once published. The issue we have is that once a replo page has been published and we add metaobjects to that page in shopify, if we ever attach additional metaobjects (or replace), anytime the replo page is modified and republished, replo is removing the metaobjects we have assigned to that page and replacing them with the original ones. This forces us to be unable to duplicate pages which already have metaobjects attached (FYI, the metaobjects are what controls our lander pricing and other things about the landers as they apply in our discount structure). Instead, we have to create a new replo page, go copy all the layers from the one we’re copying, and create the page then go hook up the metaobjects. Is there anyway for replo to quit reverting metaobjects on us?

12 comments

Ryan Elledge
·
·
this is an example of a page with metaobjects attached:
Ryan Elledge
·
·
If I go add an additional sales lander offer object or change it to a new one, it will always revert back to these exact ones anytime we republish the page in replo
Steve Schlaefer
·
·
Hmm that is very bizarre and certainly sounds like an advanced use case. We don't think we're actively doing anything here so my guess is this might either be:
an artifact of how Shopify does page <> metafield relationships -> or perhaps even a bug on their side
something specific in your theme/setup that is doing this
(The third option of course being we're doing something silly or unavoidably dumb when we update the page) One question here Ryan Elledge is does this same sort of behavior happen with NON-Replo pages. Replo pages are just another liquid file saved to your theme so in many ways they should behave the same way as any other Shopify page (like the /about-us or /contact pages). Do you have a way to test out that theory?
Ryan Elledge
·
·
Hi Steve Schlaefer — no, this only happens with Replo pages. I should point out to you that about a year+ ago when we started using Replo, anytime we published the replo page, it was completely wiping out the metaobjects. We put in a bug to you guys and you quickly released a fix for that. Ever since then, this situation has happened. I did reach out long ago in support and mentioned it, but we have just continued to do our manual work around. But now, we have so many pages and this happens so frequently, I bring it to you here.
Steve Schlaefer
·
·
Ryan Elledge just letting you know we're looking at this in more detail on our side to try and reproduce. We'll have an update for your next week. If anyone else has any insights here we're happy to take a look!
Pylon
APP
·
·
Hi Ryan! Sorry for the delay -- we're continuing to investigate this week and we're having some trouble reproducing on our end. To check, are you still using a Shopify App called "Metafields Manager"?
Ryan Elledge
·
·
Kevin Fang (Replo Team) we do still have that app in play, yes
Ryan Elledge
·
·
Kevin Fang (Replo Team) a test you can do.
1.
Build a page and publish it
2.
Add meta object(s) to it
3.
Duplicate the page in Replo
4.
The duplicated page will have metaobjects attached to it, just as the one it was cloned from
5.
Change the metaobject to a different one on the cloned version
6.
Make any change to the new lander and republish it
7.
Check to see what meta onbjects are now attached to it. If it is anything like what happens to us, you will see the metaobjects reverted to the ones that were on it when it was cloned
Pylon
APP
·
·
Thanks for providing the in-depth replication steps! From what you are describing it seems like there is an issue where pages with the same Replo template after duplicating it in Shopify result in publishing overwriting the duplicate page Metafields with the original page Metafields. Unfortunately, when replicating the steps on our testing store with Metaobject, Product, and Single line text metafields, we were unable to replicate metadata overwriting when the page was published. I've sent a request to access the BioTrustDev Shopify store metafields and apps data as we suspect the reason for non-duplication may be related to the Metafields Manager app which we do not have on our testing store. If you approve the request, we won't have the ability to delete definitions, approve app charges, or see any other product or customer data. Thanks for your patience and apologies again for this reoccurring issue.
Pylon
APP
·
·
One last check in on this -- would love to help out here. We've been testing with Metafields Manager and would love to know what your setup on that app is. Let me know you have any questions about the access request I sent.
Ryan Elledge
·
·
Hey Kevin Fang (Replo Team) so sorry I lost track of this slack channel. I do not see a pending request on biotrustdev.myshopify.com ?
Pylon
APP
·
·
Hey Ryan, sorry for the delay. Just re-requested permissions for the BioTrustDev store -- can you let me know if you're able to see it this time? Thanks!