I am getting about 115 SQL queries when not even calling on this extension, is there any reason this might be happening.  Here is the SQL.

UPDATE:
I got this issue resolved and was not related.

There may be a problem with this extension for the latest builds of EE.  I’m getting the following error:

Warning: Typography::require_once() [typography.require-once]: Unable to access ./admin/plugins/pi..php in /var/www/vhosts/projects.somewebsite.org/httpdocs/admin/core/core.typography.php on line 475

Warning: Typography::require_once(./admin/plugins/pi..php) [typography.require-once]: failed to open stream: No such file or directory in /var/www/vhosts/projects.somewebsite.org/httpdocs/admin/core/core.typography.php on line 475

Fatal error: Typography::require_once() [function.require]: Failed opening required ‘./admin/plugins/pi..php’ (include_path=’.:’) in /var/www/vhosts/projects.somewebsite.org/httpdocs/admin/core/core.typography.php on line 475

It isn’t able to find the proper plugin, but I think it’s because your multi dropdown fields are not adding “none” or something other than “NULL” to the field_ft_X column for the field in exp_weblog_data.  Or perhaps it should be putting “multiselect” in there?

I’m going to try to week through the extension and see if I can confirm this issue.  Anyone else experiencing this?

Ok - I can confirm that this is an issue.  For any of the fields that you use as the multi dropdown list, in the exp_weblog_data, the field_ft_X column is NULL.  It should be “none” or “multiselect” or something.  My entries use 1 multi dropdown field, and I changed the field_ft_X column to be “none” instead of NULL for all of them, and I no longer have the error!

Mark, can we get a fix for this please?  Or, does someone else know how to fix this?

See this post here for hopefully a fix.

Best wishes,

Mark

Mark Bowen - 28 May 2009 01:12 PM

See this post here for hopefully a fix.

That fix is very specific to a different extension, and while it’s the same concept as the Multi Drop-down List extension, the extensions are written differently.  I’ll see if I can figure it out…

creativearc - 28 May 2009 01:37 PM

Mark Bowen - 28 May 2009 01:12 PM

See this post here for hopefully a fix.

That fix is very specific to a different extension

It’s not, honest

I’ve applied this to around 5 different extensions now and it worked in all cases. Admittedly I haven’t tried it out on this extension but I would imagine it should work.

In the page that I linked to yes it does reference the LG File Manager extension as the one that they are applying the fix and the one which the page is documenting but it does also state above that, some other extensions this can be applied to also.

Should work I reckon.

Best wishes,

Mark

I have tried it.  It doesn’t work, unless I’m a wad and I’m just not doing it right.

I can even see the hidden field in the field edit source.  Everything looks as it should, but when an entry gets saved, I’m still seeing NULL

Ok, I got it to work.  So - I was a wad.  I was assuming the function that edits the field would do it, but you have to put the following at the bottom of the “publish” function for this module:

creativearc - 28 May 2009 02:47 PM

Ok, I got it to work.  So - I was a wad.  I was assuming the function that edits the field would do it, but you have to put the following at the bottom of the “publish” function for this module:

$r .= $DSP->input_hidden('field_ft_' . $row['field_id'], $row['field_fmt']); 

Excellent news. Glad you got it working

Just out of interest for anyone else that might be having this problem was wondering if you would share the exact line that you placed this code at so that others can add it in if needed.

Best wishes,

Mark

Mark Bowen - 28 May 2009 03:27 PM

Just out of interest for anyone else that might be having this problem was wondering if you would share the exact line that you placed this code at so that others can add it in if needed.

Well, I made a couple other changes of my own, so this isn’t exact, but add it above the “return $r” at the bottom of the “publish” function.  Approximately at line 510.

Thanks. I’m sure that will help out others if they ever have that problem.

Hope everything else goes well for you.

Best wishes,

Mark

Has anytone tried converting this multi-select to brandon kelly’s new fieldframe multselect field?

Can someone point me to an explanation of how to use this extension please? I was hoping for a readme in the current zip, but no joy.

I’m prepopulating this list from custom field entries in another weblog and I need to be able to extract the entry_ids from the items selected on the Publish page. All I seem to be able to access is the entered values for those entries (which is obviously what’s intended, I know), but there is some mention of people getting the entry_ids earlier in this thread, so I’m wondering if there is now a tag option?

Any help appreciated. Thanks.