Title: bubdev's Replies | WordPress.org --- # bubdev [ ](https://wordpress.org/support/users/bubdev/) * [Profile](https://wordpress.org/support/users/bubdev/) * [Topics Started](https://wordpress.org/support/users/bubdev/topics/) * [Replies Created](https://wordpress.org/support/users/bubdev/replies/) * [Reviews Written](https://wordpress.org/support/users/bubdev/reviews/) * [Topics Replied To](https://wordpress.org/support/users/bubdev/replied-to/) * [Engagements](https://wordpress.org/support/users/bubdev/engagements/) * [Favorites](https://wordpress.org/support/users/bubdev/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 25 total) 1 [2](https://wordpress.org/support/users/bubdev/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/bubdev/replies/page/2/?output_format=md) * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Side Cart Woocommerce | Woocommerce Cart] License Promise Broken](https://wordpress.org/support/topic/license-promise-broken/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [1 year ago](https://wordpress.org/support/topic/license-promise-broken/#post-18448701) * Thank you for confirming you’re aware of your misleading past offering. And thank you for casually mentioning that you received a similar email inquiry from someone else just yesterday. Anyone reading your responses can draw their own conclusions about this situation. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Side Cart Woocommerce | Woocommerce Cart] License Promise Broken](https://wordpress.org/support/topic/license-promise-broken/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [1 year ago](https://wordpress.org/support/topic/license-promise-broken/#post-18448681) * I need to correct one thing – I never sent any emails. Both of my support requests were submitted through your official contact page form several weeks ago. * If your argument is that this was a misunderstanding, you certainly went to great lengths to create this misunderstanding. The Wayback Machine proves that in May 2022, there was no mention of an annual subscription anywhere. In fact, your Plugin FAQ clearly stated as the second item: * “Do I need to renew a license everytime? No, its for lifetime” * Would you like me to send you a screenshot of this? * If your argument is that you didn’t literally promise “lifetime updates”, what else could customers reasonably conclude from this promise? It’s extremely dishonest to pretend you don’t see how misleading this was and to treat your customers as fools. You’re not the only ones offering lifetime deals online, and I’ve never experienced such unprofessional behavior in numerous similar purchases. - This reply was modified 1 year ago by [bubdev](https://wordpress.org/support/users/bubdev/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Pods - Custom Content Types and Fields] unable to add to pods fields after latest WP update](https://wordpress.org/support/topic/unable-to-add-to-pods-fields-after-latest-wp-update/) * [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [1 year, 4 months ago](https://wordpress.org/support/topic/unable-to-add-to-pods-fields-after-latest-wp-update/#post-18222096) * In case others are still looking for a solution and haven’t had any luck with clearing the cache: what solved the problem for me was going to the Pods settings and setting “Override WP Metadata values” to “Disable overriding WP Metadata values.” * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] Quotation marks modified](https://wordpress.org/support/topic/quotation-marks-modified/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [3 years ago](https://wordpress.org/support/topic/quotation-marks-modified/#post-16734579) * Just to clarify: ‘wptexturize’ can still be disabled with ‘remove_filter’. No need for ‘str_replace’, unlike what I stated above. * Thus, as a workaround, one can ‘str_replace’ the curly English quote marks with German quote marks. Preferably after checking if ‘Mollie’ is active, otherwise it messes up the closing quote marks. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] Quotation marks modified](https://wordpress.org/support/topic/quotation-marks-modified/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [3 years ago](https://wordpress.org/support/topic/quotation-marks-modified/#post-16734164) * Thank you for the info, Niklas! * Out of the more than 100 plugins I’m currently using on various websites, “Mollie” is actually the only one that causes this error. In the past, I had the same problem with the following plugins: “My Private Site,” “WP Statistics,” “Really Simple SSL.” * When the frontend is set to German and “Mollie” is activated, English curly quote marks appear, which make no sense in German. To at least get straight English quotation marks (the lesser evil), it’s not enough to deactivate “wptexturize,” but each variant must be replaced using “str_replace”. * I understand that the problem is very difficult to debug, but it’s still unfortunate because I wanted to recommend “Mollie” as the standard payment processor to my e-commerce clients. Now, I have to let them choose between proper quotation marks and “Mollie”. In certain instances, particularly for book publishers, “Mollie” becomes an impractical choice, rendering it essentially unsuitable. * Thanks again for the explanations and for keeping us informed! * Kind regards, Stefan - This reply was modified 3 years ago by [bubdev](https://wordpress.org/support/users/bubdev/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] Quotation marks modified](https://wordpress.org/support/topic/quotation-marks-modified/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [3 years ago](https://wordpress.org/support/topic/quotation-marks-modified/#post-16732053) * Do you have any new information regarding this matter? Currently, it appears to be the only plugin I know of that is causing issues with German quote marks. * Kind regards, Stefan - This reply was modified 3 years ago by [bubdev](https://wordpress.org/support/users/bubdev/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] Quotation marks modified](https://wordpress.org/support/topic/quotation-marks-modified/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [3 years, 1 month ago](https://wordpress.org/support/topic/quotation-marks-modified/#post-16646615) * Thanks for looking into it! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Statistics – Simple, privacy-friendly Google Analytics alternative] Plugin breaks ‘wptexturize’ functionality](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [7 years, 4 months ago](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/#post-11111091) * There’s no related error showing with WP_DEBUG enabled. In the meantime, I had to finish up the project and hand it over to the client. As a solution I decided on using str_replace() instead of relying on wptexturize() to achieve localized quote marks, which works reasonably well. * Thanks a lot for your time and help! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Statistics – Simple, privacy-friendly Google Analytics alternative] Plugin breaks ‘wptexturize’ functionality](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [7 years, 4 months ago](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/#post-11071078) * No, on this test site there’s nothing custom at all. Fresh WP install, no other plugins, just the default theme, typical web hosting (SiteGround). Now also tried the new default theme, Twenty Nineteen. The problem remains. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Statistics – Simple, privacy-friendly Google Analytics alternative] Plugin breaks ‘wptexturize’ functionality](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [7 years, 4 months ago](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/#post-11059255) * I just tested it on a site with no other plugins installed than WP Statistics and running the Twenty Seventeen theme. The problem persists. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Statistics – Simple, privacy-friendly Google Analytics alternative] Plugin breaks ‘wptexturize’ functionality](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [7 years, 4 months ago](https://wordpress.org/support/topic/plugin-breaks-wptexturize-function/#post-11058420) * Thanks, but the option was already disabled. It must be something else. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin Columns] Issue with Post Type Switcher Plugin](https://wordpress.org/support/topic/issue-with-post-type-switcher-plugin/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [7 years, 10 months ago](https://wordpress.org/support/topic/issue-with-post-type-switcher-plugin/#post-10483694) * This makes a lot of sense, thank you! * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Cactus Masonry Classic] Easy to tweak](https://wordpress.org/support/topic/easy-to-tweak/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [10 years, 1 month ago](https://wordpress.org/support/topic/easy-to-tweak/#post-8077860) * Hi bortpress, * thanks for your reply! It probably got published right after I had edited my review, so you didn’t notice I had already withdrawn my feature request. * On the one hand I was quite sure the missing sorting option would come in a future update, and also: Yes, using ‘menu_order’ worked fine – at least in the file itself. I don’t think I even tried it with a shortcode. Since I had already tweaked other stuff too, it didn’t matter anymore. * I’m looking forward to version 2 of the plugin. Thanks again! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Posts in Sidebar] Custom fields missing in dropdown list](https://wordpress.org/support/topic/custom-fields-missing-in-dropdown-list/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [10 years, 3 months ago](https://wordpress.org/support/topic/custom-fields-missing-in-dropdown-list/#post-6955389) * It did fix the issue. Thanks again for the outstanding support!! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Posts in Sidebar] Custom fields missing in dropdown list](https://wordpress.org/support/topic/custom-fields-missing-in-dropdown-list/) * Thread Starter [bubdev](https://wordpress.org/support/users/bubdev/) * (@bubdev) * [10 years, 3 months ago](https://wordpress.org/support/topic/custom-fields-missing-in-dropdown-list/#post-6955387) * Yes, only the last character seems to be affected. Viewing 15 replies - 1 through 15 (of 25 total) 1 [2](https://wordpress.org/support/users/bubdev/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/bubdev/replies/page/2/?output_format=md)