Forum Replies Created
-
Posts
-
Since the wizard claims that IonCube is installed…
Undo that last change, you made, after the wizard claim it was working.
Try temporarily renaming that .htaccess file to something else and see if it works now.
Inside the ioncube directory should be a “loader-wizard.php” file. Run it, from a browser.
I suspect it will say something like IonCube not properly installed. It will then attempt to troubleshoot your php.ini files.
Each encrypted download link is unique. You can do one of two things…
1. Manually generate links for each customer, using the “Admin Functions.” Not fun, if you have a lot of customers.
2. Invite them via a mailing list to download the new version.
You might also consider adding some kind of upgrade notification system to your plugin.
P.S. I found the upgrade instructions you most likely used:
http://www.tipsandtricks-hq.com/ecommerce/wordpress-estore-installation-and-usage-guide-31
And it says…
“If you haven’t stored the downloadable files inside the “downloads” directory of this plugin then you can follow this method of upgrade… * Delete the current version of the WP eStore plugin from the Plugins menu.”
Perhaps Amin or Ivy should edit the instructions to read “…haven’t store the downloadable files anyplace inside the wp-cart-for-digital-products directory…”
1a. There is nothing preventing you from keeping the folder that houses your mp3 files in the wp-cart-for-digital-products folder. HOWEVER…
1b. It is a “best practice” to keep the files someplace else, to prevent accidents like this from occurring.
2a. If you do your upgrades by simply overwriting the existing (old) files, your mp3 folder is unaffected.
2b. If you are a neat-nik like me, who likes to keep things pure and simple by deleting old stuff, then you must either keep your mp3 directory someplace else or be very careful of what you delete.
3a. As per “1b,” it is a best practice to keep your data (mp3 folder) in a separate directory. It can be at the top level (www.example.com/stuff) and will still be protected by the encrypted links. Don’t call it “mp3s-4-sale” just “stuff1,” “stuff2,” etc.
3b. You can also name the folder “.stuff” (prefix the name with a period) to make it invisible to casual drive by browsing. For “extra protection,” create an “.htaccess” file in your mp3 folder (***NOT THE TOP HTML DIRECTORY***) that contains one line:
Options -Indexes
That way, even if someone stumbles across the folder, they can’t see what’s inside; unless they start guessing at the file names.
As a suggestion, the safest way of replacing a plugin directory is to first make a backup, before deleting it:
zip plugin.backup.zip plugin
rm -rf plugin
mv plugin.backup.zip old.plugin.storage.directory
I hope this mishap was something you were able to recover from.
Yes. You would create a “product” as though it were a physical one, requiring shipping; with the understanding that it would be delivered “later.” This “understanding” would be in the product description, and in the terms & conditions.
The only caveat is that you must follow through with manual processes to fulfill the customer’s order.
Anyone can “makeup” a business name. The only way you are going to sell products to bona-fide businesses **only** is through a process which involves human vetting of the transaction. You could use the scenario in your other post, as a way to do this:
Are you really trying to only sell products to bona-fide businesses, or are you just trying to force them to fill out the field?
I suppose, what Amin could do, is add a [product_id] footer tag to the Stamper. That way, a file could be stamped as “Product A – Personal Edition” or “Product A – Commercial Edition.” Or maybe even add a [variation] tag as well…
How about it, Amin?
If you upgrade to version 4.4.7, you’ll notice that:
1. The methods now have descriptions to go with the numbers.
2. A 7th method has been added to the menu.
Note: Method 7 will only show up in the menu if the cURL library is installed on your server.
For future reference, you are welcome to contribute your solution; in case somebody else finds this thread.
I know that, unless you have a bit of “code monkey” in you, these descriptions won’t help much… but these descriptions are based upon the characteristics of each possible download method:
(Default) 1. Fopen using 8K chunks with closed session.
2. Readfile using 1M chunks remote stream.
3. Fpassthru.
4. Readfile using 1M chunks local.
5. Fopen using 8K chunks with opened session.
6. Fopen using 1M chunks with closed session.
There is also a 7th method, “cURL” that is (currently) only invoked if URL aware fopens are disabled.
