Group items tagged

“Warning: Missing argument 2 for wpdb::prepare()” How do I fix it? If you are seeing an error after upgrading to WordPress 3.5 that says something like this, you need to upgrade your theme. We have fixed this with all of our themes and they are ready to download and re-install from your account page. What if I have customized my theme’s code and don’t want to upgrade? For those of you who have customized your theme’s code and don’t want to do a full upgrade, you’ll need to take a look at the warning message. Here’s a sample error we have fixed from the Biznify Theme: Warning: Missing argument 2 for wpdb::prepare(), called in /home/mintthem/public_html/demo/wp-content/themes/Biznify/products-pagetemplate.php on line 39 and defined in /home/mintthem/public_html/demo/wp-includes/wp-db.php on line 990 Step 1: Open the file it tells you to open. In this case, it is products-pagetemplate.php and Go to the line it refers to. In this case it is line 39 Step 2: Find the code that looks like this: $wpdb->prepare(“SELECT price FROM $table_name WHERE item_number = ‘$item_number’;”) Step 3: Replace $item_number with %d Step 4: Add $item_number after the last quotation mark. Also, make sure to put a comma before it. (notice the comma before $item_number below) Example: $wpdb->prepare(“SELECT price FROM $table_name WHERE item_number = ‘%d‘;”, $item_number)

WordPress 3.5 And WPDB Prepare

a selection of common JavaScript libraries are already included that you can use for your JavaScript development

be selective about which pages you load your scripts on. If your plugin or theme has a script that only does something on one front-end or admin page, such as the theme’s options page, or maybe a page with a specific widget, you only need to load your script on that page. No point clogging things up and loading scripts on pages where they’re not being used!

it’s perfectly possible to prioritise scripts and styles and nominate whether they load in the header or footer from the comfort and safety of your functions.php. The benefit being that your theme / framework will work with a wider range of other plugins / child themes.