Found snow mold

I have noticed some themes generate error messages under certain conditions. I am trying to fix code so broken themes, widgets, and plugins work perfectly.

The most popular errors in the server logs are when widgets are used to display content you haven’t created yet. For example, including a recent comments widget in your sidebar, before you actually have any comments will result in an error message. I included a Links widget in PingoLino, but I didn’t have any links, hundreds of errors.

Trying to sort out which errors I need to pay attention too, and which errors are merely the result of carelessness is tougher than I expect.Feed validator helps.

If you notice errors occurring in a particular theme, widget, or microcontent, let me know ASAP. Show me while you are at school.

When activating a new blog, don’t be in a rush to delete the default Mr. WordPress links or Hello World posts or comments. Having empty posts or comments or empty Blogroll causes errors to be reported as well. Most errors vanish after content, links, categories are added to your blog.

I’m certain you’ll see a rash of bizarre behaviour if you allow anyone else to be an administrator, author, contributor of your blog, I did in testing. If user A and user B both administer the same blog, all links/content appear on the pages they are supposed to, but when user A tries to Manage Links or Posts, only A’s posts and links appear and can be edited. This merely confused me, causing momentary panic, then confusion. Add users to your blog at your own risk. Do not make them Administrators, unless you know what you are doing and why. Anything you actually delete from your blog is gone. But stuff can be hidden in very many mysterious ways. Take care.

D. Sader

This entry was posted in Uncategorized and tagged , , , , , , , , , . Bookmark the permalink.

Warning: count(): Parameter must be an array or an object that implements Countable in /home/dsader/public_html/dsader/wp-includes/class-wp-comment-query.php on line 399