• Resolved Steven Ray

    (@steveneray)


    I added my own “Set your log file filename. (optional)” to “spam_log.txt” so that I can view it in the browser. After the last update, at the bottom of that page, the following JavaScript errors appear on every website installed:

    var wpcf7_block_log_domain = “https://www.domain.com”; var wpcf7_block_log_filename = “spam_log.txt”; if (wpcf7_block_log_filename==””){ wpcf7_block_log_filename = wpcf7_block_log_domain+”/wp-content/spcf_spam_block.log”; }else{ wpcf7_block_log_filename = wpcf7_block_log_domain+”/wp-content/”+wpcf7_block_log_filename; }

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Steven Ray

    (@steveneray)

    @nysl, two weeks and no response?

    Plugin Author NYSL

    (@nysl)

    Hello,

    Sorry for the delay, busy schedule didn’t let us see this request earlier.

    Our plugin DOESN’T use JS to set values. It looks like you are using an old version of another plugin, is causing this error.

    The error sample you provided is a piece from the PHP code of the plugin itself.

    Are you sure you didn’t use multiple plugins that they hook with Contact Form 7 simultaneously ? OR somehow you entered as a value that interrupts the PHP code execution ?

    After the domain name you have an html code for double quotation mark (&#8221) … Why is that ?

    Thanks,

    NYSL

    Thread Starter Steven Ray

    (@steveneray)

    “wpcf7” is the prefix identifier for Contact Form 7. It seems your plugin is conflicting with the plugin it is supposed to work with. As explained above, I added my own “Set your log file filename. (optional)” to “spam_log.txt” so that I can view it in the browser. The conflict appears to be the use of the text file option in your plugin in combination with Contact Form 7. I think the string appeared after the recent addition of CF7 apps and honeypot integration. This recent issue occurs on any website where Spam Protect for Contact Form 7 is installed. Thanks.

    Plugin Author NYSL

    (@nysl)

    Hi Steven,

    We’ve thoroughly investigated the issue and were finally able to reproduce the problem on our systems. It appears that the latest update to CF7 Ver6.1 (released a few days ago) is unexpectedly stripping a large portion of our plugin’s code, which we hadn’t noticed until now.

    This is an event that was outside of our control and was completely unexpected.

    We are currently working on an update for our plugin and plan to release it in the next few days.

    Thanks for bringing this to our attention.

    Best regards,

    NYSL

    Thread Starter Steven Ray

    (@steveneray)

    @nysl Thanks for the quick fix. It appears version 1.2.7 fixed the error.

    About the readme.txt changelog entries, you have them inverted. The oldest entry should be at the bottom and ascend to the newest entry on top. This is the general rule used by plugin developers.

    I have developed several plugins over the last decade: https://profiles.ww.wp.xz.cn/artiosmedia/#content-plugins

    Thanks!

    Plugin Author NYSL

    (@nysl)

    Hi Steven,

    Thanks for the sugestions.

    NYSL

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘JavaScript Error with Log Filename’ is closed to new replies.