Plugin updates – October 2024

Current versions of plugins in October 2024: WooCommerce Simple Auctions v3.0.3, WooCommerce Lottery v2.2.5, Lottery Pick Number v2.6.4.2, WooCommerce Group Buy Deals v1.2.2, WooCommerce Simple Bulk Discounts v1.0.12, WooCommerce Simple Storewide Sale v1.1.8.

Before updating make backup (just in case) and read changelog to see what’s updated in new plugin release and decide if you need to update.

ClassicPress – Get Simple Auctions, Lottery and Group Buy running on lightweight WordPress fork

ClassicPress Get Simple Auctions, Lottery and Group Buy running on lightweight WordPress fork

ClassicPress is WordPress long awaited fork of WordPress 4.9 (from version 2.0 fork of WP 6.2.x) without Gutenberg block editor, basically a lighter fork of WordPress with a few tweaks and improvements. It is under active development, has less bloat and has latest security patches. You will love overall simplicity and speed.

Most popular themes and plugins that work with WordPress 6.x are compatible with ClassicPress and there are forks of WooCommerce called ClassicCommerce and RankMath called Classic SEO (for more infos see link here).

Update: ClassicPress v2.0+ is a re-fork based on WordPress 6.2.x so brings ClassicPress a host of new features. Release notes are here. There is also https://directory.classicpress.net/ for native plugins and themes.

WooCommerce Simple Auctions running on ClassicPress v2.2.0 – https://wpgenie.org/classicpress-wsa/ – here is how we have setup it https://wpgenie.org/classicpress-wsa/setup/

Setting up prerequisites in ClassicPress

First thing to do when installing one of our plugins on ClassicPress is to decide what version of WooCommerce you will use. ClassicCommerce is fork based on WooCommerce v3.5.3 and usually needs tiny compatibility plugin (get it here) which allows WooCommerce addons to work with ClassicCommerce. We used StoreFront theme.

classicpress-plugins-list
Plugin list in ClassicPress

Another option is regular WooCommerce installation but version that does not include (register) blocks for Gutenberg like WooCommerce v4.8.3 – scroll to the bottom and download version you want from wordpress.net/plugins repository. Once WooCommerce is ready you can install our plugins like you would on normal WordPress website.

Payment gateways tested in ClassicPress

Payment gateway we tested beside those that are preinstalled with WooCommerce is WooCommerce Stripe Gateway version 5.3.0 since that is the latest one that works fine with WooCommerce v4.8.2. Here is sample order done using test card with Stripe GW:

classicpress stripe order using test card plugin woocommerce stripe payment

Using our plugins on ClassicPress

There is no difference in how you use and work with plugins. Everything from documentation applies here. Install it, setup couple of products, make couple of orders and that’s it. Once deal, auction or lottery ends you and users will get notifications (if that is set), normal workflow is not affected in any way.

WooCommerce Lottery with Pick Number Mod addon
WooCommerce Lottery with Pick Number Mod addon

Here is screenshot of how auction product looks like:

ClassicPress with WooCommerce Simple Auction auction single product page

And screenshot with WooCommerce Group Buy / Deals product:

classicpress group buy deal product
Group Buy / Deal single product page

In this simple guide we have shown how you can use our plugin on ClassicPress setup and enjoy its superb performance. Easy on hosting and great for your visitor’s user experience.

Privilege Escalation Vulnerability in WCFM

Wordfence team reported a Privilege Escalation via Account Takeover vulnerability in WCFM – WooCommerce Frontend Manager, a WordPress plugin with more than 20k installations. Some of those sites are also our clients using our Auction, Group Buy and Lottery plugins so we urge them (and all other using the plugin) to update WCFM to the latest version.

This vulnerability makes it possible for an authenticated attacker to change the email of any user, including an administrator, which allows them to reset the password and take over the account and website. Full article is here and tech details are here.

Coming Soon / Site visibility available as part of WooCommerce from v9.1

WooCommerce now includes a feature that allows you to easily set your website to “Coming Soon” mode, negating the need for a separate plugin.

Site visibility – Coming soon general settings
Coming soon mode – only for store pages and site access only with private link

WooCommerce introduced option to set store “Coming Soon” mode so no need to have additional “manintenance mode” or “coming soon” plugins. You can switch that option from WooCommerce Settings. From version 9.3.1 there is also small icon in wp-admin upper left corner showing whether site is live or in coming soon.

New shortcode in WooCommerce Simple Auctions for any WordPress visual builder

We listened to our clients and introduced this handy feature. From WooCommerce Simple Auctions version 3.0 we have introduced special shortcode which display template parts for single auction page.

Shortcode example is below:

[wsa_templates template="countdown"]

This is useful for any visual builder like Avada Builder, WP Bakery Visual Composer, Beaver Builder, Divi Builder, Oxygen Builder, Themify Builder, SeedProd, Gutenberg, etc. You can do usual styling using your visual builder and just place shortcode with part you need (bid input, countdown timer, auction details, etc).

Available shortcode attributes (template parts) are:

add-to-cart
countdown
pay
bid-form
condition
dates
max-bid
reserve
auction-sealed
ajax-conteiner-start
ajax-conteiner-end

Keep on your mind that most builders require WooCommerce addon / integration in order to build WooCommerce pages like shop or single product page. As always we recommend you to check documentation for visual builder of your choice and see how it works and integrates with WooCommerce.

We have also FAQ entry covering this shortcode, see FAQ item no 68.

Bid Input Form Fixes for Some Themes

We have noticed that some themes are changing default quantity input field and controls from default WooCommerce one. That can cause misaligment of those fields and fixes are needed for such cases. Here are ready made fixes in form of code snippets or copy paste CSS for those who experienced described problems:

https://pastebin.com/fyQWyBJT  – fix for Shoptimizer theme
https://pastebin.com/fZFgWacP – fix for Enfold theme
https://pastebin.com/xhsegr4q  – fix for Woodmart theme
https://pastebin.com/3pudwH3e – fix for Avada theme
https://pastebin.com/M6fFue3E – fix for Salient theme
https://pastebin.com/X2c41izd – fix for XStore theme

CSS code should be copy pasted in Appereance > Customize > Custom CSS.

Code snippets and how to use them
https://wpgenie.org/tutorials-category/code-snippets-and-template-customizations-using-child-theme
(you will need account on wpgenie.org for this tutorial). You can also always contact us via support to help you with this issue.

New shortcodes in WooCommerce Lottery Pick Number Mod addon for WooComerce Lottery

There are two new shortcodes available for displaying instant wins and instant winners in WooCommerce Lottery Pick Number. We have implemented after some inquires from users of WooCommerce Lottery and Pick Number Mod addon. Shortcodes are available if you have active Pick Number Mod addon (version 2.4.7 and higher).

Shortcode that displays all instant wins with pagination and ordering:

[lottery_all_instant_wins paginate="true" limit="5" orderby="title"]

Shortcode that displays all instant winners with pagination:

[lottery_all_instant_winners limit="5"]

Lottery Pick Number and how to avoid on hold orders and duplicate numbers

In pick number it is possible to have two users selecting same number unless things are properly set up. How that could happen? For example one user selects number and does not pay for order right away but later on whole order is still created and available for payment / checkou. In meantime other user purchased that number in other client’s order. If 1st user tries to make payment order will go on hold due to duplicate ticket. This is normal behaviour of plugin.

How can site owner prevent this situtation?

  1. Lottery Pick Number comes with ticket reservation setting, it is located in Woo Settings > Lottery
  2. sensible value for reservation is 5 minutes, this means tickets will be unable for selection to others for 5 mins after user adds it to cart
  3. now we need to define time in which order will be cancelled if not paid, this is done via setting called “Hold Stock”, in Woo Settings > Products > Inventory tab, you need to set hold stock to 1 minute less than reservation time, so set it to 4 mins

This way we allowed each user 4 minutes to complete payment and finalize order, 1 minute later ticket will be freed if order was not completed. Settings explained here apply both to randomly assigned number and manual ticket number picking.

If you have some questions please open ticket here.

WooCommerce Simple Auctions v3.0 bidder verification and auto charge for won auctions

We have released new update for WooCommerce Simple Auctions v3.0 with two new features you asked for: allow bids if user has stored credit card and auto charge for won auctions if user has stored credit card. These new features work with WooCommerce Stripe Payment gateway.

First one allows users which have valid payment option saved (credit card) to place bids. This way you can verify user’s payment method.

Second feature allows to automatically charge saved card in case user has won auction. Order is automatically created and saved credit card is charged.

Video explainer for new features – bidder verification and auto charge for won auctions
New settings in WooCommerce Settings > Auctions tab.
WooCommerce Stripe Payment Gateway setting that needs to be enabled for these new features.
Screenshot of user’s My Account page > Payment methods with saved credit card. Credit cards are saved on Stripe not on your website so no worries about PCI compliance.

New version is published on CodeCanyon. If you have questions feel free to open support ticket.

WooCommerce 8.5.0 triggering mod_security rule and causing 403 error

Recently we have came accross issue with WooCommerce versions 8.5.0 and higher which has enabled feature “Order Attribution (Order Attribution Enable this feature to track and credit channels and campaigns that contribute to orders on your site)”.

Issue is that this feature triggers ModSecurity Comodo rule ID 218500 (SQLmap attack detected). Triggering that rule prevents access to site for all users and could potentially ban user’s IP via firewall.

You might want to disable this option or skip the rule (can be done usually in your control panel or you need to contact hosting support).