Hi Michael,
Not sure if it is meant to do this or not, I would guess not but I have had the same thing happen when I don’t fill in columns. Everything moves around a bit. If you try filling in the empty spaces with something, maybe even just a dash does it still happen then?
Regards,
Mark
Yes If you put a space/or anything in a field it will keep the table in order. I gave Mark access to my site but he never logged in so I don’t know what he thinks, maybe he saw it on his own site and working on a fix. It’s a brilliant plugg and I really want it to work.
NOW… Mark if you read this! 😊
With the power of the EE 1.6 version how about if we could set the number of columns for each custom field, so for categori A I have a custom field A set to 5 columns and CF B set to 3 columns etc…
Hmm What do you think.
-Michael Bystrom Design
Would it be possible to use the offset parameter with this? I need to enter data that will physically be displayed in different columns on the page. The layout of the content in the entry form is so clean using Multi-Text, I just need the ability to offset which rows of content are being displayed in which column on the page.
giovanni, I think that you just use col1, col2, etc. where the content should output.
Can anyone think of a way to hack it so that you can sort the order of the rows on the front end?
I have one field in each row set to hold the sort order. I’d like to be able to parse the array on output, to order the results (eg: loop through the custom tag, but sort by col_4…)
Any thoughts?
Having a particularly nasty issue with this one that we just discovered. The issue happens when adding a double-quote (“) character to any text in the multi-text fields. The first time you save the data, it works fine. However, when you come BACK into the same entry to edit it, everything past the ” in a given field disappears – and then, of course, when you save it it saves without the data that isn’t showing.
It’s gotta have something to do with the way characters are being escaped on the way to and from the server; any ideas for a fix?
I would guess that it probably has something to do as you say with the fact that “ characters are probably being used in the query statement and so when it sees these it is having a problem although I would personally have thought that it would throw errors up at that point. They probably do need to be escaped differently to handle this but I will leave that up to the excellent Mr Huot to fix for you as it is his extension.
Best wishes,
Mark
@alienne - please try v110 at the top of this thread.
@Mark Bowen - it’s strange because I’m not really touching any of the database calls. It’s all happening in EE, so I don’t know why a text field doesn’t have this problem, but my EXT does. Either way, I’m hopeful v110 will fix this.
Mark,
Update does NOT seem to have fixed the issue, I’m afraid. If you need a login to the site that’s having issues, I’d be happy to PM you one. I’ve also got a couple other extensions of yours enabled, and can disable them to see if that’s the issue, or set up a minimal test case elsewhere.
Adrienne
I must be such a noob…
I added this wonderful extension, followed all directions and all I’m getting for output is:
* {my_field_name} {col_1}: {col_2}
{/my_field_name}
It’s not recognizing the field name as something it should be converting into working code or something. Any ideas on this?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.