Title: Sammy Nordström's Replies | WordPress.org --- # Sammy Nordström [ ](https://wordpress.org/support/users/samface/) * [Profile](https://wordpress.org/support/users/samface/) * [Topics Started](https://wordpress.org/support/users/samface/topics/) * [Replies Created](https://wordpress.org/support/users/samface/replies/) * [Reviews Written](https://wordpress.org/support/users/samface/reviews/) * [Topics Replied To](https://wordpress.org/support/users/samface/replied-to/) * [Engagements](https://wordpress.org/support/users/samface/engagements/) * [Favorites](https://wordpress.org/support/users/samface/favorites/) Search replies: ## Forum Replies Created Viewing 14 replies - 1 through 14 (of 14 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WC Variations Radio Buttons] Display Variation Details](https://wordpress.org/support/topic/display-variation-details/) * [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [10 years, 11 months ago](https://wordpress.org/support/topic/display-variation-details/#post-6719167) * Maybe you should look into something like this: * [http://isabelcastillo.com/free-plugins/woocommerce-variation-description-radio-buttons](http://isabelcastillo.com/free-plugins/woocommerce-variation-description-radio-buttons) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Angry Creative Inspector] Please develop with DEBUG on](https://wordpress.org/support/topic/please-develop-with-debug-on/) * Plugin Author [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 2 months ago](https://wordpress.org/support/topic/please-develop-with-debug-on/#post-5083208) * As an update and final comment on this issue; the latest release (v0.5.1) fixes some php warnings/notices, although I suspect some may still show the first time you install and not all variables are defined yet. * However, it should be noted that this plugin has yet to be released as version 1.0, ie it’s not yet a full stable release. Consider it more like a public beta and that issues like this is to be expected. This because the code base is still being refactored from release to release, making it futile to write error checks for every variable that is almost certain to be rendered obselete in the next rewrite anyways. Once we’re closing up on a real stable release though, of course it should not be ignored nor left uncared for. With that in mind, I thank you once again for your feedback and mark this topic as resolved. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Angry Creative Inspector] wp-way content dir](https://wordpress.org/support/topic/wp-way-content-dir/) * Plugin Author [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 2 months ago](https://wordpress.org/support/topic/wp-way-content-dir/#post-5149256) * Not sure what you mean by hardcoding but the log file path you are referring to is just the default setting that you may set to any path you like under the General Settings tab. Just make sure it’s a path that the webserver has write access to. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Angry Creative Inspector] Please develop with DEBUG on](https://wordpress.org/support/topic/please-develop-with-debug-on/) * Plugin Author [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 3 months ago](https://wordpress.org/support/topic/please-develop-with-debug-on/#post-5083018) * We do have the tools and processes for developing with CI, although Travis really doesn’t do the trick for us since it only supports Github and we strongly prefer Bitbucket. We use Jenkins in combination with Sauce on Demand by Sauce Labs. It’s really neat stuff if you’re interested in that kind of thing. However, errors like the above are still prone to go undetected when you haven’t foreseen all possible scenarios and/or just haven’t got the resources to anticipate them. As with so many other projects like these, it’s matter of time and money resources rather than tools or know how. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Angry Creative Inspector] Please develop with DEBUG on](https://wordpress.org/support/topic/please-develop-with-debug-on/) * Plugin Author [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 3 months ago](https://wordpress.org/support/topic/please-develop-with-debug-on/#post-5083000) * Hi! * Thank you for notifying us. We do develop with debugging on, it’s just not a guarantee for detecting all issues. In this case, it’s probably a matter of variables that is loaded from the database that was set in our development environment but not when doing a fresh install. We should of course have tested for this as well, but as an open source project without paying customers to finance the development, we apply the release early release often philosophy. * So again, thank you for letting us know and expect it to be fixed in our next update. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simple Fields] 3.9 HTML editor load script issue](https://wordpress.org/support/topic/39-html-editor-load-script-issue/) * Plugin Contributor [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 3 months ago](https://wordpress.org/support/topic/39-html-editor-load-script-issue/#post-4825403) * We’re happy to report that the issue we had has now been resolved and that it was not caused by the Simple Fields plugin at all. In other words, disregard our bugreport. 🙂 * Sorry if we sent you on a wild goose chase. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simple Fields] 3.9 HTML editor load script issue](https://wordpress.org/support/topic/39-html-editor-load-script-issue/) * Plugin Contributor [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 3 months ago](https://wordpress.org/support/topic/39-html-editor-load-script-issue/#post-4825399) * It’s an issue with TinyMCE, with WP 3.9 comes TinyMCE 4. The visual editor needs to be instantiated a bit differently. I fixed it in another project like this: * ``` // The old way of adding TinyMCE to a textarea: // tinyMCE.execCommand('mceAddControl', false, id); // The new way: ed = new tinyMCE.Editor(id, tinyMCE.settings, tinyMCE.EditorManager); ed.render(); ``` * Not sure of how applicable it is to Simple Fields (the sources have been refactored several times over since I worked on it), but hopefully it is of some help. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[BP Sticky Groups] Ignore sticky posts](https://wordpress.org/support/topic/ignore-sticky-posts/) * Thread Starter [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 4 months ago](https://wordpress.org/support/topic/ignore-sticky-posts/#post-4974772) * That didn’t work entirely as expected. As it turns out, you need to do it a bit differently to ignore sticky posts in Ajax requests as well. I ended up doing it as a plugin in order to hook into the right actions and filters, like this: * ``` groups->extend ) ) $bp->groups->extend = new stdClass(); if( empty( $bp->groups->extend->bp_sticky_groups ) ) $bp->groups->extend->bp_sticky_groups = BP_Sticky_Groups::instance(); function allow_sticky_groups() { if (!is_admin() || (defined('DOING_AJAX') && DOING_AJAX)) { remove_action( 'bp_groups_get_paged_groups_sql', 'disallow_sticky_groups', 1, 1 ); add_filter( 'bp_groups_get_paged_groups_sql', array( BP_Sticky_Groups::instance(), 'alter_bp_groups_query' ), 10, 2 ); } } function disallow_sticky_groups( $sql = "" ) { if (!is_admin() || (defined('DOING_AJAX') && DOING_AJAX)) { remove_filter( 'bp_groups_get_paged_groups_sql', array( BP_Sticky_Groups::instance(), 'alter_bp_groups_query' ), 10 ); add_action( 'bp_groups_get_paged_groups_sql', 'disallow_sticky_groups', 1, 1 ); } return $sql; } add_action( 'bp_before_groups_loop', 'allow_sticky_groups', 1 ); add_action( 'bp_after_groups_loop', 'disallow_sticky_groups', 1 ); add_action( 'bp_groups_get_paged_groups_sql', 'disallow_sticky_groups', 1, 1 ); } } add_action( 'bp_include', 'bp_ignore_sticky_groups' ); ``` * Preferrably the Sticky Posts plugin would enable the site admin to choose when and where the sticky posts should be applied, but the above solution does the trick for me right now. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast Duplicate Post] Feature request: Retain original post author](https://wordpress.org/support/topic/feature-request-retain-original-post-author/) * Thread Starter [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 7 months ago](https://wordpress.org/support/topic/feature-request-retain-original-post-author/#post-4659915) * Oh sorry, forgot about a line of code that needs to be at two due places within the function ‘duplicate_post_plugin_upgrade()’ of the file duplicate-post-admin. php: * ``` add_option('duplicate_post_copyauthor','0'); ``` * And THAT should be it. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)] Forgotten UA-code after update and unable to re-enter](https://wordpress.org/support/topic/forgotten-ua-code-after-update-and-unable-to-re-enter/) * Thread Starter [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 7 months ago](https://wordpress.org/support/topic/forgotten-ua-code-after-update-and-unable-to-re-enter/#post-4658789) * Btw, I work for a company that supports and maintains a multitude of WordPress- sites and this problem occurs in the same manner on all WordPress-installations having this plugin. Due to this we have to write down all UA-codes before updating and then switch over to Firefox after completing the updates for manually re- entering the UA-codes. I can’t imagine this how it is supposed to work. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)] Authentication issue](https://wordpress.org/support/topic/authentication-issue/) * [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 7 months ago](https://wordpress.org/support/topic/authentication-issue/#post-4620615) * Tried resetting all settings too, btw. No improvement. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)] Authentication issue](https://wordpress.org/support/topic/authentication-issue/) * [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 7 months ago](https://wordpress.org/support/topic/authentication-issue/#post-4620614) * I’m having the same issue. Furthermore it refuses to let me enter a UA-code manually. Ticking the box does absolutely nothing. It keeps wanting me to authenticate with a google-account. What am I doing wrong? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[thumbGen] Thumbgen generated images are black](https://wordpress.org/support/topic/thumbgen-generated-images-are-black/) * Thread Starter [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [12 years, 9 months ago](https://wordpress.org/support/topic/thumbgen-generated-images-are-black/#post-4429071) * btw: we have a dedicated server with gdlib 2.1, debian 7, nginx, php5-fpm. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simple Fields] There is an update available for Simple Fields!](https://wordpress.org/support/topic/there-is-an-update-available-for-simple-fields/) * Plugin Contributor [Sammy Nordström](https://wordpress.org/support/users/samface/) * (@samface) * [14 years, 7 months ago](https://wordpress.org/support/topic/there-is-an-update-available-for-simple-fields/#post-2559601) * Hi sguk! * Like plux wrote, thanks for the feedback! We knew that there were more bugs that needs fixing when releasing this update but we felt the bug fixes in this update needed to be released now so that the plugin would atleast be usable with WP 3.3, even if with a few glitches. * Now, keep reporting bugs and watch out for more updates coming soon! 🙂 Viewing 14 replies - 1 through 14 (of 14 total)