Lee – despite the frustration of having to navigate thru several different, verbose, external pages of documentation, your plug-in does what it promised. For that, I am sincerely thankful. I realise that many people wish only to consume and, intentionally or inadvertently, overlook the fact that you spent time and energy designing something .. then sharing it with the WP community, hoping to bait a few sales. I can’t speak for everyone .. but there’s actually no issue with that agenda. I think if you provided current and relevant screenshots, as well as streamlined the instructions and provided the community with step-instructions for leveraging the FREE version, you might attract more sales .. in comparison to leaving people dismayed from the onset.
I also have much success with the SkyVerge “Customizer” plugin, although it does not include “SKU” at present: https://www.ads-software.com/plugins/woocommerce-customizer/screenshots/
That being said, here’s what I did to make your plugin a success for my WooCommerce project:
(1) Downloaded WooCommerce (ZIP file) to my local development PC – https://www.ads-software.com/plugins/woocommerce/
(2) Unzipped the WooCommerce ZIP file to my desktop, using free tool from https://www.7-ZIP.ORG – there’s no need to purchase WinZip or other licensed tool. This produced a single, parent folder on my desktop with all of the WooCommerce assets inside.
(3) Used the intrinsic search “Find In Files” feature of the free tool NOTEPAD++ which can be found at https://www.notepad-plus-plus.org – This is a great tool and widely used by many developers, in place of the Windows Notepad. Moreover, it works faster and more accurate than the built-in Windows Search Index which is horrible at best.
(4) Searched the WooCommerce folder and sub-folders for the string “SKU” (without quotes) and then sifted thru the results until I found _e( 'SKU:','woocommerce');
, as per your instructions to look for the function _e
. Note the space after the opening parenthesis, as this initially resulted in NO match, when I wrongly searched for string _e('SKU
. Also, the string value I intended to replace includes a colon.
(5) Using your SAY WHAT plugin, I added an entry:
Original string: SKU:
Text Domain: woocommerce
(note this is from the 2nd argument of the _e function as shown above)
Text Context: I left this empty – did not require defining.
That was all it took. I hope this detailed feedback helps others leverage your plugin to their success.