Forum Replies Created
-
Posts
-
Your server is running in PHP “Safe Mode.” In Safe Mode, the operation of certain PHP functions is restricted or ignored. The set_time_limit() function is one of them.
If you were to create a PHP file, called “test.php” containing the following one line:
<?php phpinfo(INFO_ALL); ?>
…And then execute it as yoursite.com/test.php you will get a whole bunch of stuff about your PHP configuration. One of those is “max_execution_time” under the “PHP Core” section. It specifies the maximum number of seconds any given PHP script is allowed to run.
So, by default, any file that is downloaded must be downloaded in under that number of seconds, “…or else” the Hosting Gods step in and terminate the download script. The download script attempts to “turn off” the timer.
It is preferred that you try to get your hosting provider to turn Safe Mode “off.”
P.S. If you do create the “test.php” file, please delete it after you see the information; so that your configuration remains confidential.
I just figured it out, why your counts stay at zero…
You are not limiting the number of times customers can download a particular file…
Under eStore -> Settings -> General Settings -> Digital Product Delivery Settings -> Download Limit Count, you either have left it blank or set to 999.
If there is no limit, eStore doesn’t bother keeping count, LOL!
Mystery solved
Under eStore -> Settings -> Addon Settings -> WP eStore Download Manager Related is a checkbox labeled “Automatically Convert to Relative URL.” If it is unchecked, check it. If it is checked, uncheck it. Then save the settings and try again.
Does this change anything?
Also, what did you enter for the product’s URL?
Are you talking about changing domain names? If so, according to the WordPress CODEX, you’ll have more than just eStore to worry about:
In the root level of your website, create a test.php file that contains the following line:
<?php phpinfo(INFO_ALL); ?>
Then, execute it from your browser as http://yoursite/test.php
Make a copy of whatever it gives you, and then delete the test.php file.
In file eStore_classes/eStore_dlmgradm.php on lines 3:
static function settings_menu_html() {
change to:
function settings_menu_html() {
And on line 38:
static function settings_menu_post($eStore_auto_convert_to_relative_url, $eStore_download_method) {
change to:
function settings_menu_post($eStore_auto_convert_to_relative_url, $eStore_download_method) {
Essentially, you are removing the word “static” from before the word “function.”
In file eStore_classes/eStore_dlfilepath on lines 3, 21, 36, and 62:
Remove the word “static” from in front of the word “function.”
This should correct the problem.
I apologize. I was going by what I saw on your site, and was under the impression from your questions that you were still trying to get WordPress working.
Emergency fix:
On line 2 of the wp_digi_cart_admin_menu.php file it says:
require_once(‘eStore_classes/_loader.php’);
Change to:
//require_once(‘eStore_classes/_loader.php’);
require_once(‘eStore_classes/eStore_dlmgradm.php’);
These changes are required for the download links to work.
This will allow the eStore to activate.
You must also make the following changes to the download.php file…
On line 7, find:
require_once(‘eStore_classes/_loader.php’);
Change to:
//require_once(‘eStore_classes/_loader.php’);
require_once(‘eStore_classes/eStore_dlfilepath.php’);
Please let me know if this works. I also have some more questions for you later, about your particular system.
I visited your site this morning. Looks like you really just want to “sell stuff,” and as you said not run a blog site. It also appears that you are very knowledgeable about MIDI files, but not about how to setup WordPress, etc. Since it seems you are not quite at the point yet, of setting up eStore and are still working on just getting WordPress up and running; would you like to take this discussion offline and communicate one-on-one?
If so, please visit my site (click on my profile name) and complete a contact form, with your e-mail address (click on the Contact tab).
The “.htaccess” file, we have been talking about, should be INSIDE the folder containing your mp3 files. It is a text file, but its name is “.htaccess” NOT “.htaccess.txt” or anything else, just plain old “.htaccess” (without the quotes!).
If your site already has a robots.txt file, then you should just add the appropriate “Disallow” lines to it, so as to disallow access to your mp3 folder.
@uNeedStuff — The reason I specifically recommend an “.htaccess” file for the folder containing downloads, is to reduce the risk of problems, should someone later edit a higher level “.htaccess” file, by creating multiple failure points in the security architecture.
Large retail stores, such as Walmart, are a good analogy of what I mean by multiple failure points. They rely on CCTV, anti-theft tags, store detectives, and locked cabinets to prevent theft; not just the “greeter” at the door.
Also, it reduces the amount of damage someone could cause; by changing something else that they shouldn’t have
Hi,
Because your questions are specific to the WordPress product itself, I’d like to make the following suggestions…
The best source for information on WordPress permalinks, of course, is the OFFICIAL WordPress Codex:
http://codex.wordpress.org/Using_Permalinks
Notice how the above link is a so-called “pretty” permalink. The information provided should answer your questions.
If you wish to ask further questions about permalinks, the WordPress company (Automatic) has its own discussion forum:
Use your favorite text editor. Inside the .htaccess file, the one and only line should be:
Options -Indexes
PLEASE REMEMBER, this is the .htaccess file in your mp3 directory, not the one in your site’s root directory we are talking about.
Please see this…
https://support.tipsandtricks-hq.com/forums/topic/software-licensing
Maybe Amin has something like this in mind as a “feature?”
What would be really good is if the plugin had some way to check for updates, like the others do for the free WP plugins; except the updates would come from your server instead.
