Narthur

For anyone who is doing theme or plugin dev and runs into this issue, I discovered I had registered an empty callback function on the the_title filter which was catching every title and returning null. Expanding the callback along these lines prevented it from unsetting every title until I had a chance to build the callback out properly:

function setTitle($title)
{
    return $title;
}

I tried this:

jQuery(document).on('click','#un-feedback-submit',function() {
	console.log('Ow!');
});

Then I realized the form is in an iframe, so that doesn’t work.

I tried this in my theme’s functions:

function trackFeedbackSubmission() {
	echo '<script type="text/javascript">
		ga("send","event","form","contact");
		console.log("Submission tracking attempted");
	</script>';
}
add_action('un_feedback_created','trackFeedbackSubmission');

Which results in this error in the JavaScript console on form submission:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Same. Running WordPress 4.1 on a DreamHost one-click WP install.

That indeed fixed the issue.

I also went in and disabled it in Security’s settings. I’d like to turn away mode back on, but it’s not reading my timezone correctly. I have my timezone set in general settings to Chicago, making it a bit after 1pm. Security, however, is still showing the time as a bit after 7am. How can I resolve this discrepancy?

I’m sorry; it appears that I spoke too soon. My problem was not caused by your extension but rather by the url of my site being set in WordPress’ general settings as https:// instead of https://. Hopefully someone will be helped by this. =)

Thanks for the quick reply. =)

Has this been resolved?

Agreed! lol

Hmm, ok, that’s probably why. I’m no expert on such things. You’ll probably want to post to their support section.

Hmmm, not sure what that’s all about. Were you online when you tried to activate it? You might try posting in their support area.

It seems from what I’ve heard that WordPress has become a lot more strict about how people code their plugins, hence the new errors. We have a few options:

1. Downgrade PHP. Not a good option.
2. Downgrade WordPress. Not a good option.
3. Turn off error display and wait it out until the plugin author fixes the errors. May or may not be a good option.
4. Log errors but don’t display them, and use a plugin like WP Error Fix to view and filter errors by source.

As a plugin developer, I’ve settled on option 4 as it allows me to continue viewing errors that are relevant to me. So far it’s working very well.

Thank you for researching this, rethinkmarketing!

Until the plugin author updates the extension, I’ve gone to using the WP Error Fix plugin to view errors in place of displaying errors on the website. (Note that you’ll have to edit wp-config.php to turn off error display separately—this plugin won’t do it for you, as far as I know.) Anyway, works like a charm. Lets me filter errors by source so I can keep working on my own plugins even when other plugins are generating loads of errors.

Never mind, I just figured it out. For others who may be wondering: Simply click the trashcan in the right “sidebar” and click “Yes” to the message that comes up. It would be nice to be able to dismiss errors selectively, but this works.

I’m getting the same errors. Makes this plugin rather un-fun to use in a dev environment with errors set to display.

Glad I could be of some help. =)