Loading Profile...
Twitter,
Facebook, or email.
I noticed that the thumbnails weren't refreshing in the admin area if the image was changed in the Matrix field, so I got the newest version.
If I simply upload the new files into place, the admin shows that it's now using 2.1.3, but on the front-end, it only displays the EE tags, not the output of the tag.
I considered uninstalling the plugin to add the new one, but receive a message stating that the data will be lost. Is there a work-around or am I missing something?
Thanks
I’m
confused
Matrix not parsing tags after upgrading from 2.0.11 to 2.1.3
Official
Response
-
Stephen’s problem ended up being another bug with EE’s template parser. The workaround for that one isn’t as simple as “add ‘_matrix’ to the end of your field name”, so I reverted him to Matrix 2.1.2 while we wait for EllisLab to fix their template parsing bugs. (I’ve notified them about both bugs.)
To anyone else who wants to revert back to Matrix 2.1.2, you can grab it from P&T.com by just appending “&VER=2.1.2” to the Download link’s URL.
And if you’re wondering how this is an EE bug if changing your Matrix version fixes it – that’s because previous versions of Matrix parsed their own tags, via the extension, but in Matrix 2.1.3 we decided to start letting EE parse our tags for us, like a normal fieldtype.
-
EMPLOYEE
1Hey Thomas,
Do your column names begin with your Matrix field name? If so, can you try appending "_matrix" to the field name, and reflecting that change in your template?Comment -
-
Hi Brandon,
I'm seeing this as well. My columns aren't prefixed with the matrix field name. I upgraded to 2.1.3 from 2.1.2
Thanks,
Dylan -
-
What exactly is happening? And what is your Matrix field name, and its columns’ names?
-
-
I’m
frustrated
I am also seeing this. Basically, it just outputs the tags. E.g...
{slideshow_items}
{/slideshow_items}
My matrix field is slideshow_items. The column names are: image, label, description, url, url_target, duration.
I don't see any odd behavior with the field when I create, edit, or save any entry. -
-
You guys have extensions enabled right? (Add-Ons > Extensions)
-
-
And what version of EE are you guys on?
-
-
Yes, the extension is enabled.
I'm running version 2.1.3 Build 20101220 -
-
Any chance I can get FTP and Super Admin access so I can go in and see this for myself? If so, you can email the credentials to support@pixelandtonic.com. Please also include the template where you’re having the issue.
-
-
I'm on EE 2.1.3 Build 20101220 as well with extensions enabled. My matrix field is named exh_works and contains 1 file field, 7 text fields and a P&T Checkbox field. All of the columns just appear in my template as ee tags.
Unfortunately this is a local install so I can't give you access. I couldn't see anything obvious when turning on template debugging. The query is being run okay. I setup a new matrix field with a file and text column and it worked fine. It seems to be an issue with existing matrix fields. I was able to rollback to 2.1.2 easily. -
-
I'm also having this problem (ExpressionEngine v2.1.3 Build 20101220). After updating Matrix from 2.0.11 to 2.1.3, Matrix tags are not being parsed.
Edit: My column names did begin with my Matrix field name. I appended '_matrix' to the field name and things seem to be displaying properly now. -
-
Stephen’s problem ended up being another bug with EE’s template parser. The workaround for that one isn’t as simple as “add ‘_matrix’ to the end of your field name”, so I reverted him to Matrix 2.1.2 while we wait for EllisLab to fix their template parsing bugs. (I’ve notified them about both bugs.)
To anyone else who wants to revert back to Matrix 2.1.2, you can grab it from P&T.com by just appending “&VER=2.1.2” to the Download link’s URL.
And if you’re wondering how this is an EE bug if changing your Matrix version fixes it – that’s because previous versions of Matrix parsed their own tags, via the extension, but in Matrix 2.1.3 we decided to start letting EE parse our tags for us, like a normal fieldtype. -
-
I’m
flabbergasted
i came across this bug too just now. weird thing is: it only happens on some of my matrix fields and only after updating to playa 4.0.3... can i roll back to matrix 2.1.2 with playa 4.0.3 installed?-
Yes you can.
-
-
-
-
-
I forgot to say that I upgraded to playa 4.0.3 at the same time too. Portnull I'm happily running matrix 2.1.2 and the latest version of playa.
-
