Good unless you want to do advanced things

This plugin is great to get an auction up and running quickly. If you want to do anything advanced is where you can run into road blocks.

Here are some road blocks and issues I’ve ran into.

Stylesheets aren’t set up properly. They are “enqueued” but not registered. Same for scripts. This means each and every page includes these files. Your homepage will have these scripts, your contact page etc. This is terrible for web page performance in most instances since it loads assets not needed for the page.

In an ideal world only the pages which include the shortcode would also use those scripts.

The problem with how they are included is if you want to over write or use WordPress’ dequeue_style or script you have to then pull those out and include them in your own theme under a different name and then register and queue them.

This also causes you to have to almost fight how the auctions are styled with specificity.

The included css files also use !important throughout it. Making things a pain to over ride

Javascript (Jquery) is sprinkled inline throughout the page. Instead of having one script loaded in the footer you can go through each and every area that has a click event listener and beneath it will be an inline script tag and stylesheets are also included inside the body of the page.

There are old HTML tags used. For instance the tag <center> is used. This tag was deprecated and considered obsolete in HTML4 so almost 17 years ago now.

There are table attributes and table children elements used without any opening or closing table tags.

In the backend user dashboard and the main auction feeder page there are tons of inline styles on elements, div’s being used for spans, text inside div’s with out paragraph tags or heading tags. Labels for checkboxes not in label tags just placed inline next to the check box.

Modal / dialog boxes use javascript:void(0) – along with the rest of the inline javascript – violates a content security policy. So if you have this enabled your entire application / website will not function since click listeners are inline… ie: <a id="loginmodel" href="javascript:void(0)" class="login" data-toggle="modal" data-target="#login-modal">Login</a>

Content Security Policies will also break if you don’t allow unsafe inline because of the inline javascript.

Now if you’re just wanting to get going, not worried about page performance and don’t use a Content Security Policy then this hits all the right areas. The over all functions of this plugin do everything it says it will. Is easy to setup. I just wish it followed some more “modernish” best practices and allowed us the user to over ride styles and layout easier.