EGF
Forum Replies Created
-
Forum: Plugins
In reply to: [Mailgun Email Validator] Mailgun no longer free 100 validation limityes this looks like it will do the job. I will try it out.
Thank you.Forum: Plugins
In reply to: [Mailgun Email Validator] Mailgun no longer free 100 validation limitUnfortunately, “is_admin()” does not help as there are still many duplicate validations. I believe the bulk of them are coming from WooCommerce “front-end” orders.
Forum: Plugins
In reply to: [Mailgun Email Validator] Mailgun no longer free 100 validation limitOk, even with my additional conditions I still see many validations when an WooCommerce customer order is triggered (approx. 50 validations per order). I will try your suggestion to add the “is_admin()” condition to see if this helps eliminate them.
Thank youForum: Plugins
In reply to: [Mailgun Email Validator] Mailgun no longer free 100 validation limitI believe someone else mentioned that is_email() function is called many times in WordPress thus this is the reason for excessive (unnecessary) usage of Mailgun e-mail validation.
The problem is not only WooCommerce. I’ve found that editing/saving/modifying a contact form in Contact Form 7 plug-in also causes dozens of unnecessary Mailgun API calls. I would assume this is the case for other plug-ins that use some sort of is_email() functionality.
Some suggestions;
ignore validating e-mails that belong to the site owner, for example, mysite@mysite.com
have option to only validate e-mails that originate from a specific page(s). For example, a contact form.
I’ve been able to eliminate most of unnecessary Mailgun API calls by preventing “admin.php”, “post.php” and “admin-ajax.php” using $pagenow conditions but a better solution could be to only allow the validation to occur on the pages you want.
Thank you for providing this plugin but it can be a problem if no limit is set in the Mailgun account. The result could be a hefty $$$ bill for thousands of repetitive validation requests. Perhaps you can come up with an elegant solution to this problem?
Forum: Plugins
In reply to: [Mailgun Email Validator] Mailgun no longer free 100 validation limitif I add a customer note in a woocommerce order, it will generate approximately 10 identical API requests to the same email address. Also if a new order is processed it will also generate several API requests to Mailgun.
I added additional code for post.php and shop_order post type, but was not successful.
if ( "edit.php" == $pagenow && "shop_order" == $wp->query_vars['post_type'] ) { return TRUE; } if ( "post.php" == $pagenow && "shop_order" == $wp->query_vars['post_type'] ) { return TRUE; }I have approximately 30 plug ins enabled, many are woocommerce related. I can send via PM the list but if you have any ideas what to check in the meantime please let me know.
update; it appears the following code solves the problem
if ( "post.php" == $pagenow ) { return TRUE; } if ( "admin-ajax.php" == $pagenow ) { return TRUE; }but I am unsure if excluding post.php or admin-ajax.php would prevent the mailgun validator from working elsewhere.
Forum: Plugins
In reply to: [Contact Form 7] problems with reply addresses showing noreply@testmail.comyou can try adding this code in your themes functions.php file
/* changing default wordpress email settings with this function it changes the 'WordPress' name to your website name in the e-mails sent out from within WordPress */ add_filter('wp_mail_from', 'new_mail_from'); add_filter('wp_mail_from_name', 'new_mail_from_name'); function new_mail_from($old) { return 'youremail@yourdomain.com'; } function new_mail_from_name($old) { return 'You Name Goes Here'; }Forum: Plugins
In reply to: [Contact Form 7] Mail(2) Settings show syntax error for To: fieldFYI I created a brand new form and default values were automatically filled in. The default values created when mail(2) is enabled generates a Syntax error for the To: field.
Forum: Plugins
In reply to: [Contact Form 7] Problem with my configurationhave you tried changing your ‘from:’ field ?
From: [your-name]<wordpress@directorsoi.com>to
From: wordpress@directorsoi.comForum: Plugins
In reply to: [Contact Form 7] Syntax Errortry adding a “*” after select in your form code if it is not already there
[select* your-recipient ...]Forum: Plugins
In reply to: [Contact Form 7] Mail(2) Settings show syntax error for To: fieldthe form still works, it just always shows a configuration error in the to: field. I am unable to determine why. Also in my other form it shows 2 configuration errors , yet only one error is reported.
What exactly do you want to see? I cannot provide access to the back end of the site but I can offer any screen shots if that would help.
I was thinking of creating a brand new form..maybe there is a problem from a previous version
Forum: Plugins
In reply to: [Contact Form 7] Email (2) autoresponder email address syntax errorExact same issue here, and I have always had email field set to required field. Always showing as Syntax error in Mail(2) settings
Form:
<p>Your Full Name</br>[text* your-name /60]</p> <p>Your Company (optional)</br>[text your-company /60]</p> <p>Your valid E-mail </br>[email* your-email placeholder "email@domain.com"] </p>and,
Mail(2)
To: [your-email] This field has syntax errorsForum: Plugins
In reply to: [Invoices for WooCommerce] Logo not showing on invoiceI have same problem but all I needed to do is switch base64 encoding, as mentioned above. To do this:
go to this folder:
wp-content/plugins/woocommerce-pdf-invoices/includes/abstractsfind this file: ‘abstract-bewpi-invoice.php’
go to line: 344. add a comment //
go to line: 347. remove the comment //code snippet below:
// get the relative path due to slow generation of invoice. // $image_url = '..' . str_replace( get_site_url(), '', $image_url ); // try base64 encoding with or without relative path if MPDF gives images errors. $image_url = image_to_base64( $image_url );This worked for me. Problem is when you update PDF Invoices it will over write this change. Could there be a toggle option within the settings instead?
also note that previously generated invoices will still show the “X” instead of image even after this change, you have to CANCEL then CREATE them again for it to work.
this is the code:
<img width="1" style="position: absolute" height="1" src="//www.sweetcaptcha.com/api/v2/apps/csrfp/999999?=999999999999999&mobile=0">and this is the line of code in sweetcaptcha.php that is causing this:
wp_enqueue_script('sweetcaptcha-csrf', '//'.SWEETCAPTCHA_SITE_URL.'/api/v2/apps/csrf/'.$app_id, array(), $ver, true);Forum: Plugins
In reply to: [Sweet Captcha] WoocommerceSweet Capcha is ingnored by registrationThat version did work, but we updated to the Dec 2014 update assuming that code would include a working WooCommerce integration. It did not and I had to manually edit files again.
I had to manually add in short code into the form-lost-password.php file in your /wp-content/plugins/woocommerce/templates/myaccount folder.
the shortcode is
<?php echo sweetcaptcha_shortcode(); ?>also, for the woo login form you have to add in the following:
add_action('woocommerce_login_form', 'sweetcaptcha_login_form');somewhere under the
if (get_option('sweetcaptcha_form_login')) {condition in the sweetCaptcha.php file in your sweetCaptcha plug in folder.problem with this method is any update to woocommerce OR sweetCaptcha will remove these changes.