yes… combine your Moxicode File/Image field into there!
Thanks for your work on this extension Leevi!
I third the request– adding a “file” column type would be incredible, especially if it were for Moxiecode.
Edit: Build 20081212 of EE fixed the multi-dimensional array in POSTs issue. Does that mean Victor’s resolution here is no longer necessary?
RE: Conflict with LG Live Look
I had this installed and working perfectly and only recently realised the JavaScript interactions (add, delete, order) had stopped working.
It took a while to track down the problem but I realised eventually that once I disabled LG Live Look on the weblog the JavaScript started working properly again.
Once realising that the jquery library was being loaded in a few times by different extensions I resolved this issue by removing the references to the jquery.min.js file in the extension settings.
Just posting here in case anyone is experiencing a similar issue.
I’ve suddenly started getting the following error on 1.6.6, build 20081212:
Notice: Undefined index: lg_field_conf in *my_system_path*/extensions/ext.lg_data_matrix_ext.php on line 1030
Edit: This happens only when BN Add Short_Name is enabled. I’ve posted there: http://ellislab.com/forums/viewthread/101260/
I know 1.6.7 is fresh out the press, but does anyone know if the Core EE bug described by Nirada above has been corrected in the latest version of EE? Would this open the door to fixing the apostrophe bug in the extension?
I also get the unserialize error, as well as lose all the data I inputted in the data matrix, if one of the cells has an apostrophe or quotation mark. Using ' instead of ’ avoids the problem, but I’m paranoid of adding an accidental apostrophe and breaking everything. I’m even more worried of letting clients write their own text in the matrix!
A massive shoutout has to go to the one and only Brandon Kelly for commiting a bunch of fixes and updates to this extension including the date and checkbox field types. Thanks again mate.
Welcome to the Matrix 1.1.1!
I’ve just commited a major update to LG Data Matrix to GitHub: http://github.com/newism/lg.data_matrix.ee_addon/tree/master
I’d love for you guys to test the latest version before I make it official and add it to my site.
Upgrading is simple, just replace the old files with the new ones. Remember backup your db first before upgrading.
This version also requires CP jQuery loaded with jQuery 1.2.6 and jQuery UI 1.5.2 - jQuery 1.3.1 and jQuery UI 1.6 have some sortable bugs so don’t use them just yet.
There are two new field types checkbox and date. To create a new date / checkbox field add the following to your field configuration:
short_name = date_1
title = Date 1
type = date
short_name = checkbox_1
title = Checkbox 1
type = checkbox
The new version of LG Data Matrix also supports quick save, preview and revisions. It’s also NSM Publish Plus compatible.
Hey Leevi,
Great to see this, as I’ve been struggling with this for the past 24 hours. Thanks for all the hard work.
Unfortunately, this update does not fix the main problem I’m having, which is the unserialize() error. I tried the previous fix posted here by Nirada, that didn’t work either. The problem - I think - has to do with not single quotes, but high-ASCII apostrophes (and presumably other high-ASCII characters) which originate from a cut and paste (which is how my clients generally get data into EE). The serialization is counting them as single characters, but EE is subsequently converting them into entities, which of course adds extra characters to the string, which throws off the unserialize() function.
Any chance of a fix for this that would cover high-ACII character conversion?
Also, there’s a typo on line 501 causing an error:
$old_fields = $DB->query("SELECT * FROM `exp_weblog_fields` WHERE type = '".$this->type."'");
I think should be:
$old_fields = $DB->query("SELECT * FROM `exp_weblog_fields` WHERE field_type = '".$this->type."'");
Thanks again for the great extension.
I have updated the extension on GitHub which addresses the typo you mentioned above. There were a couple of Brandon’s commits that I missed in the original merge.
Re: high ASCII issues - I’ll take a look at the them asap but I ‘can’t make any promises.
I recommend everyone download the 1.1.1 tag again
Sorry for any inconvenience.
Thanks Leevi.
Best I can think of is running the data through the filter_censored_words() function from the Typography class (which appears to be the function that converts high ASCII characters to entities) before it gets serialized - this way EE won’t have anything to convert when it processes the serialized array?
Best, Derek
Hey Leevi - I finally got to the stage of outputting data from the extension, and found that slashes added to quotes were not stripped. So I just changed line 875 from:to:return $r;
return stripslashes($r);
Missed that one :D
I have updated the master branch on github if you want to grab the latest. A couple of IE7 bugs were also fixed
Thanks once again Leevi, that fixed it up.
Just found another issue … a conditional check on an empty Data Marix field doesn’t seem to prevent the processing of that field, despite it being empty, which is yielding errors and warnings:
{if my_custom_data_matrix_field}
{!-- Evaluates false, as there's nothing in this data matrix --}
{!-- Data Matrix tags here --}
{/if}
Leads to this when my entry is displayed:
Notice: Undefined variable: clean_row_data in /home/.../extensions/ext.lg_data_matrix_ext.php on line 691
Notice: Undefined variable: clean_row_data in /home/.../extensions/ext.lg_data_matrix_ext.php on line 705
Warning: Invalid argument supplied for foreach() in /home/.../extensions/ext.lg_data_matrix_ext.php on line 768
I fixed this by adding this to line 640:
$clean_row_data = FALSE;
Sorry to keep piling them on. 😊
Derek
Hey guys,
A new download is available on my site. It’s the official release of version 1.1.1 which has many bug fixes and a couple of new features.
Things to note if upgrading include:
Make sure you backup your DB first.
Check out the rewritten and improved docs: http://leevigraham.com/cms-customisation/expressionengine/lg-data-matrix/
Leevi,
I might be an anomaly, but I’m trying to implement this for Architectural & Engineering specifications table with 6 different matrix’s and it seems to crash on the 4th instance of the matrix on a single entry page.
I need 6 different matrix’s b/c of the product properties differences (ie. Physical, Mechanical, Thermal, Flammability and Electrical). It’s a whole bunch of technical data that varies from product to product and thought this would be the easiest way for data entry on their end.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.