PhpLD3 - How to disable reciprocal link

I want to remove reciprocal link option in the submit form but i can not find where this configuration was I am using Phpld 3.x.

Thanks.

 

admin panel Settings>Directory

Cheers

 

Open your submit.tpl

Find these line and remove them:

   {if $price.reciprocal gt 0}
      <tr><td><input type="radio" name="LINK_TYPE" value="reciprocal" {if $LINK_TYPE eq 'reciprocal'}checked="true"{/if}>{l}Regular links with reciprocal{/l}</td><td>{$smarty.const.HTML_CURRENCY_CODE}{$price.reciprocal}</td></tr>
   {elseif $price.reciprocal eq 0}
      <tr><td><input type="radio" name="LINK_TYPE" value="reciprocal" {if $LINK_TYPE eq 'reciprocal'}checked="true"{/if}>{l}Regular links with reciprocal{/l}</td><td>{l}free{/l}</td></tr>
   {/if}

Code (markup):

and

   {if $ShowReciprField == 1}
   <tr>
   <td class="label">{if $recpr_required}<span class='req'>*</span>{/if}{l}Reciprocal Link URL{/l}:</td>
   <td class="field">
      <input type="text" name="RECPR_URL" value="{$RECPR_URL|escape|trim}" size="40" maxlength="255" class="text" />
      {validate form="submit_link" id="v_RECPR_URL" message=$smarty.capture.invalid_url}
      {validate form="submit_link" id="v_RECPR_ONLINE" message=$smarty.capture.url_not_online}
      {validate form="submit_link" id="v_RECPR_LINK" message=$smarty.capture.recpr_not_found|replace:'#SITE_URL#':$smarty.const.DEFAULT_RECPR_URL}
      <br />
      <p class="small">{l}To validate the reciprocal link please include the<br />following HTML code in the page at the URL<br />specified above, before submiting this form:{/l}</p>
      <textarea name="RECPR_TEXT" rows="2" readonly="readonly" cols="50" class="text">&lt;a href="{$smarty.const.DEFAULT_RECPR_URL}"&gt;{$smarty.const.DEFAULT_RECPR_TITLE}&lt;/a&gt;</textarea>
   </td>
   </tr>
   {/if}

Code (markup):

Let me know if you face any problem

 

Thanks. It worked. Rep added.

 

this method did not work for me too, when i tried to disable it. Had to go into the code myself and disabled it. Probably similar to what was suggested above.

 

so does that mean a bug in the directory ?

 

i know that there is a bug in mine, but mine is not the latest version, perhaps it has been corrected in the latest version.

 

Yes, it has been fixed in the latest version 3.2.