markparolisi

I’ve seen no issues with that zipped version you last supplied.

Understood. I’m going to leave things as-is for now and will continue to monitor. Thanks for this update.

This updated Zip is running on https://www.theyonkersledger.com/newsletter/ and seems to be fine so far. Thanks

https://www.theyonkersledger.com/newsletter/

Feel free to submit dummy email addresses to that live list. Just make them obvious so I can delete them later.

Now that you mention it, I can reproduce that bug.

I also notice an error in the console…

An error has occurred. [ File: ./wp-content/plugins/constant-contact-forms/assets/js/ctct-plugin-frontend.min.js?ver=2.4.0 ] [ TypeError: Cannot read properties of null (reading ‘querySelector’)

                        e.cache.forms[r].honeypot = t.querySelector(".ctct_usage_field"),

All good so far. Been doing routine functional tests just submitting data via forms created with the plugin. Both to CC subscriber lists and general contact form information submitted to an email address.

Sure, I’ll help where I can. Just let me know how to communicate changes if not via this support forum.

Much appreciated. Not sure where you are doing the development as I don’t see a public repo for this in your Github org, but I’d be happy to help test and review.

Thanks for your response.
And yes I agree that the CMS scripts for the form builder, etc are fine. It’s only on the client-facing front-end where we want to see a performance improvement by removing the jQuery library.

<?php

if(!empty(Multi_Post_Thumbnail::get_post_thumbnail_url($post_type, $id, $post_id, $size))){
 // show featured image
} else {
  // show default image
}

On a sidenote, LIKE queries are pretty expensive so you should cache those results.

No clue on that WPAlchemy side, but you should wrap all of your code in classes and just call the methods when you need them. For example you should have an admin_page class that generates your HTML and just call that in your display_function function. Just make sure you require_once all of the class files before you call them.

You should probably use admin_notices instead of throwing a JS alert.

no need to reset the entire query. just use wp_reset_postdata()

var_dump returns the value of the expression, in this case, is_admin returns the boolean value of true if you are on an admin page