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?
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
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.
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
Explanation:
The code changes are split into 2 parts:
Load the new JS file from within the functions.php of your child theme.
ga-send-error-event.jsshould 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).
Visit your Checkout page (preferably in an uncached and incognito browser session)
Open your Developer Toolbar from the Browser (Chrome Dev Tools or FireBug)
Leave all fields empty.
Select a Payment Method and click on Continue
You should see the messages printed above the Checkout Form
Log into your GA interface
Navigate to Real-Time->Events->Events (last 30 minutes)
You should see new events generated under the “WooCommerce Error” category.
See screenshots below
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 & Conditions.”
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).
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.
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; }
When you Google the phrase “replace Add to Cart WooCommerce” (or any variants thereof), there are a lot of SERP’s suggesting the same way of hiding/not displaying the Add To Cart button. The idea is to remove the “woocommerce_template_single_add_to_cart” action.
Replace “Add to Cart” for Custom Products
However, in my case, I wanted to do this for only certain specific products. I have products that are marked as “Custom”, i.e. not stocked products. These are products that can be customized as per the customer/client. They usually take 6-8 weeks from order to delivery. The idea for the landing pages for these “Custom” products is not for them to make the purchase outright, but get them to contact the store owner. This way, the process of designing the custom product can be taken offline.
How to Designate a Product as “Custom”
The first step is to identify the products as “Custom” in WooCommerce. Following this guide by Remy Corson, I added a Checkbox under the General tab in the Product Edit Screen. When this Checkbox is checked, it means that the Product is “Custom”.
“Custom” product
As you can see in the image above, this product is defined as “Custom”.
Next up, we have to hook into the correct action for marking all “Custom” products as not being allowed for Purchase. We will use the is_purchaseable() hook for that purpose.
Alternative CTA for “Custom” Products
I wanted a form to take the place of the “Add To Cart” button. In my case, I use Contact Form 7 for my forms. I just added a small form specifically for the purpose of this CTA. The visitors will see this form in place of the Add to Cart button. The store owner receives an email containing the lead.
We are simply checking if the Product is “Custom”. If it is “Custom”, we will set it as being non-purchaseable. This will hide the “Add To Cart” button for such “Custom” products.
Full Code Listing
Here is the full code. Notice that 2 other custom fields were added. You do not need those, so you can easily delete the relevant lines of code.
Questions/Comments? Type away in the comments below.
