advantagen

I would update the rating, but this forum is telling me that I don’t have permission to ‘edit that topic’.

Anyway, thank you for clarifying, though wouldn’t it make sense to simply remove the deprecated functionality from your plugin so that other people don’t think the same thing?

I’m sorry – you’re right, and I realized that after I submitted this, but was unable to change or remove it because it was being moderated.

What made me think that it was MapPress was because the ‘noindex’ tax was immediate after the comment place there by MapPress.

And as it turns out, it was because I integrated a new theme on a staging site where I told bots not to index it. So then when I copied it over to the live site, that setting went with it.

Anyway, thank you for responding in this free support forum.

I’m sorry, this is a null issue. That is, after the email was never received, I installed and configured that SMTP plugin, and then I reloaded the page with the URL parameter. Apparently that wasn’t good enough though, and once I did a whole new form submission, it went right through. So I’m good! Sorry about that!

…but hey, ya gotta love the ones that solve themselves, right?

P.S. It seems that the title of this issue “Uncaught TypeError: Cannot read properties of undefined” is irrelevant to the actual issue at hand (since it’s present on the page regardless of the URL parameter).

That’s really helpful info, Andy – thank you! Might wanna add that in the FAQ or description for the plugin.

Can you please provide a link? If I test using the link above, it gives me a 38 for mobile.

Never mind. I just created the file and put the following dummy content in it:

{"version":1,"sources":[],"names":[],"mappings":"","file":"style.css","sourceRoot":""}

Thank you kindly for your response.

Can you please let us know what steps are being taken to ensure this doesn’t happen again?

Do I need to audit your code every time you issue an update?

Thank you for the offer, but I’d rather not put the time into it, especially because I found an option in the NFS control panel that’ll take care of this.

For anyone else that might be coming across this who are also NFS customers, just…

1) Go to the Sites tab and click your site’s short name
2) In the ‘Config Information’ box (scroll down a bit), click Canoncial URL
3) Type: Hard; Canonical HTTPS: On
4) Click Save

For anybody reading this with the same issue, I believe the understanding we came to on this was that, while the plugin does work with checkboxes in general, it does not however work with ‘repeater fields’ – or in other words, one field that has multiple checkboxes as options.

You might be able to arrange your custom fields so that each option is a new field though.

Hope this helps!

No kidding? I didn’t know that. That’s kinda stupid. Thanks for explaining though.

For the future reference of anyone stumbling across this thread in the future, I’ll put the resolution here.

That way, if anybody complains, it’s on me and not you guys.

Ok, done…though I don’t see what the difference is considering you’ve already responded here.

I should also clarify that the notification only echoes the first checked box.

(If there’s two boxes, the first is un-checked, and the second checked, it’ll echo the value from the second checkbox.)

But if both boxes are checked, it only shows the value from the first box.

Hopefully that makes sense.

Update: By using [custom_field field="app_features"], this will echo only the value of the first checkbox in that custom field.

That’s a step in the right direction anyway, but on top of the fact that it’s not showing values from the other checkboxes associated with that custom field, it’s still not sending a notification when the checkbox values change. I only get a notification if I set one on the whole listing changing, which is overly broad but better than nothing.

So I’m really hoping this plugin works with checkboxes and I’m just not configuring it right.

Actually, the free version you mentioned isn’t the same theme at all, and while I appreciate the effort you’ve put into troubleshooting this, it’s enough for me to know that it’s a conflict between your plugin and my theme. And since my theme is essential to my site’s functionality, it’s easier for me to simply choose another plugin. Perhaps this thread can help someone else that’s runs into the issue in the future though.