Categories
Wordpress

How to selectively enable/disable plugins on a per page/post basis using Plugin Organizer

I am in perpetual pursuite of reducing page time. I think it not only helps your SEO ranking but also provides a better user experience. So it is a win-win. That said, when I ran a Speed Test on one of the page, I noticed it was loading some external 3rd party scripts that were slowing down the TTFB and First Paint time.

Upon further digging using webpagetest.org and gtmetrix.com, it was clear that Contact Form 7 (with Google Captcha enabled) was adding a few external scripts that were not needed. For example, I did not need the Contact Form 7 plugin loaded on the Cart and Checkout page.

What You Need

Process

Without further ado, I will present below the steps I followed. But before we do that, let me first acknowledge that these are the steps provided to me by the author of the Plugin Organizer plugin. I do not take credit for these. The plugin author is very helpful and guided me through this process. I hope you will find it useful.

Step 1: Determine what scripts/styles need to be excluded

First, you have to determine what scripts/styles are slowing down your page. For this you can use gtmetrix.com or any other speed test site if your preference. Usually, I use both gtmetrix.com and webpagetest.org together because they complement each other quite well.

Here is an example of the summary. Pay attention to the numbers highlighted. The page size and number of requests is very important for determining whether your un-needed scripts/styles are loading.

Fully Loaded Time, Total Page Size and Requests are important metrics that we will monitor

Now, let us dig a bit deeper. The Waterfall view of gtmetrix.com is where I find the scripts that I need to unload. The screenshot shows below the JS and CSS resources loaded for the page, sorted by Size. I find the Sorting feature useful because I can attain significant optimization by removing the bigger scripts/styles first.

All the CSS and JS resources loaded by the page (sorted by size)

After the speed analysis, I determined that I did not want Contact Form 7 to be loaded on all the pages.

Step 2: Configuration of Plugin Organizer

Brace yourself, this is not as easy as it seems. Plugin Organizer is a very powerful tool. It allows incredibly fine control over how and which plugins can be enabled/disabled on a certain page/post.

  • Install Plugin Organizer
  • Activate Plugin Organizer
  • Setup Plugin Organizer

Here is the screenshot for my settings for Plugin Organizer. Of note is the highlighted post types that I wanted to use Plugin Organizer for. Also, note the global settings. You can read up on each of these settings on the Plugin Organizer documentation site.

For me, the “Fuzzy URL Matching” and “Ignore URL Arguments” parameters need to be ON.

Disable the affected plugin globally. Here is the screenshot for my case – Contact Form 7 has been disabled Globally, i.e. it will not load at all on any pages/posts.

Step 3: Setup Plugin Filters

Here is the crux of it all. The logic, so to speak. In my case, I am enabling the CF 7 plugin on the 2 pages. Note the priority of filters.

Filter 1: CF 7

The 2 URL’s (permalinks) are the ones that this filter affects.

Filter 2: CF 7 JSON

In this case, there is only 1 URL that will be impacted. It is a specially formulated URL to select the URL that CF7 submits the form to. Notice the priority set to 4 in this case. The priority is important for this to work correctly, as it controls the execution order of the filters.

Step 4: Clear your cache(s)

After you have made the above changes, make sure to clear your cache(s) completely. Run the speed test again and verify that the un-needed scripts/styles are not being loaded anymore.

Conclusion

There you have it! With this configuration, I can successfully exclude a plugin from loading on a certain page/post. You may have to tinker with the priorities and Permalinks to get it working for your specific use case. Let me know in the comments if you think this is useful. For me, this was a great tool in easily reducing the page load time across the site in one shot. It is a clean way to exclude plugins from loading on every page.

Categories
Wordpress

[SOLVED] WordPress/WooCommerce Reset Password form not working

I am not sure when this started occurring, but recently a few of my users complained that they are unable to change their passwords. They click on the "Lost Password" link. They receive the email with the link to reset the password.

Upon clicking on the link, they are redirected to "https://…./my-account/lost-password/?show-reset-form=true". However, the Reset Password form does not show up. Instead, they receive the original Lost Password screen prompting them to enter username/email so the Lost Password email can be sent to them. 

So the users are in this circular loop. They are unable to change the password.

Looking at the relevant code (https://github.com/woocommerce/woocommerce/blob/a3ec0bf85aa6a55ed3241fc2a30a397e4b1273dc/includes/shortcodes/class-wc-shortcode-my-account.php#L215), it seems that the "wp-resetpass-" cookie is not being set. 

Ask your hosting provider if somehow they are caching the "my-account" and "lost-password" pages. If they are, that can explain this behaviour. Atleast, that was the case with me. Once those URL's were excluded from cache, the Reset Password" form showed up successfully. 

Have you experienced this issue before? What did you find?

Categories
ecommerce WooCommerce Wordpress

How to move the Archive Text in Genesis

For a while, I have struggled with how to remove or change location of the Archive Intro Text in a Genesis-based theme. Essentially, the idea is to move the Archive Intro Text towards the bottom of the page mostly for SEO purposes.

When I asked the questions on the StudioPress forums, I did not receive a satisfactory answer. So I did what most coders do: hack it till you discover how to do this way. Worry not, because this is not a hack. It is actually the recommended way to make a change like this.

Here is the code

/* Remove the Archive Headline and Text from the default location */
remove_action( 'genesis_archive_title_descriptions', 'genesis_do_archive_headings_open', 5);
remove_action( 'genesis_archive_title_descriptions', 'genesis_do_archive_headings_close', 15);
remove_action( 'genesis_archive_title_descriptions', 'genesis_do_archive_headings_headline', 10);
remove_action( 'genesis_archive_title_descriptions', 'genesis_do_archive_headings_intro_text', 12);
/* Now, add it back at the bottom */
add_action( 'woocommerce_after_shop_loop', 'ar_add_custom_hook_archive_description', 8);
add_action( 'ar_add_wc_archive_descr_text' , 'ar_do_custom_archive_description_text', 7, 3);
function ar_add_custom_hook_archive_description() {
global $wp_query;
if ( ! is_category() && ! is_tag() && ! is_tax() ) {
return;
}
$term = is_tax() ? get_term_by( 'slug', get_query_var( 'term' ), get_query_var( 'taxonomy' ) ) : $wp_query->get_queried_object();
if ( ! $term ) {
return;
}
$heading = get_term_meta( $term->term_id, 'headline', true );
if ( empty( $heading ) && genesis_a11y( 'headings' ) ) {
$heading = $term->name;
}
$intro_text = get_term_meta( $term->term_id, 'intro_text', true );
$intro_text = apply_filters( 'genesis_term_intro_text_output', $intro_text ? $intro_text : '' );
do_action( 'ar_add_wc_archive_descr_text', $heading, $intro_text, 'taxonomy-archive-description' );
}
function ar_do_custom_archive_description_text( $heading = '', $intro_text = '', $context = '' ) {
if ( $heading || $intro_text ) {
genesis_markup( array(
'open' => '<div %s>',
'context' => $context,
) );
}
if ( $context && $intro_text ) {
echo $intro_text;
}
if ( $heading || $intro_text ) {
genesis_markup( array(
'close' => '</div>',
'context' => $context,
) );
}
}

view raw
functions.php
hosted with ❤ by GitHub

The first 4 lines simply unhook the actions responsible for showing the Archive Intro Text at its default position. This will make sure the Archive Intro Text does not show up in its usual location.

The rest of the code moves the Archive Intro Text down to the bottom of the page, by hooking on to the “woocommerce_after_shop_loop” action. The trick is to get the relevant parameters passed to the function that eventually displays the Archive Intro Text.

This example is limited only to moving the Archive Intro Text. You will have to extend it to display the Archive Headline to the bottom.

Do let me know if you have any questions!

Categories
code ecommerce google analytics WooCommerce

How to Report WooCommerce Checkout Errors as Events in Google Analytics

Google Analytics Logo

For a while now, I have wanted to have visibility into what really happens on the WooCommerce Checkout page. More specifically, the goal is to determine why almost 50% of those visitors leave the site from the Checkout page?

Survey pop-ups could be one way of determining why they are leaving the site. However, personally, I consider those intrusive. Why not have a behind-the-scenes way of reporting the exact error(s) the user might be encountering?

At first, I envisioned that I could insert some JS code (specifically the GA Send Event JS code) within the relevant WooCommerce filter. In this case, it was going to be the “woocommerce_add_error” filter. However, that was not going to work, as I found that out after a bit of experimentation. Somehow, the JS code was being appended to the “checkout.min.js” file instead of being added inline. Later, I discovered that you can not add JS code in Filter Hooks. See this Facebook post in the Advanced WordPress group for that discussion.

The Solution

As I looked for how to solve this issue, another alternative method came to mind. What if I could trigger on the addition of the “<ul class=”woocommerce-error”>….</ul>” element to the DOM?

This way, the solution would be generic and can be extended for other notice types (warning, notice, message etc) as well. It could easily be used outside of the WooCommerce context as well. Ofcourse, you will have to change the correct class/id of the element being targeted.

Code Changes

function load_ga_error_script() {
// Load the JS file (jquery is a dependency)
wp_enqueue_script( 'ga-send-error-event', get_stylesheet_directory_uri() . '/js/ga-send-error-event.js', array('jquery' ) );
}
add_action( 'wp_enqueue_scripts', 'load_ga_error_script' );

view raw
functions.php
hosted with ❤ by GitHub

jQuery(function() {
jQuery('.woocommerce').on('DOMNodeInserted', function(e) {
if (jQuery(e.target).is('.woocommerce-error')) {
// How Many Errors
var error_count = jQuery('.woocommerce-error li').size();
// This extracts the contents of the <li></li> tags, separated by commas
var messages = jQuery(".woocommerce-error li").map(function() { return jQuery(this).text() }).get().join();
// Send the GA Event
// Event Category: WooCommerce Error Event Action: checkout-error-notice Event Label: Actual Error Message shown to user
// Event Value: How many errors were shown to this user
ga("send", "event", "WooCommerce Error","checkout-error-notice", messages, error_count, {"nonInteraction": 1});
}
});
});

view raw
ga-send-error-event.js
hosted with ❤ by GitHub

Explanation:

The code changes are split into 2 parts:

  1. Load the new JS file from within the functions.php of your child theme.
  2. ga-send-error-event.js should be located in the “js” folder of your child theme. If the “js” folder” does not exist, you will have to create it.

Testing

Once you make these changes, you can test it yourself in Google Analytics. But first, you will have to conduct your testing in an Incognito window (Google Chrome).

  1. Visit your Checkout page (preferably in an uncached and incognito browser session)
  2. Open your Developer Toolbar from the Browser (Chrome Dev Tools or FireBug)
  3. Leave all fields empty.
  4. Select a Payment Method and click on Continue
  5. You should see the messages printed above the Checkout Form
  6. Log into your GA interface
  7. Navigate to Real-Time->Events->Events (last 30 minutes)
  8. You should see new events generated under the “WooCommerce Error” category.

See screenshots below

New Category of events called WooCommerce Error
New Category of events called WooCommerce Error

In my case I had left the Billing First Name and Billing Last Name empty. Additionally, I had also left the “Terms & Conditions” checkbox unchecked. The Event Label got truncated, but if you hover over it, the full label is :

“Billing First Name is a required field.,Billing Last Name is a required field.,You must accept our Terms &amp; Conditions.”

Event showing Full error message
Event showing Full error message

So this is how I solved the issue of reporting error messages on WooCommerce checkout page. I am not sure how helpful this will be (I am hoping it will lead to better insight into the actions of the user on the Checkout page). Hopefully, it will reveal weaknesses in the UX.

What do you think? Is this something useful for you? Go ahead and use the code. Let me know if it works well for you. You can also easily extend this code to any part of the site (it does not have to be WooCommerce related).

Categories
Wordpress

How to Setup Algolia Search on WordPress with Genesis Theme

For those of you new to Algolia, this is another Instant Search solution for WordPress search. It is a 3rd party solution. The plugin is Free. The service is based on the free plugin on the client side communicating with the Algolia servers to retrieve search results for users.

The Algolia setup is very simple. You download the plugin from https://github.com/algolia/algoliasearch-wordpress. Install the plugin manually via your WordPress Admin. Create a new account on www.algolia.com.

For some reason, my drop down box containing the Search Results was not showing. It would only happen when using a Genesis theme. For other themes (I verified it worked with Storefront), it worked just fine. I posted in the StudioPress forums, but no luck. I inspected the Chrome Inspect Console but saw no JS errors.

I even tried disabling one plugin at a time, trying to figure out a possible conflict. No luck there either.

I decided to seek the help of Algolia’s support team. Sylvain Utard, the VP of Algolia Search came to my rescue. After a few experiements and emails back and forth, he figured out the issue. The issue was CSS related.

From my understanding, the Search Form overflow property was not visible by default in Genesis. The drop down for Algolia Search Results was always there, just invisible!

Here is the fix
.search-form {
overflow: visible !important;
}

Voila! That CSS change did the trick.