I am using WP eMember Version v7.0.2 and WP eStore Version v3.4.9. I have a Multi Blog site where my second-blog site is in a sub-directory rather than a sub-domain. It is in the second (sub) blog site where I have downloadable products set up. To the best of my knowledge everything is set up properly and everything works until I click the download links for any product ID. Rather than taking me to the downloadable file it simply displays a blank page with the following two words... "link expired". I have set the expiry to 4444 hours, but no matter what I put there, it matters not. I have tried several things, including generating an encrypted links through Admin Functions which also display the same message.
Link Expired for no apparent reason
(13 posts) (2 voices)-
Posted 8 months ago #
-
Please upgrade to the latest version of eStore and try again...
http://support.tipsandtricks-hq.com/update-requestPosted 8 months ago # -
Okay, I completely removed WP eStore from the site/s and removed all WP eStore database tables putting everything back to square one. I deactivated all plugins except WP eMember. I installed the upgrade to v5.9.6 and carefully went through the settings and added a downloadable product. I did a test purchase which worked great but for the fact that I get the same result when I click on the generated link. A page that displays "Link expired". When I generate a link using Admin Functions the log file says:
[09/16/2011 12:12 AM] - SUCCESS :Generating download link for single file.
I am at a loss.
Posted 8 months ago # -
I noticed in your original post, you said you have a multiple blog site. Is eStore only installed on one of those blogs?
Posted 8 months ago # -
eStore is installed on the primary blog (www.matteroflife.ca) and activated on the sub-blog (www.domain.ca/sub_blog)
Go here to try it out...
http://www.domain.ca/sub_blog/member-page/download/Log in as... *****REDACTED*****
Posted 8 months ago # -
I am suspicious about whether or not a link generated by eStore on the sub blog, is inadvertently invoking the download.php script on the primary blog. If you are not using eStore on the primary blog, try deleting the plugin from there.
Posted 8 months ago # -
Thanks for your rapid responses! You are a real blessing!
I can't delete it from the primary blog. That is how Wordpress Multi-site works. All the plugins are installed in the primary blog server and thereby become available and activated on each individual sub-blog. Every pluggin on my sub-blog is set up and activated in this way, including eMember (working flawlessly) as well as all my other plugins.
BTW, although eStore is installed on the primary blog, it is not activated there.
I also deactivated eMember to see if somehow it was interfering. Nope!
Posted 8 months ago # -
I think I may have found the solution thanks to you, as you are thanked for sorting this issue out at the bottom of this article in the forum...
http://www.tipsandtricks-hq.com/ecommerce/how-to-customize-the-encrypted-download-url-224Posted 8 months ago # -
I am getting closer. I followed the instructions in the article above placing 'cppmembers' in the new (custom) "download.php" file and uploaded it to the http://www.matteroflife.ca/downloads/ directory.
the line is... $wp_home_dir = 'sub_blog';
I also revised the "Download Validation Script Location" field to reflect the new location of the "download.php" file to be "http://www.domain.ca/downloads/"
However, I now get the following error...
===========================================
Warning: scandir(sub_blog) [function.scandir]: failed to open dir: No such file or directory in /home/domain/public_html/downloads/download.php on line 33
Warning: scandir() [function.scandir]: (errno 13): Permission denied in /home/domain/public_html/downloads/download.php on line 33
Please tell us "the Custom Download Validation Script could not find the WordPress home directory, because the script is not properly configured." Thank you!Posted 8 months ago # -
The error occurs because the custom script is having trouble finding the correct location of the active eStore plugin directory. Because there is more than 1 copy of the plugin and WordPress installed, it gets confused. I suppose that, given you seem to be code savvy, you could always hack the custom script and give it some "help," by just hard coding the proper path to the active eStore plugin directory.
That would fix the problem for the immediacy. In order to fix the problem for future customers, and "for greater humanity," I'd need to study your configuration. If you'd like, please drop me a line on my contact form TheAssurer.com/contact and I will get back to you.
Posted 8 months ago #
Reply »
You must log in to post.