Title: surml's Replies | WordPress.org --- # surml [ ](https://wordpress.org/support/users/surml/) * [Profile](https://wordpress.org/support/users/surml/) * [Topics Started](https://wordpress.org/support/users/surml/topics/) * [Replies Created](https://wordpress.org/support/users/surml/replies/) * [Reviews Written](https://wordpress.org/support/users/surml/reviews/) * [Topics Replied To](https://wordpress.org/support/users/surml/replied-to/) * [Engagements](https://wordpress.org/support/users/surml/engagements/) * [Favorites](https://wordpress.org/support/users/surml/favorites/) Search replies: ## Forum Replies Created Viewing 7 replies - 1 through 7 (of 7 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets] Little Bug with Device Visibility](https://wordpress.org/support/topic/little-bug-with-device-visibility/) * Thread Starter [surml](https://wordpress.org/support/users/surml/) * (@surml) * [5 years, 3 months ago](https://wordpress.org/support/topic/little-bug-with-device-visibility/#post-14126552) * It’s a site with quite a lot plugins, so I tested on a clean install. The only active plugins: – Siteorigin Page Builder – Siteorigin Widgets Bundle – Widget Options …same behaviour with both themes Siteorigin Vantage and Twenty-Twenty One. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets] Little Bug with Device Visibility](https://wordpress.org/support/topic/little-bug-with-device-visibility/) * Thread Starter [surml](https://wordpress.org/support/users/surml/) * (@surml) * [5 years, 3 months ago](https://wordpress.org/support/topic/little-bug-with-device-visibility/#post-14120934) * Thanks for the offer, but the URL in question is not publicly accessible. Anyway, it doesn’t pose a problem, my post was just for your information as I suspected this could be general behaviour of the plugin not specific to my instance. * I forgot to mention: it happens with page builder widgets, I did not test with standard wordpress widgets. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[WP DSGVO Tools (GDPR)] V3 Update is a mess!](https://wordpress.org/support/topic/v3-update-is-a-mess/) * Thread Starter [surml](https://wordpress.org/support/users/surml/) * (@surml) * [6 years, 4 months ago](https://wordpress.org/support/topic/v3-update-is-a-mess/#post-12427657) * I – of course – tested the upgrade. That does not change the fact I had to completely rework GDPR-compliance of most affected websites because I could not leave them with an outdated, unsupported version of a plugin, could I? * The poor rating was not for having that work to do – I get paid for that. It was for bad programming practise of publishing an upgrade that breaks current installations without prior warning. And it is for silently changing the policy on free/non-free components, stripping functions off running installations and making them premium. * Both factors let you seem unreliable and unpredictable to a certain degree, which people should be able to consider when evaluating the use of this software by reading reviews. * Oh, and before you get into your “come on, its a few bucks on functions only commercial users need”: I am not upset about having to pay. I am upset about HOW you made people pay. * So it’s funny you should invite me to a beer, because my complaint, as an open source guy who contributes a lot, is about the “free as in free speech” part, not the “free beer” part! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[SVG Support] News: Illegal string offset warning for Height and Width](https://wordpress.org/support/topic/news-illegal-string-offset-warning-for-height-and-width/) * Thread Starter [surml](https://wordpress.org/support/users/surml/) * (@surml) * [7 years, 7 months ago](https://wordpress.org/support/topic/news-illegal-string-offset-warning-for-height-and-width/#post-10870571) * Jumping in just for the quick-fix: Yes, attachment-modal.php is a plugin’s file( inside the “functions”-folder) and yes, it will be overwritten in case of an update. * [@benbodhi](https://wordpress.org/support/users/benbodhi/) could you possibly release a minor upgrade with a fixed version? I had to manually edit multiple client installations already and this would really help to stay on the safe side. * Regards Surml * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[SVG Support] News: Illegal string offset warning for Height and Width](https://wordpress.org/support/topic/news-illegal-string-offset-warning-for-height-and-width/) * Thread Starter [surml](https://wordpress.org/support/users/surml/) * (@surml) * [7 years, 8 months ago](https://wordpress.org/support/topic/news-illegal-string-offset-warning-for-height-and-width/#post-10717453) * You’re very welcome 🙂 glad when I can help! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[VS Contact Form] Very Simple Contact Form with settingspage](https://wordpress.org/support/topic/very-simple-contact-form-with-settingspage/) * [surml](https://wordpress.org/support/users/surml/) * (@surml) * [8 years, 2 months ago](https://wordpress.org/support/topic/very-simple-contact-form-with-settingspage/#post-10106804) * Hi Guido, * thanks for your effort! But why would you remove any features your plugin already has? As far as I see it, it would be very simple to expand vscf-form.php and vscf-widget-form.php by an array filled with all options from the admin page and then placing these settings as defaults into shortcode_atts() instead of the hardcoded ones you have now (while these could be the new hardcoded defaults of the admin page fields). That way none of the functionality would be lost and all available settings could be set both ways. Would be fine for users like me who need shortcode_atts and would be easier for non-power users, because for one simple form everything could be set in the admin page without touching shortcode_atts at all. * Cheers, Michael * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[VS Contact Form] Very Simple Contact Form with settingspage](https://wordpress.org/support/topic/very-simple-contact-form-with-settingspage/) * [surml](https://wordpress.org/support/users/surml/) * (@surml) * [8 years, 2 months ago](https://wordpress.org/support/topic/very-simple-contact-form-with-settingspage/#post-10104098) * Settings Page would be fine for setting defaults. But **please** do not remove shortcode attribute abilities! ..so that one can make forms that differ from defaults. Would be a dealbreaker for me, because I use multiple forms with different settings throughout the Site. Viewing 7 replies - 1 through 7 (of 7 total)