5reyreyr5ey5rey5re5rey5reyr

@robertocorreale Thank you very much for this Roberto, this is a great help!

Hopefully it’ll me merged for the next version bump, as this isn’t a cosmetic issue but a show-stopper in terms of functionality. Very much appreciate your quick patching of this issue.

In answer to the question about contributing code, the plugin’s Github repo is here:

https://github.com/wildbit/postmark-wordpress

I’m experience exactly the same issue. What was your work around, please?

That’s great, thanks, I’ll add this to my ‘toolkit’ for future Woo builds. Absolutely no need to apologise – you’re making this plugin freely available as-is and are under no obligation to update at all, so very grateful for you efforts. If and when I install on future builds, expect a donation ??

+1, appears broken on WC 2.6.2, WP 4.5.3, plugin 1.2.5. No checkboxes are visible.

Thank you to plugin author for your efforts. Looking forward to if/when a fix is forthcoming.

I’m experiencing the same issue.

Town/City (billing_city) and Postcode (billing_postcode) fields are still showing, despite being set as non-required. Other fields are unaffected.

Screeshot of settings page here:

https://www.dumpt.com/img/viewer.php?file=yexmdmuydpzz5dspgtx9.png

+1 for jamiechong’s comment. The version the plugin supports could be checked on installation to prevent breakage.

Not only would it be advantageous to allow plugin authors to select their own minimum supported PHP version, but this would also provide subtle momentum to nudge web hosts into upgrading their servers to support a half-way modern version, as more and more of the best and newest plugins start to require a higher minimum version.

That would still allow WP to support the earlier versions in terms of the core platform, yet allow the plugin authors to drive the momentum to upgrade – which is surely what we all want in the end. It benefits nobody that so many persist in running old versions of PHP on their servers, but there is little impetus for the average WP admin to upgrade if all the plugins in the WP directory are restricted to older versions.

Owing to its strong “market share”, WordPress is in a strong position to play a significant role in generating upgrade momentum in general; if website owners start bothering their hosting companies with calls to offer higher PHP versions and/or selecting their host based on version support because they want the ‘latest plugins’, then that’s all to the good, whilst those who’re happy with what they’ve got would still be at liberty to go merrily on with running WordPress on 5.4 whilst it remains supported by core.

Hello Nick

I uninstalled / reinstalled first, and verified that the issue was replicated. After applying the above fix, everything works like a charm. Perfect.

No worries, thanks for the plugin!

I look forward to the update. Feel free to get in touch if I can be of any further assistance as regards testing a fix or whatnot.

Marking this bug as resolved – soon-to-be released version update eliminates this issue. Thanks Ivan, great work.

Thanks Ivan. The site is under development and so not publicly accessible; I will send you the dev URL and access credentials via email so you can check it out.

Status: Fixed.

Bug Status: Closed.

Hello, great spot, thanks for that, much appreciated!

I’ll update and push the fix out shortly.

On my systems the bug didn’t manifest as an error, but just a PHP warning in the logs, which is due to WordPress taking the decision to require at least one additional parameter on the prepare statement, to mitigate against erroneous code when evaluating user submitted data.

There’s no security issue here as the table name variable is hard-coded, however I should have added the empty string to prevent the warning.

Thanks again for taking the time to point this out!

I’ve just checked your website; it appears you’re using a non-standard comment form; I note the class of your form element is “f1-comment-form” and not the standard “comment-form” class.

That could be because the theme you’re using is providing a non-standard comments form/system, or because you’re using a comments form plugin.

This plugin is only tested against the standard WordPress comments form.

If the plugin words for you in other respects, then you could remove the “website” field by modifying your comments form template – either in your plugin, or Theme.

Another option would be to simply hide the field using CSS, however this may not prohibit automated postings (bots), depending upon your overall security setup.