Forum Replies Created
-
Posts
-
In the media library settings you most likely have the settings enabled to do compression for the image.
Edit the image by clicking the edit link from the gallery. It will open the media library interface for that image. Look at the “File URL” field. Check the name of the image file from there. Does it have the full image there or is that a resized/compressed version of the image?
This is going to be an issue related to a server conflict somewhere. Something is getting stuck. Do you have anything in the server’s error_log file that can offer some clues?
This is not going to be a trivial solution unfortunately. Even if you do all the coding, I will still have to spend a fair amount of time understanding the requirement and how things might be implemented (with the way the plugin currently works).
You will need to use the following option:
If your site is being targeted by bots then using that default black-list option is not a good idea. That blacklist option is really for humans members who you want to ban (it’s purpose is not to block the bots).
If a site is being targeted by bots, then the following captcha option should be used to block those in the first place:
Are you using that captcha option?
Please do the following and let me know if you see the issue after that:
The Masonry style template is most likely the best option for you. Have you tried template 7?
Please take a look at the following addon to see if that will be helpful:
If you are using WooCommerce already, then you shouldn’t need to use WP eStore. You only need to do the following to make a WooCommece product for the PDF file:
That PDF file will get stamped when the customer clicks on the download link sent by woocommerce (after a transaction).
These are completely separate plugins with completely different database table structures. It will need a custom developed script to handle that kind of migration.
Anything that we don’t advertise on our WP eMember’s feature list, don’t expect it to be there. I will send you an email for it.
We don’t do anything with that other plugin you are using. It becomes very difficult to maintain hooks to external plugins (as they will make changes without us knowing about it and so on). We prefer to do this kind of integration with our own plugins for better maintainability over long term.
Just to clarify, there can only be ONE auto-upgrade sequence happening at one time to one member profile. Some users mess things up with the multiple levels feature and then try to configure two concurrent auto-upgrade scenarios and stuff (sometimes without realizing it). So a good idea is to sit down with a piece of paper and work out the auto-upgrade path a member will take. Then you can make sure the path is straightforward and setup correctly.
WP eStore will try to check the PayPal email address (from the transaction) and match with a member’s profile to see if there is an existing profile or not. However, some users use multiple alias emails in their PayPal account so it is not a 100% foolproof way to detect existing users.
The best foolproof option is to force a user to log-into the site then do a transaction. That will ensure that the plugin will know for sure that the transaction came from an existing user and the payment will be applied to that profile.
