{"id":10831,"date":"2014-11-30T05:08:20","date_gmt":"2014-11-29T18:08:20","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=10831"},"modified":"2014-11-30T05:08:20","modified_gmt":"2014-11-29T18:08:20","slug":"mysql-wordpress-issue-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/mysql-wordpress-issue-primer-tutorial\/","title":{"rendered":"MySql WordPress Issue Primer Tutorial"},"content":{"rendered":"
\"MySql<\/a>

MySql WordPress Issue Primer Tutorial<\/p><\/div>\n

The WordPress Blog uses MySql as its database and PHP as its language. A great interface between these two worlds is the stupendous, the marvellous, the life-saving, phpMyAdmin<\/a>, an interface into the MySql database written in PHP. You will see it in action a lot if you administer a WordPress Blog, and it was used during MySql Repair Table Primer Tutorial<\/a> as shown below.<\/p>\n

Today we talk about the same issue, that is, what you do when a WordPress Blog administration piece of functionality is not behaving as expected.<\/p>\n

The issue, on this occasion, was, while maintaining comments in the WordPress Blog we were receiving the error message “No comments awaiting moderation\u2026 yet.” (and say error<\/i> here because we happened to know there were comments awaiting moderation (doh! if you have just started your blog) … the approach of “sticking your head in the sand and hoping it will go away” (ie. SYHITSAHIWGO) doesn’t often work with database work … though, that being said, users can create unrealistic queries that can cause issues … or things can become too busy and so have a read of watchdog<\/a> blog postings here):<\/p>\n

No comments awaiting moderation\u2026 yet.<\/i><\/b><\/p>\n

    \n
  1. \n

    First thing about resolving such an issue is … have a look to see whether the error is logged in the WordPress Blog error_log<\/i> file, which sits in the WordPress Blog (sub)domain’s document root directory.<\/p>\n<\/li>\n

  2. \n

    In our case there was nothing to note, but often there is, and often you get ideas about how to start resolving the issue from the error message.<\/p>\n<\/li>\n

  3. \n

    Next approach can be to submit a query to a search engine … such as (ie. often put exact error message in quotes) … like this<\/a>.<\/p>\n<\/li>\n

  4. \n

    For our case this lead to this excellent link<\/a> (this resolving advice we’ll talk about more below) … but should such a search lead to nothing concrete, for WordPress, it can be good to ask a question on the WordPress Forum<\/a>.<\/p>\n