Checkout - step 3 alteration

Hi Jason,

The short simple answer is that it is complex. Because of the feature that we allow extra fields to be assigned individually to a category(ies), the php code that gets extra fields, has to determine which extra fields are available for the individual listing category. In other words a seller placing a listing in category 1 may have different extra fields than a listing in category 2.

However, if your extra fields are set so that ALL extra fields that you created are available in ALL categories, then {$extra_listing_fields} code will always be the same. If this is the way that you have it set up, then you could simply look at the source code of the page after it is rendered in your BROWSER and simply copy the portion of html code for the extra fields section and manually add it to your template file however you wish as long as you, of course follow the html form syntax rules keeping all of the extra field elements within the form. (replacing the {$extra_listing_fields}).

Bear in mind that {modulehook function="tpl_addlisting"} is a module hook and has nothing to do with the extra fields unless, of course you actually have a module installed that is using that function and is manipulating the extra fields.

Jason,

This is entirely different, due to the fact that the fields have already been assigned a value. However, in your particular case having narrowed this down to only needing to do this with known field id's and only in one extra field type (drop down/select menu), you may be able to simply capture the value to do your comparison.

Use the same code for the extra fields forms as you did in the step3 checkout, but use the smarty plugin to get the individual values as you've already shown in your post above for the values. Now for your drop down menus...
I haven't tried/tested this, but smarty has a capture function available and it may work here. Essentially, you tell smarty to capture something and assign it to a name instead of displaying it.
Try it like this:

Code:

{capture name="opt7"}
  {get_extra_field id=$entry.id fid=7}
{/capture}
<option value="THIS COMES FROM YOUR step3 CODE" {if $smarty.capture.opt7 == $smarty.post.opt7} SELECTED{/if}>THIS COMES FROM YOUR step3 CODE</option>

Jason,

The listing in that template is $id. As you know, to find out what variables are available, you should use the Smarty {debug}. So, with that said, the plugin should be id=$id.

I would suggest that you see if indeed that both the variables are being shown/available in the template. In other words, try just showing each variable separately to see if they are actually showing in the template.

Try: {get_extra_field id=$id fid=7} {$smarty.post.opt7} just in the template by themselves to see if they show. Obviously, if they both don't show, then the comparison isn't going to work.

If it doesn't show, then I'm afraid it's back to the much more complex solutions that I mentioned earlier in this thread.

Try this instead, when using the code from step3 (so you already have all of the options including the values):
{if $smarty.capture.opt7 == "XXXX"} SELECTED{/if} <-- Where XXXX = the name of the value for the option.

Code:

<option value="opt1value" {if $smarty.capture.opt7 == "opt1value"} SELECTED{/if} />opt1value</option>

OK, Jason,

I think I figured out why it wasn't working. Apparently when you "capture" it for some stupid reason, adds a space before and after the text string!

So, simply try adding the smarty "strip" modifier to replace the spaces with nothing like this:
{if $smarty.capture.opt7|strip:'' == "XXXX"} SELECTED{/if} <-- Where XXXX = the name of the value for the option.

This worked for me.

Glad we were able to get that sorted for you.