Changing Gravity Forms Description Location

GravityForms received a feature request two years ago to add the ability to change the description location on the forms from below the input boxes. Instead of putting it AFTER the field, the request was to place the box description above them.

Last year, they listed it as a future feature, but as of version 1.6.9, (today) this feature is still not available. They do still have this on their list for a future release, but in the mean time, this can be accomplished by adding a piece of code to your theme’s header.php.

To move the description from this location:

To this location:


Place this code in your theme’s header.php just before the </header> tag:

 <script type="text/javascript">
    jQuery(document).ready(function($) {
        $('.gfield_description').each(function(i,e){
            fielddesc = $('<div>').append($(e).clone()).remove().html();
            $(e).siblings('label.gfield_label').after(fielddesc);
            $(e).remove();
        });
    });
 </script>

After you’ve added this code, you should take a few minutes to view your site in a browser that you can easily see if there are any javascript errors, such as Internet Explorer.

If adding the above code causes any conflicts with your other plugins or custom theme code, you will see a yellow error warning in the bottom left corner of Internet Explorer.

Remember too, that this change could cause your other plugins or custom code to stop working. If that happens, just remove the above code you added or if you’re more experienced with working with your plugins and code, you can try to adjust the conflicting plugin(s) or code.

*** Update 2014 – At some point this became a non-issue since the feature was added to WP. However, if you don’t see the option to relocate the description, see the very last comment for my guess why.

Read More

Scentsy Theme Menu Fix

Scentsy recently made a change to the About link on their consultants corporate site to point to a different URL, and didn’t redirect the old URL to the new.

Under normal circumstances, best practices and common sense would dictate that you should take care not to “break” the incoming links that come to their site from other websites,  Facebook, etc. but in this case, Scentsy didn’t do that, so everyone link ended up broken.

When we first noticed it, we assumed Scentsy would catch and fix it, but they still haven’t, so you have to fix it yourself. If you have a WordPress theme of your own, you’ve may have already figured it out under Appearance > Menus.

If you don’t know how to do it, or if you bought your theme from us a while ago and didn’t even realize your  link was broken, here’s a very short video showing you how to fix it…

[imaioVideo v=1]

Read More

Changing Our Domain Name?

As a consultant, as far back as 2007, when businesses used to come to me in need of redevelopment, I would tell them that the best thing they could do was to “get WordPressed”.

I explained how they needed to take their dinosaur HTML site and have it converted into the most search friendly system I knew of, and that’s how this particular website was born.

It’s a specialized niche site, to fit the growing industry of converting sites into WordPress, and that’s how the domain name came to be chosen.

Yesterday however, attorneys for the WordPress Foundation sent me an email, saying that we are in violation of the WordPress copyright by using WordPress in the domain name. ;(

On the one hand, I realize that a company does have the right to protect themselves from misuse of their trademarked name or logo, but on the other hand, I’m surprised that they have nothing better to do with their time than go after supporters like us, who provide services based on their product.

Here’s a copy of the letter in its entirety:

Re: Trademark Infringement By

Dear Mr. Hendison:

I write on behalf of the WordPress Foundation to ask that you stop all use of the domain and transfer it to WordPress and that you also remove the WordPress Logo from your site. As you know, our client is one of the world’s most famous providers of blogging and website support services and offers these services under its famous WORDPRESS trademarks. It has used its WORDPRESS trademarks for many years and this trademark is the subject of many trademark registrations throughout the world including the United States.

As I am sure you can understand, in business a company’s brand is its reputation with customers. For this reason it is critical that a company have the ability to control how its brand is presented to the public. Further, the company has set out its domain name policy on the WordPress.org website as follows: “For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you not use “WordPress” in the domain name.” http://wordpress.org/about/domains/

Your use of the domain name(the “Subject Domain”) and your use of the WordPress Logo is without the permission of WordPress and removes its brand reputation from its control since visitors to your website will wrongly believe that the site is controlled by, or at least approved by WordPress when this is not the case.

In order for the company to maintain control of its reputation, we ask that you transfer thedomain to WordPress and remove all uses of the logo from your website. Should you care to discuss this matter please don’t hesitate to call or email me. I await your reply.

Very truly yours,

Steven M. Levy, Esq.
FairWinds Partners, LLC
1632 Wisconsin Avenue, NW
Washington, D.C. 20007
United States
+1-202-341-3722
steve.levy@fairwindspartners.com

Now I really don’t have the time or money to get into some legal battle that I would probably end up losing in the long run, so I said I would come up with a new domain, and would remove their logo (as obfuscated as it is) from our header.

Our communication back-and-forth has been very cordial, and Mr. Levy said that they could give me a reasonable amount of time to make the switch, get the new site indexed, etc. but I can’t find a domain name I like yet this morning.

We’ve established a pretty good  business here, and we’ve got some good search rankings, decent backlinks, and a loyal base of returning customers who know us by name.  Changing domain names is really going to require some thought, and this morning I set out to get one.

My first thought was to follow the suggestions that WordPress makes here and use a WP instead of their name, but when I tried to buy GetWP.com I found that it was already taken.  I was surprised at that, so I tried to visit the site, but when I did,  I got redirected to a subdomain of WP.com, called get.wp.com –  Huh? Could it be?

Yep – I looked up the registrant information, and found that the domain I want –  GetWP.com –  is already owned by the folks at WordPress – The same people telling me to use WP!

Registrant:
   Automattic, Inc.
   60 29th Street
   #343
   San Francisco, California 94110-4929
   United States

I really like the name GetWP.com, and feel it would be a fair substitution – after all, they’re not even USING it!  So I wrote the lawyer back just now, asking if maybe they’ll consider giving me getwp.com, but I’m not going to hold my breath.

Anyway, I thought I’d share – After they refuse, have you got any ideas for me for another good domain name?

Read More

Scentsy WordPress Themes

We’re excited to be working with another company on a new design that will enable Scentsy consultants to have an affordable theme that meets their desired look and feel. This theme will be in 100% compliance with the Scentsy corporate guidelines.

Update August 26 2011 – It’s here – $39 for one color or $99 for all six.

(Either JavaScript is not active or you are using an old version of Adobe Flash Player. Please install the newest Flash Player.)

Read More

Optimize Your Database

One of the drawbacks to using WordPress is the fact that if you work hard on your website, not only by adding content regularly, but perhaps changing your page copy, trying different calls to action, working on conversions, etc. then your database can ultimately grow quite large.

While a problem may not present itself for months or years, it’s reasonable to assume that someday, something will go wrong and you’ll wish your database was smaller and cleaner. Perhaps it will come during a routine upgrade and you’ll notice something’s out of whack, or the automatic upgrade will fail, forcing you to upgrade manually.

On the other hand, you might discover a problem only after something has gone seriously wrong – like while trying to restore a backup after a loss – and at that point, to put it technically, you are screwed.

Because we manage a lot of domains on a lot of different hosts, we’re probably a lot more prone to see a problem than you are, however, it never hurts to be safe, and be proactive. That’s why it’s a good idea to keep your database clean of unnecessary data.

A few weeks ago, while dealing with a site that had literally hundreds of revisions for every page, and a giant database that was giving us problems moving from one server to another, I looked for a plug-in that would get rid of all these revisions that we no longer needed.

I found a good one in WP Optimize, that not only gets rid of unwanted revisions, but also optimizes the database tables, which was previously only accessible through your web hosts phpMyAdmin.

Rather than tell you all about it, take a look at this 2 minute video…

 

Read More

WordPress Shopping Cart PCI Compliance

There’s a set of requirements called the Payment Card Industry Data Security Standard (or “PCI DSS”) and it was developed by the PCISSC – (the Payment Card Industry Security Standards Council)

These requirements are designed to provide a standardized set of consistent security measures for merchants to follow that are handling credit card transactions.

The standard includes 12 requirements for maintaining a secure operation:

Build and Maintain a Secure Network

  • Requirement 1: Install and maintain a firewall configuration to protect cardholder data
  • Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters
  • Protect Cardholder Data
  • Requirement 3: Protect stored cardholder data
  • Requirement 4: Encrypt transmission of cardholder data across open, public networks

Maintain a Vulnerability Management Program

  • Requirement 5: Use and regularly update anti-virus software
  • Requirement 6: Develop and maintain secure systems and applications

Implement Strong Access Control Measures

  • Requirement 7: Restrict access to cardholder data by business need-to-know
  • Requirement 8: Assign a unique ID to each person with computer access
  • Requirement 9: Restrict physical access to cardholder data
  • Regularly Monitor and Test Networks
  • Requirement 10: Track and monitor all access to network resources and cardholder data
  • Requirement 11: Regularly test security systems and processes
  • Maintain an Information Security Policy
  • Requirement 12: Maintain a policy that addresses information security

For WordPress your E-commerce options are limited, and for a PCI Compliant shopping cart, they’re limited even further.

There is no way in a million years you should consider developing a new site using ANY shopping cart that is not willing to be compliant or in my (non legal) opinion, you’re setting yourself up for a lawsuit.

This list of WP shopping carts and their PCI compliance info will grow over time…

  1. Shopp – They are compliant, and they are willing to say so, partly why they are one of our current chosen platforms.
  2. Eshopp – We love this free plugin. By shifting all cardholder data entry onto Authorize.net, there are no compliance issues. Sweet!
  3. Cart 66 – They say they’re compliant right on their home page.
  4. PHP PurchaseThey say they’re compliant right on their home page.
  5. Cart 32 – They do claim compliance.
  6. Vevo CartThey DO claim to be compliant
  7. WooThemes – They offer various add-ons 

These carts are either Non Compliant or simply not addressed on their sites:

  1. WP Ecommerce – Although we HAVE tested and passed compliance once and found no issues,  they now seem to fail any test, so we’ve given up.  They offer no statement about compliance, either that we could ever find, even using Google to search their site
  2. WP Auctions –  No mention of PCI Compliance – check.
  3. WP eStoreNo mention of PCI but they use something called instant digital product delivery – check
  4. Shopper PressHas more than 20+ payment gateways, but not PCI compliant?  check
  5. Market ThemeNo mention of PCI Compliance – check.
  6. Word Press Shopping Cart Plug-inNo mention of PCI compliance – check.

In the comments below, please leave any links to compliance info for anyone you come across, and I’ll update this list. Likewise, if you have information about anyone that’s NOT compliant, that would be helpful too.

WP Ecommerce – What You Should Know

If you need to learn a lot about PCI compliance, this is pretty damn good…

[imaioVideo v=1]

Read More

Upgrading cForms Plugin

Tip on some steps: Before creating or editing files such as abspath.php or cforms.js, change your local directory to a folder named after the site you’re working on. This will help prevent accidental uploading of these edited files for one site onto another, which will cause the forms to stop working. Having these for backup for each site worked on also comes in handy.

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.

Read More

WordPress and Plugin Upgrade Issues

If you blog is installed in a sub-directory rather than the root, here is a list of common errors being seen when attempting wordpress upgrades or installation, upgrade, or removing plugins in wordpress versions 2.8+:

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 ?>):

//Added the line below to correct issues with failing upgrades
//and inability to add plugins through the admin area.
putenv('TMPDIR=' . ini_get('upload_tmp_dir'));

(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.)


Read More

WordPress Automatic Upgrade Has No Backup

It may be common knowledge or common sense, but here’s a quick Q & A on the new built-in upgrade feature of Word Press 2.7 and up.

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.

Read More

PCI Compliant Cart for WP e-commerce

We are happy users of the WP e-commerce shoppping cart not only for our own site but we use it often for clients as well.

Recently, one of our customers told us that they were being required by their credit card company to pass a certification test verifying that their website was PCI compliant and wanted us to attend to it.

The company doing the compliance check was called Trustkeeper, and I’m very proud to report that right out of the box, with no changes on our part related to their cart, WP e-commerce passed the PCI compliance test with flying colors.

I don’t pretend to be an expert on PCI compliance, but I can tell you that we had no problem passing the test using the WP e-commerce software. We did have some server configuration changes, but those were unrelated to the WP or the cart plugin.

If you’re a WordPress lover and you’re in need of a shopping cart too, this one will meet your needs…   Please tell them that Scott sent ya!

Read More