1. Before beginning, be sure you have the latest cForms downloaded and unzipped from Delicious Days.

2. FTP to the plugins directory of the site, download a full backup copy of cForms.

3. Do a database backup in the wp-admin, if you haven’t already done it.

4. Deactivate cForms.

5. Upload the new cforms folder through ftp. (Be sure you are uploading the cforms folder and not the zip file name – this will cause cforms to have errors and partially work.)

6. Leave the ftp on for now – activate cForms again.

7. Go to the cForms admin page.

8. Does it say: It appears that cforms was not able to create abspath.php…?
If it does, start a new text file. Copy the green highlighted code cForms produced.
Looks like: <code>&lt;?php $abspath = ‘/home/www/domain-name.com/’; ?&gt;</code>
Paste that code into your new text file and save as abspath.php.
Upload that file to the cforms folder.

9. Refresh the cforms admin page to be sure it’s correct now.

10. If you see more notations at the top, such as upgrade database table, just follow the instructions. This isn’t as common anymore unless you’re upgrading a very old installation.

11. Final step: test one of the forms.

Failed tests:

1. Did you add the abspath.php file and is the path on that correct? If the installation is in a sub-directory, check to see that cforms recognized that and the sub-directory is showing at the end of the file path in abspath.php.

2. If cforms didn’t tell you to add the abspath.php file, check that it’s actually in the cforms folder anyway. If not, create one using the above code with the correct server path.

3. Is the cforms folder it’s own? In the plugins directory, when you open the cforms folder, do you see files or another cforms folder? If you see another cforms folder, you will have to open it, select all the files and folders, and drag them up one directory.

4. Follow this path in your ftp: cforms/js/. Download the cforms.js file and open for editing.
Just past the copyright information, look for this line:
<code>var sajax_uri = ‘/wp-content/plugins/cforms/lib_ajax.php’;</code>

If the wordpress installation is in a sub-directory, add it to the code like this:
<code>var sajax_uri = ‘/sub-directory-name/wp-content/plugins/cforms/lib_ajax.php’;</code>

Upload the file and re-test the form.

Unable to locate WordPress Plugin directory.

Warning: unlink(/tmp….

Unable to locate WordPress Content directory (wp-content)

How to fix:

The best solution is to create a new ftp login that goes directly to the sub-directory rather than to the root. This usually takes care of the problem right away. When you upgrade in the admin area, it normally asks you for this information before continuing.

If you don’t have control panel access for setting up a new ftp, Artyom’s Blog has a suggestion to try. I’ve not tested his method since I’ve had control panel access for all blogs that had issues, so try at your own risk.

Still having issues:

After clicking “Upgrade Database” – Fatal error: Call to undefined function: populate_roles_270() in /your-abspath/blog/wp-admin/includes/upgrade.php on line 904

For some odd reason, a wordpress file corrupts or does not always upload correct during manual upgrades. This actually resulted in issues through the entire admin. Simple solution was to re-upload the file: wp-admin/includes/schema.php

Yet one more issue to help:

Any error relating to tmp/anything directory couldn’t be found.

Add the following to the end of the wp-config.php file (but before ?>):

(I suggest this as a last resort if all else has failed to stop errors, but I have tested this method and it did resolve an issue for one site.)

Starting with 2.7 I typically deactivate and delete the automatic upgrade plugin after upgrade. But mostly of curiosity I left one on when upgrading to 2.7.1.

Question:
Should I definitely deactivate and delete the automatic upgrade plugin once upgrading to 2.7? Will it make a difference leaving it on?

Answer:
Yes. At the least it must be deactivated. It will cause an error during the attempt to auto upgrade if the plugin is still active. This won’t cause damage to your blog, but the upgrade will not work until you have deactivated the plugin.

This feature now being built-in to Word Press is very nice though. It skips several tedious steps from the the previous automatic upgrade plugin.

No Automatic Backup:
One important thing to remember though, you definitely need a database backup plugin now. It no longer takes you through the steps for backup during the upgrade.

I recommend WordPress Database Backup. It works very well, simple to use, and have used it myself to restore lost or corrupt databases with 100% success. This plugin also has automatic backup, which I highly rercommend taking the few seconds to set.

This has most commonly been used in the page.php file of the WordPress themes only, but can certainly be applied to any page that you would like the ability to set the h1 tag (or some cases, if you prefer, the h2 tag). Remember, it is recommended to set the default theme h2 tags displaying the header of the pages to H1 for an SEO advantage.

This documentation will demonstrate applying this hack to page.php in your theme, but can easily be understood from that point on doing the same to your template pages, index.php, single.php, etc.

Step by Step:
1. You will need to be using an installed version of WordPress at least 2.x or greater as this method uses the “Custom Fields” you will find toward the bottom of the page in the admin area as you create or edit pages or posts.

2. In your favorite editor for editing your theme pages, or using the Theme Editor under the Presentation tab of the WordPress admin area, open pages.php for editing.

3. In the default theme of WordPress or the theme you are using, you will see a section toward the top of the file that looks exactly like or similar to this:

It’s this line – <h2><?php the_title(); ?></h2> that you will be changing. It may not look exactly the same, but will almost always be enclosed in h2 tags.

You will want to replace the contents inside those tags, but it is highly recommended that if they currently say <h2></h2> to change those to h1.

4. Replace that line with the following:

So your file should now look similar to this:

5. Save the file and upload it to your theme folder or save the file in the theme editor.

6. Now you can edit or create new pages and use the custom fields to change the heading of the page without changing the actual title of the page.

7. To do this, as an example, let’s create a new page named “Test”.

8. Publish the page, then view it from your WordPress site.

9. You can see that not only the title in the browser, in the menu, and the heading of the page says “Test”.

10. Now back to the admin area, edit the page “Test”.
11. Scroll to the bottom of the editing area until you see “Custom Fields”.
12. You may have to click on the “+” sign to the right to see the area for editing these fields.

13. Here you will need to add “changeH1” to the key text box for the first time. Be sure that changeH1 is spelled exactly the same and the “H” is capitalized.

14. After you have done this the first time, you will be able to select the changeH1 from the drop-down box under the word Key instead. It is only necessary to add the key once with a value, and from that point, it will remain in the drop-down list to be selected easier.

15. Now change the header by typing a new one in the Value text box to the right. Let’s just test it out by typing “This is my new heading text”. Then click “Add Custom Field”.

16. Save and continue, or save the page now.

17. Go back to your site and refresh to see the change.

18. Now you can edit any page to display a different heading just by setting the “changeH1” key in the drop-down list and typing in the heading you want in value. Don’t forget to click “Add Custom Field”.

19. If you have already set a heading in a page using this method, you can also go back to editing the page, and change the value in the box just above where you set it originally. After making the change click on “update”.