FieldFrame

@kundi:

… == {row_count}} …

Hi Brandon (and everyone else in here).

I’ve never once had a problem with the FieldFrame extension but just today have done unfortunately. I recently updated a site to the very latest build of 1.6.7 (it was only one build behind though), the server has PHP V5.2.9 on it and I have installed the very latest version of FieldFrame.

Upon creating a new FieldFrame matrix field though I can’t add any more columns using the green plus arrow. I have checked in the Error Console in Safari and get this error :

TypeError: Result of expression ‘rows’ [undefined] is not an object.

I thought perhaps it might be another extension interfering or something but I have now tried disabling all extensions except for FieldFrame and still I can’t add any more columns.

Just wondering if anyone had any ideas?

Best wishes,

Mark

Sorry for the exceptionally shameless bump but was just wondering if anyone had any ideas on the above at all?

I’ve checked everything that I can think of now, permissions, version etc… and just for the life of me can’t see why it won’t work. I’ve never ever had this problem before and every other site I’ve ever used it on it just works first time every time. The servers are pretty much identical too.

Thanks for any insight that anyone might have on this.

Best wishes,

Mark

@ Mark,

When in doubt, remove & reinstall. Worth a shot, at least.

@ Mark, When in doubt, remove & reinstall. Worth a shot, at least.

Did do twice already but unfortunately no go :-(

Hi Brandon,

I’m using your search parameter on FF Matrix for the first time and I’m getting an error message. Wondered if you could help me out. This is my code:

{exp:weblog:entries weblog="daily-news" limit="50" disable="pagination|member_data|trackbacks"}

{news-articles search:category="{segment_3}"}
<ul>
<li>{title}</li>
</ul>
{/news-articles}
{/exp:weblog:entries}

And this is the error that I get:

Notice: Array to string conversion in /extensions/fieldtypes/ff_matrix/ft.ff_matrix.php on line 650

Thanks so much!

Yeah search is a bit incomplete at the moment; doesn’t work on celltypes that save their data as an array yet. Next version should fix that.

I’m using it on a multi-select. What field types would work now?

Thanks

Everything besides FF Multi-select and FF Checkbox Group.

Ok, thanks.

I’m sure you’ve been asked this 1,000 times already, but I haven’t been able to find the answer to it on your site, this thread, or Satisfaction…

Is there any plan to make this work for Custom Profile Fields? In particular I have searched everywhere and can’t seem to find a non-hacky way to add a multi-select field to a profile (such as a Checkbox group).

Thoughts?

Thanks!

Hello, I’m experiencing some problems with the following code:

test template: {exp:for_loop start="1" end="5" increment="1"} {embed="packet/test_list" selected="{index}"} {/exp:for_loop}

test_list template: {exp:weblog:entries weblog="myweblog" disable="categories|trackbacks" limit="1"} {ffmatrix} <option value="{row_count}"{if embed:selected == {row_count}} selected{/if}>{name}</option> {/ffmatrix} {/exp:weblog:entries}

It occures that only the first 3 items will have selected attribute set, and the next items wont have it. (Seems like there is a problem with comparing embed:selected == {row_count} when the number is bigger than 3. Any idea?

Thanks in advance!

Biggest Praise Wow FF is a great plugin. Thanks Brandon! And thanks for all your support for the products!

Sneaky plug for FF requests: 1. Allow the $this->include_js() function to accept full url’s, to save me having to enter something like $this->include_js(‘../../../../../scripts/myscript.js’). Maybe as an optional parameter for the array. Ditto for $this->include_css(). 2. Port FF to Custom Member fields. Then shall you become superhero. 3. Port FF to Custom Category fields. Then shall you become world dominator.

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.

Any chance of allowing textarea formatting as standard?

I’d have thought that it could just use the same formatting options as a standard textarea.

Otherwise my clients are stuffed as they don’t do HTML.