Hacker News new | ask | show | jobs
by 8ig8 5167 days ago
Would there be much harm in posting the fix for others? If not, could you?
2 comments

Sorry, I didn't think to post it because it's not a generally useful patch. It eliminates rather than fixes the functionality.

Here's to hoping Woothemes gets this sorted out. As it stands, automatic updating to 5.3.11 is still broken, and instead of stating this directly, it claims that your currently installed (out of date) version is current.

That's a cute side effect of woo_get_fw_version returning the currently installed version # instead of throwing an error if http://www.woothemes.com/updates/functions-changelog.txt isn't available for download (which it isn't, at the moment.)

    --- ./wp-content/themes/inspire/functions/js/shortcode-generator/preview-shortcode-external.php.orig
    +++ ./wp-content/themes/inspire/functions/js/shortcode-generator/preview-shortcode-external.php	
    @@ -58,6 +58,7 @@
    <?php
 
    $shortcode = isset($_REQUEST['shortcode']) ? $_REQUEST['shortcode'] : '';
    +$shortcode = '';
 
    // WordPress automatically adds slashes to quotes
    // http://stackoverflow.com/questions/3812128/although-magic-quotes-are-turned-off-still-escaped-strings
I wrote a simple Nagios check that can be used to watch for WooFramework updates, and published it here:

https://github.com/kway/check_woo

At this point in time it returns 'UNKNOWN' because the WooThemes changelog file isn't fetchable, but it should return CRIT/WARN/OK once they have their shop back in order.

Sharing it here in case it might help somebody notice critical fixes more expediently in the future.