Paul Wong-Gibbs

I’ve just tested with a new form with radio buttons and check boxes, and can confirm that these show up correctly when a form is submitted.

As you suspected it looks like the pre-made form templates need to be updated.

Thanks for highlighting the field name box! I missed it!

As far as question 1 goes, I’m not quite seeing expected behaviour. Are you able to access this screen recording? There are many fields on the form I’m not seeing in the response.

https://share.getcloudapp.com/2NuXEWAR

I agree a default value for text fields is a weak argument by itself, but a default value for a Hidden text input field would let a site owner capture extra data that would be stored alongside the form responses.

For example, a site may have multiple contact forms which are identical, apart from a hidden field value that holds some name or ID.

I will try that later, thank you!

To be clear, not a default value, I meant not a field placeholder= attribute, but the initial value state of the field.

Thanks – for default values, if I set this in a Name or Message field (I haven’t tested the others), then it becomes the placeholder= value, not the element’s value=.

Thanks! Makes sense now.

Yep – you were right. I’m not exactly sure yet what the incompatibility is, but if it’s anything interesting, I’ll let you know!

I’m seeing this too.

Hello, troll.

There is no obligation to continue developing or supporting what was always a free WordPress plugin. I spent three or four years building it (I think), then moved onto other things. I enjoyed spending time on the plugin and engaging with the people who used it, and I’ll always look back at it fondly. I have no worked on the plugin for almost four years now, and no intention to do so in the future (at this point in time).

I have never called myself a “WordPress Lead Developer”; anyone who knows me knows that contributing directly to WordPress is something I have absolutely no interest in. I have been, however, a Lead Developer on the BuddyPress plugin for several years now, which is where I currently choose to spend most of my free time.

That’s what “no active dev support” means. ??

@giggi Users are only showing in BuddyPress’ Members directory when they’ve been active on the site, at least once. For this situation, it’ll mean they will show up the next time each user logs into your site.

I’ll add some info about BuddyPress.

@ositive If the BuddyPress translation you’ve loaded is 100% complete, it’ll include the translated emails. What you need to do is go to wp-admin > Tools > BuddyPress, and run the “email repair” tool. This will delete all the existing email posts (English), and re-add the emails, using the translation provided by the .mo file.

The loop_start/end name clashes has been fixed in https://buddypress.trac.www.ads-software.com/changeset/11083/ due for BuddyPress 2.7 this October.

Those other messages come from the podlove-podcasting-plugin-for-wordpress plugin calling some code too early. Other than representative of probably doing something wrong, it doesn’t cause problems most of the time, so you can disable the debugging again and ignore those.