Yesterday, I wrote a plugin and uploaded it to my website. I activated it and it activated successfully.
But when I deactivated it, the page turns blank.
On returning to the WordPress admin page, the plugin was successfully deactivated.
I was also getting problems when I added custom field.
The cause ?
A blank line at the beginning of my plugin file.
Deleting the blank line and letting the first line be <?php solved the problem.
If you are using
Yoast’s Google Analytics for WordPress plugin
and
a Thematic theme with a child theme, Yoast’s plugin might warn that the plugin might not work.
Yoast advises to include wp_footer() in footer.php.
Actually that is not necessary as the Thematic theme files already include it.
It is a false warning and the plugin will work, despite the warning.
Here is a screenshot from the source code of this website with the plugin activated.
Why might you want to use the plugin instead of just putting the Google Analytics code in a text widget ?
Well, text widget code disappears when you upgrade a theme.
With a plugin, you won’t have to retype the Google Analytics code.
From the results I get from querying for ‘custom field unindentified error has occurred‘, this is quite a common problem.
I followed many wild goose chases from repairing the database to deactivating plugins.
The solution is actually understanding that a custom field is a field that you have to enter a value for.
So I should select the field and then enter the value for the field. In this screenshot, I chose the ‘private’ field and entered the ‘yes’ value, then clicked on Add Custom Field.
This is how a successfully entered Custom Field post look like.
Regular updates are what blogging’s all about, but sometimes you want to keep hot topics or other static info at the top of your posts. This feature has existed as Sticky Topics in the forums, but hasn’t been available on blogs. Until now.This feature might be a good reason to upgrade to WordPress 2.6.2.
If anything has gone wrong the first thing to do is go through all the steps in our extended upgrade instructions. That page also has information about some of the most common problems we see.
Upgrading WordPress « WordPress Codex
I recently upgraded WordPress manually following the instructions at Upgrading WordPress « WordPress Codex. Soon after, when I tried to post using Windows Live Writer, I received the xmlrpc.php invalid response error. This does not happen if I upgrade using Fantastico.
WordPress support forum led me to think that the problem was with my blog client, Windows Live Writer.
It seems I am not alone, Joe Cheng at Microsoft received a lot of complaints about Live Writer not working after upgrading WordPress.
Actually, the problem is not with Windows Live Writer, it’s with the WordPress upgrade instructions.
Briefly, Upgrading WordPress « WordPress Codex says:
copy contents of downloaded zip file to:
1. wp-admin directory
2. wp-includes directory
3. wp-contents directory
But it neglects to tell you to also overwrite the contents of the root directory with the files from the zip file.
This screen capture shows some of the files at the root directory.
As it turned out, one of the files in the root is xmlrpc.php.
After I overwrote the root files, Windows Live Writer posts fine to my blog.
All newbies who is looking for a good blog platform to start a blog, a marketable, searchable blog, go with WordPress.
In this interview with Matt Cutts, he said that WordPress blogs are SEO.
Step number three is smart marketing and that can involve good SEO. If you do everything on WordPress you’re pretty much automatically covered as far as SEO
After a long lapse, I wanted to make a post to this blog again and got an XMLRPC 404 error.
I was blogging with Windows Live Writer. It did not give problems earlier and I have not upgrade my WordPress software.
A quick search on Google pointed me to Simply Buzz. I tried his suggestion of putting
<Files xmlrpc.php>
SecFilterInheritance Off
</Files>
in the .htaccess file and it worked.
In the old days before Internet, it would have taken me days to figure an obscure problem like this but thanks to Google and the internet and kind folks like Simply Buzz, I was back blogging this second post within the day.