Hey @andreearadacina21
Yes that product is one I assigned manually on the product page.
The issue is exactly as @carryoncoding described in the ticket prior to mine. The fields are assigned to products in PPOM Field Groups but they are not being pulled in to the product.
? If you assign a field group to a product that has NOT previous had the fields assigned it works.
? If you remove a field group from a product that had the fields assigned to it prior to the update and then reassign it the fields are NOT pulled through.
Rolling back the plugin to version 32.0.9 fixes it, but this is not a solution as there has been a security patch since then.
The only solution I can find is to add the fields at product level.
I am unsure how many products are effected as I did not add them and inherited the client/site from another agency as well as the PPOM integration.
? Interestingly, down grading to 32.0.9 and then upgrading again to 32.0.13 appeared to fix the local version I set up earlier, but not the live version.
? The live version was fixed after down grading to 32.0.9 but the problem returned once the 32.0.13 patch was applied.
I am unsure how many products are effected as I did not add them and inherited the client/site from another agency.
I will hopefully speak to the client in the morning and can get a better idea of the damage then, I have been unable to reach her today after she reported the issue.
In a nutshell though, it appears that the custom field groups that PPOM generates are not being pulled through to existing products anymore and there are no sign of them in the code.
I will add to this ticket once I get to speak to the client.
Cheers
Gary
-
This reply was modified 8 months, 2 weeks ago by tinpeas.
-
This reply was modified 8 months, 2 weeks ago by tinpeas.