phpMyAdmin is software typically installed by your host and available via your hosting control panel, it is not part of WordPress. A search on web for [your host] phpMyAdmin will probably tell you what you need to do.
Not sure how dramatic this’ll be, but it should improve nontheless: <?php /** * You can try forcibly splitting the query (grabbing IDs *then* all fields) * Works well for large post results. (available WP 3.4+) */ add_filter( ‘split_the_query’, ‘__return_true’ ); $posts = get_posts( array( ‘post_type’ => ‘listings’, ‘posts_per_page’ => -1, /* Disable term caching … Read more
Two Problems Problem #1 – You shouldn’t ever change the default schema that ships with WordPress. This schema might change in the future (entire tables could be dropped and re-built in an update). Problem #2 – You shouldn’t really be creating new tables in the first place. If you create a new table with your … Read more
Every time you edit a post/page, WordPress creates timely revisions of it. Check the Firebug console for the requests that are sent at regular intervals when you are on the edit page. They are useful if you lose the post content at some point and want to get back to an earlier version of the … Read more
Ideally, post meta should never be stored in a serialized form to begin with, thus making it easy to query. If the code uses the standard methods for storing meta instead of self-serializing it, then each item would be in its own row and easily queryable. If the data is stored serialized, then you have … Read more
This part in your table creation SQL looks wrong: DEFAULT CHARSET=CHARSET=utf8. It should just be DEFAULT CHARSET=utf8. Also, dbDelta() is quite a delicate function. Don’t ask me why, but you need to put a double space after the PRIMARY KEY keyword. You also need to get rid of the quotes around the field names because … Read more
The table wp_options can normally be queried using get_option() So you can use something like $testimonial_settings = get_option(‘testimonial_settings’); to retrieve the values of testimonial_settings. If the stored value is serialized, it will be retrieved as an array.
$wpdb is a global variable. You have to take it into your function’s scope first … global $wpdb; $wpdb->insert(); … or access it per $GLOBALS … $GLOBALS[‘wpdb’]->insert(); And I would use always lowercase keys; this is just a useful convention.
There’s a wpdb class in WordPress for you to be able to read/write DB. To get variable from table, use $wpdb->get_var function. This way: //set current page ID or define ID in another way – depends on your code $my_page_id = get_the_ID(); global $wpdb; $ListingID = $wpdb->get_var( “SELECT listing_id FROM “.$wpdb->prefix.”fsrep_listings WHERE ID = ” … Read more
I’ll answer this from a security perspective, please add additional detail to the question if you are more interested in the user interaction/UI/etc. side of things. You could argue that a password protected page offers far less security when compared to a default WordPress user, therefore you might want to setup up one or more … Read more