Forum Replies Created
-
Posts
-
I have made an update to the addon just now to address that warning in the TCPDF library. Please download a new copy and try it.
The customer input addon should work fine with the smart paypal checkout option also. Are you referring to the smart checkout option of the simple cart plugin or a different option?
There maybe a mix of conditions (for example: the “From Email Address”) contributing to this also. I personally use that exact same “Email Subject” and the deliveries work fine. Anyone who purchase from TTHQ site also gets delivery with that email subject which works. So I don’t think it is just based on the “subject” line.
Good to see that you got it sorted out for your site.
By default it tries to send a maximum of 100 emails per hour. However, the way WP Cronjobs work, it cannot be guaranteed that way.
All of your member’s won’t expire on the same day. For example, you may only have 25 members who will expire tomorrow. So unless there are a lot of other emails being triggered at the same time on your system, it generally should work fine.
A small customized solution maybe needed for your site with the parameters that is best suitable for your project:
We don’t have something like that. Our plugin is really for customers doing their own transactions. You would need to log into their account using their username and password.
The customer should really do the transaction to make sure the payment is not triggered as a fraud by the credit card company or the payment gateway. You can get them to do the transaction then you can manually adjust things from the admin interface (like create a member account manually from the admin dashboard).
The WP login solutions you referred to, can be used if you use the following WP user integration option (this is an optional feature).
Using eMember with Another Plugin That Uses the WordPress User Roles
The emails going to spam and the following are completely two separate items:
PayPal reports “Things don’t appear to be working at the moment”
The email issue has nothing to do with WP eStore (as explained above). The PayPal reporting an error will be related to amount value or other configuration value that you entered incorrectly somewhere. Create a separate topic for this and post the URL where we can go and see the error. Then we will be able to investigate the values being used and what is causing the PayPal error.
We didn’t receive any contact form submission in our inbox. I have sent you an email for it just now.
Please load a new copy of the plugin and this PHP Notice should be fixed now:
The first thing to understand is the following so you know where the real source of the issue is and who to ask for so you can get SMTP details for your server:
1) The email issue is related to your mail server which is configured and managed by your hosting provider.
2) Any WordPress plugin (including WP eStore), simply uses the mail function of your server to execute the email sending functionality.
3) Your hosting provider is the only one who can give you the information needed to setup SMTP for your site. You can ask them for the SMTP details and then plug those values into the SMTP plugin so the emails sent from your site are sent via SMTP (that improves the reliability of email sending and delivery).
4) WP eStore doesn’t need any SMTP configuration. You configure SMTP for your WordPress site and your server and then all the emails from that site will go via SMTP.
Fully read the following page which can provide a good understanding of why the email issue happens:
Go to the “Email Settings” menu and empty whatever value you put in the “Forgot Password” email body field. Make that text-area field empty then hit the save settings button. That will re-generate the original/default email content for that field. Then you can modify it some (keeping the email merge tags in place) and save again.
The following page should be helpful for you. It has all the shortcodes that you need to keep on the required pages of the WP eMember plugin:
Once you plug in the values and update the settings with the *updated* URL, it will connect and start to work fine.
IPv6 shouldn’t be an issue in general. There maybe something specific to this site (a combination of things) that is creating some kind of a conflict with it. Do you have the “Disable Simultaneous Member Login” option enabled in this site? If you do, disable that option. Then do a test to see if the same issue persists.
