Plugin

Developer
Supported

Custom Drop Down Creator

ExpressionEngine 2

Back to this add-on's main page
View Other Add-ons From Mark Bowen Design

     

You must be logged in to post.

PHP errors but fields show

Support Request

JonnyTurner
JonnyTurner

Hi Mark,

I’ve installed your plugin that I bought earlier. I’m getting php errors but the fields still show fine when i scroll down. The error I’m getting is:

SeverityNotice

Message
Undefined offset1

Filename
custom_drop_down/pi.custom_drop_down.php

Line Number
126 

I have the template code below within a super search form. Everything seems to work perfect apart from the php errors.

<select id="{exp:custom_drop_down:field_id field_name="classifieds_inst"}" name="{exp:custom_drop_down:field_id field_name="classifieds_inst"}">

{exp:custom_drop_down field_name="classifieds_inst" separate_values="yes" initial_value_value="" initial_value_option="Choose an instrumentÂ…"}
<option value="{value}">{value}</option>
{/exp:custom_drop_down}

</select

Is it something really stupid I’ve done??

Cheers in advance!

Jonny

Mark Bowen Design
# 1
Developer
Mark Bowen Design

Hi Jonny,

I’ve never tested the plugin with Super Search and that’s why it’s not mentioned as being a compatible add-on on this plugins page.

I do own a copy of Super Search so if you can wait a while I’ll have to set up a test bed to see if I can figure out what’s going on here.

Saying that though I have noticed a few add-ons don’t tend to work when used within certain Solspace add-ons, not too sure why that is though.

I can’t promise that I will get it working and that’s the reason why I left off compatibility for it on the plugin page but I promise I will give it a go in the coming week and see what I can find out.

Best wishes,

Mark

P.S. Whilst I’m testing would you mind trying to change double quotes inside all the plugin parameters to single quotes just to ensure they’re not interfering with the double quotes in the HTML code.

JonnyTurner
# 2
JonnyTurner

Hi Mark,

Cheers for the quick response! I’ve managed to get it working by removing the separate_values parameter. I tried it outside of the supersearch loop and still got the errors so just experimented with it. Not sure what’s going on with it but it now works perfect!

Thanks for the excellent plugin!

JT

Mark Bowen Design
# 3
Developer
Mark Bowen Design

Hi Jonny,

Thanks for letting me know what it was. To tell the truth I can’t even remember adding in that separate_values parameter so I will have to look into what that was exactly and why it isn’t working.

Glad you have it working and as soon as I’ve reminded myself as to what that parameter is for I’ll take a look into why it’s not working.

Thanks again for letting me know what was up though.

Best wishes,

Mark