Toby

The wpdb::prepare() method is used substitute values into a SQL statements safely. The first argument is the format of the SQL statement, with placeholders for the values, & the second is an array of values to use. If these aren’t present I’m not sur why you’d be using the prepare() method at all.

Without seeing the plugin code it’s difficult to advise how to fix, but if it’s not going to actually escape any values, you could remove the prepare call…

$sql = "SELECT * FROM ".$wpdb->prefix."background_partner WHERE Category LIKE '".$type."'";

Of course, search loads before posting… then find the answer immediately after posting…

You can use the register_taxonomy_for_object_type() function to link a taxonomy to a post type after it’s been registered.

Hi libets,

Somewhere in the code you’ve copied there is likely to be a call to register_post_type().

The 2nd parameter of this function supports an array of settings, one of which is ‘taxonomies’. This should be set to the taxonomy you wish to associate the custom posts with (category, tag, custom_taxonomy, etc.) It can be a string or an array of linked post types.

The full documentation on this function can be found here…
https://codex.www.ads-software.com/Function_Reference/register_post_type

Hope this helps.

My bad. The “while ( have_posts() ) : the_post();” call was in the other conditional statement.

All fixed now.

Not sure if it helps, but you may need the Contact Form 7 to Database plugin to persist the data on the new page? Anyone know how this might work?

https://www.ads-software.com/extend/plugins/contact-form-7-to-database-extension/

Hi there,
I have the sam issue for an app that I developed for a client. It’s not WordPress, but came across this via Google.
Not sure what to do about this yet, but still researching.
T