just as a test I added ?&form= to my chunk instead of ?form= I received the same invalid form error. So I changed it back cleared the cache and it is working again.
[!mailchimpSubscribe?form=`mailchimpNewsForm_en`&listId=`d7c8e27095`!]
@einsteinsboi: Please can you try the attached snippet in place of your current subscribe snippet and see if that eliminates the parse errors. I’ve revised the detection of the $modx->placeholders array.
I’ve tested the snippet locally on Evo 1.0.2 and the following snippet call construct works fine:
[!mailchimpSubscribe?form=`mailchimpNewsForm_en`&listId=`d7c8e27095`!]
What was the issue? I noticed the new conditional that you added. Is this something with Evo 1.0.2 or just some setups in particular?Although the document parser initiates the ’placeholders’ class variable, it never sets it’s type. So, it only gets the array type when the first placeholder is set. That was the problem with the parse errors. When I first developed the snippet, it must’ve been on a page where a placeholder had already been set so I never seen the parse error.
What was the issue? I noticed the new conditional that you added. Is this something with Evo 1.0.2 or just some setups in particular?Although the document parser initiates the ’placeholders’ class variable, it never sets it’s type. So, it only gets the array type when the first placeholder is set. That was the problem with the parse errors. When I first developed the snippet, it must’ve been on a page where a placeholder had already been set so I never seen the parse error.
One more question out of curiousity, why does adding the & before form break the snippet? Shouldn’t that work?It works fine for me on the revised snippet code, are you still seeing that even with the revised snippet?
One more question out of curiousity, why does adding the & before form break the snippet? Shouldn’t that work?It works fine for me on the revised snippet code, are you still seeing that even with the revised snippet?