• Wanted to rename “SKU” in WooCommerce to some other value.

    Found this plugin to be unfriendly and it solicited this fact by attempting to coerce me into purchasing the “Pro version”. Meh.

    Original text is defined in WooCommerce as: _e( 'SKU:','woocommerce'); Note the space after the opening parenthesis.

    I successfully swapped the text, using this plugin, once I correctly supplied the “Text Domain” (which, in this case, was “woocommerce” – the 2nd argument shown above) and the “Text Context” which did not require defining.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Lee Willis

    (@leewillis77)

    Hi;

    Firstly – thanks for taking the time to leave a review.

    I’m sorry you found it unfriendly – although I think from your review that you managed to do what you wanted – which is great.

    Finding strings to replace is normally straightforward if you’re a full time developer. That’s the main reason I released this as a free plugin – it can be really useful for people who are happy digging around in plugin code to find the information they need.

    I appreciate that if you’re not a full time coder – or don’t want to spend the time hunting through code then the free version probably isn’t as useful. However – that’s the main reason that I spent the extra time developing the String Discovery feature that sets the Pro version apart. That makes the plugin accessible to non-coders – or people who want / appreciate a quicker way of mapping strings.

    The user interface in the Pro version is pretty much identical to the free version – so if you have constructive comments on how that could be approved they’d be more than welcome.

    Thread Starter IRD-dev

    (@ird-dev)

    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.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Free version is not user-friendly but did work with WooCommerce’ is closed to new replies.