WordPress.org

Ready to get started?Download WordPress

Forums

Fast Secure Contact Form
[resolved] ReferenceError: VC_FSCF_set_cookie is not defined (5 posts)

  1. linux4me2
    Member
    Posted 1 year ago #

    I'm using WP 3.5.1 and Fast Secure Contact Form 3.1.8. Firebug is showing the following error on the Fast Secure Contact Form Settings page on the Admin side:

    ReferenceError: VC_FSCF_set_cookie is not defined

    and gives this file path:

    /wp-admin/plugins.php?page=si-contact-form/si-contact-form.php
    Line 1096

    I also see this error in 3.1.7 on WP 3.5.1. I searched but couldn't find anything on this.

    Oddly, I'm not getting a PHP error in the wp-admin directory where plugins.php is.

    http://wordpress.org/extend/plugins/si-contact-form/

  2. linux4me2
    Member
    Posted 1 year ago #

    I found where this is coming from and why there is no PHP error. It's a javascript error, but it's pointing to a PHP file, which threw me off.

    The function VC_FSCF_set_cookie is actually called on the FSCF admin options page in this block of code:

    <a id="vCitaSectionAnchor" data-user-changed="false" name="vCitaSettings"></a>
        <p class="submit">
          <input type="submit" name="submit" value="Update Options ยป" />
        </p>
    
    		<script type="text/javascript">
    			VC_FSCF_set_cookie("48500", "confirmation_token=<token here>");
    		</script>
    
    <div class="form-tab">Meeting Scheduler - by vCita: (form 1)</div>

    So it actually has to do with the vCita section of the options.

    It looks like the javascript file or code that is supposed to have the VC_FSCF_set_cookie function is not being loaded, maybe?

  3. Mike Challis
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks, I will look into fixing that

  4. linux4me2
    Member
    Posted 1 year ago #

    No problem. Thanks for such a great plug-in. If there is anything I can do let me know.

  5. linux4me2
    Member
    Posted 1 year ago #

    You got it. I installed the update you just released (3.1.8.1) and the error is gone. Thanks!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic