I’ve installed FF Matrix on two sites, and I can’t get it to render my fields at all, instead, it just prints the entire template tag:See the attached picture… it just prints this out. The 2nd site does the same thing, but with different data. It’s just ignoring the custom field. The 2nd site is EE core with very few add-ons installed, so I can’t imagine a conflict. What am I missing?{location_dept_phone} <-- my custom matrix field {department_name} - {phone} {/location_dept_phone}
And, {department_name} and {phone} are both the column names (as opposed to labels)?
Just checkin…
Well this was my problem…
http://getsatisfaction.com/brandonkelly/topics/ff_matrix_outputting_tags_not_rendered_matrix
EE needs to get away from absolute/full paths.
Edit: I see the new config values in 1.2. Nice. Thank you.
Edit again: Nice attention to detail in the CP by making those files uneditable if the values are defined in the config file.
Noticed someone referenced how foxEE was causing problems with FieldFrame.
http://ellislab.com/forums/viewthread/108082/P72/#579082
Does this mean that FieldFrame is not going to work if you have foxEE on your site?
Is there any way to get xhtml markup in a FF matrix? I see in the docs that there’s a switch for formatting_available but can’t quite wrap my head around where that might go.
Thanks!
Nice attention to detail in the CP by making those files uneditable if the values are defined in the config file.
Glad you caught that! 😊
Is there a way to filter entries by multiple checkboxes (Months of the Year)?
I think you brought this up on IM, and it was solved using {exp:weblog:entries search:my_field="month1|month2"}
Why FieldFrame doesnt work with Sarge? Is there any other way to assign values to options?
Not sure if I understand your question. Do you mean the drop-downs within FF Matrix? You can assign values to those in the same way you assign values to FF Checkbox Group, FF Radio Group, and FF Multi-select fields:
value1 : My First Option
value2 : My Second Option
value3 : My Third Option
Noticed someone referenced how foxEE was causing problems with FieldFrame…
That was a FoxEE bug. I have no idea if they’ve fixed it yet. Try it out with the latest version of FoxEE, and if you’re running into the same issue, contact its developer.
Is there any way to get xhtml markup in a FF matrix? I see in the docs that there’s a switch for formatting_available but can’t quite wrap my head around where that might go.
That setting is for the actual fieldtype developers, which toggles whether or not you see the formatting settings within the Edit Field form.
None of the bundled fieldtypes (including FF Matrix) do their own formatting. Take a look at SL Field Formatting which will work with FF Matrix cells.
That setting is for the actual fieldtype developers, which toggles whether or not you see the formatting settings within the Edit Field form. None of the bundled fieldtypes (including FF Matrix) do their own formatting. Take a look at SL Field Formatting which will work with FF Matrix cells.
I installed SL Field Formatting, and it doesn’t seem to have any effect on Matrix cells.
I really need some way to get formatting buttons onto a Matrix textarea. I’d be willing to do a bit of hacking, if necessary, which is why I went poking about in the Matrix fieldtype file.
I’m also wondering if there is a way to apply the XHTML or formatting filter to FF Matrix text areas. At the moment, users must write their markup in text areas, but not all users will remember to wrap their paragraphs with the tags, for example.
Other possibility: is there a plugin that I could use in my templates which would add XHTML formatting to a text area part of a FF matrix?
@ContextDesign: Have you looked into the EE Typography plugin?
This answered my previous post, where a text area can be formatted after wrapping text area tag with the plugin.
If you want to give formatting control to your users, I imagine an extra FF selection field could be used just for that, as EE Typography accepts a formatting parameter.
{exp:ee_typography formatting="{your_ff_field_formatting}"}
I haven’t tried it though, so I cannot confirm if this works correctly.
I agree that the option of using a WYSIWYG field for those users would be nice, although I’m not fond of giving WYSIWYG powers to regular users. I guess what we’re looking for is a new WYSIWYG fieldtype for FF FieldFrame (and Matrix), maybe combined with the LG TinyMCE extension?
In the meantime, although maybe not the most elegant solution, how about using the HTML formatting buttons that come with EE (with maybe the EE Typography plugin)? Unless the mere sight of HTML tags frightens some users, in which case WYSIWYG is the other option.
I’ve been playing with epEditor lately. It produces much nicer code than tinyMCE. If there were a way to get that into a Matrix field, I’d be tickled.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.