John Huebner
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] permanently dismiss warning@wpwalker, I agree, as a developer I want to see errors. My problem is the concern that these errors cause my clients because they don’t understand that I am aware of the issues and I’ve dealt with them, they just see the error and think I’m doing something wrong.
But as a developer I know that using mail() or wp_mail() (which is just a wrapper for mail()) has issues, the biggest one you mention is that emails disappear into the ether. There are many, many reasons for this, and just putting in an @site.com that matches your domain name will not cure every problem, so from my point of view checking for this is a waste of time because it only gives you a false sense of “now it will be okay and I’ll get all my form submissions.” This is why I install a plugin for and set up SMTP for sending emails from a dedicated email address. Once this is done it really doesn’t matter what email address is in the “from” box of CF7 forms, since it’s ignored.
I created this as part of 3 plugins to do something very similar. Combine this with my hidden field plugin. I think it can also be done using the dynamic text extension.
Add a hidden field that is populated dynamically, for example: “hidden-post-id” and dynamically populate this with the current post ID.
add another hidden field to the form with the name “dynamic-mail-to-filter”. This fields value needs to be the name of the filter to run, the “hook” that will be used in apply_filters($hook_name, $recipient, $args)
create a third hidden field named “dynamic-mail-to-fields”. The value of this field would be “hidden-post-id”. This will be passed to your filter as part of $args.
In your filter get the recipient value from the post and return it. In this case the first hidden field could be dynamically populated with the exact recipient rather than the post id, but I wouldn’t do that since it will make the email address visible to bots and I’d prefer the first method.
And if you do have it defined in your wp-config.php, the way I do because there are many other plugins that use this constant that I must put it there for debugging, which is the proper place for it, it causes an error that prevents AJAX requests from completing. This is not a constant that should be defined in a plugin file, EVER!
Forum: Plugins
In reply to: [Dynamic Select for Contact Form 7] Get parameters based on URLSorry, but this isn’t something that I’m going to be able to help you with. If this was something simple like getting a list of categories or a list of posts or something, I might be able to help you with, but where and how the someone gets and returns the values for this field is something that each person needs to work out. I don’t know much about the dynamic text extension plugin and I don’t use it very often, so I don’t know how it works or how you’d use it to fill the select values of this field.
Looking at the other question that you posted (I won’t answer there so that maybe someone else will help you) there isn’t any way to collect values from other input fields and supply them to the filter in this field, especially if you’re looking to get values entered into the form and not something that can be generated before the form is displayed. If the values are generated before the field is displayed then you would generate them the same way. There is not AJAX functionality in this plugin that can regenerate the selections after the fact. You might want to look at creating some JavaScript that will do this.
Forum: Plugins
In reply to: [Dynamic Select for Contact Form 7] Get parameters based on URLThe choices can be based on anything you want them to be based on. This plugin does not do any of the generation, that part is up to you. See the example filter in the file https://plugins.svn.wordpress.org/contact-form-7-dynamic-select-extension/trunk/cf7-dynamic-select-examples.php
Forum: Plugins
In reply to: [ACF Enhanced Message Field] installing in another pluginBecause I’m putting it in my plugin just in case the site does not already have it installed, but if the do already have it installed there will be a conflict. Elliot has also released a new version of the field type template that deals with this without needing to add any additional code.
I was assuming that I’d need and account to contact you directly. When I’m dealing with this plugin on a site I usually don’t have access to the client’s sharethis account, I’m simply adding the plugin and setting it up. As a rule, my company does not register any 3rd party accounts to us so that we do not tie a client to our services.
I will keep this in mind in the future and give it a try the next time.
I was just looking for the same thing, some type of filter or something. I have a multisite installation and some of the sites have 20 editors and several admins on them. There is only one or two people on each of these sites that needs to be notified and if all of them get these notifications I’m going to get a lot of emails complaining about it. I have no interest in creating to new user roles to replace the existing admin and editor roles so that those people get the notification, and the 3 network admins don’t need to get them either, the last thing I need is to get 30 emails every day telling me there’s a post revision when I’m not involved in the day to day management of the sites.
Forum: Plugins
In reply to: [ACF Enhanced Message Field] installing in another pluginBasically, I was trying to include this plugin as part of another plugin rather than have people install it separately. Elliot has made some changes to the custom field template that allows this. I was just asking if you could make the update when you have time. For now I’ve altered the version I’m including to load after plugins are loaded and only include the enhanced message field if it does not already exist. Not a huge hurry now since I have a solution that’s working.
Until the author corrects the problem, edit the field and comment out that line where the define statement is.
After 4 months, to be honest, I don’t even remember what site this is referring to. I maintain more sites than I can count. Either there was an update after I posted this issue or we removed the plugin, or maybe figured out how to correct. Either way it must have gotten resolved one way or another.
Forum: Hacks
In reply to: Custom Post Type below Options Pageactually, didn’t take it that way. sometimes even when I do rtfm I tend to miss more the more times I read it. I was actually looking at add_menu_page and related documentation. I’m just glad that someone replied before I stumbled over it myself. Probably saved me several hours of banging my head on the keyboard 🙂
Forum: Hacks
In reply to: Custom Post Type below Options PageYep, thank you. I’ve read that page more times than I can count and didn’t recall that bit of information. Appreciate your time. Now I know what I’m looking at.
Forum: Plugins
In reply to: [Contact Form 7] permanently dismiss warningFor others like myself that are not interested in seeing these errors and warning, this seems to effectively remove them until such time that there is some other way to accomplish it. Add this to function.php
add_action('init', 'remove_cf7_error_filters'); function remove_cf7_error_filters() { remove_action('wpcf7_admin_notices', 'wpcf7_notice_config_errors'); remove_action('admin_notices', 'wpcf7_notice_bulk_validate_config'); add_filter('wpcf7_validate_configuration', '__return_false', 20); }Forum: Plugins
In reply to: [Contact Form 7] permanently dismiss warningEven the validation errors are quite annoying…
“This email address does not belong to the same domain as the site.”
I use SMTP. The email addresses I use here will never belong to any domain that I build. Having my clients see these messages will just confuse them.
These continuous warning and error messages are unacceptable and there needs to be a way to dismiss them when they are meaningless.