Forum Replies Created
-
Posts
-
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.
Is the question “Why don’t you see Method 7,” or “Where do you select the download methods?”
Method 7 will only show up if your server has the cURL library installed.
The download methods are on the “Addon Settings” tab of the eStore Settings page.
I think Amin & Ivy may need to poke around your site and have a look. Obviously, if the loader-wizard.php claims IonCube is installed and the minimum requirement checker claims otherwise, there is a problem.
I think Amin & Ivy may need to poke around your site and have a look. Obviously, if the loader-wizard.php claims IonCube is installed and the minimum requirement checker claims otherwise, there is a problem.
eStore takes care of encrypting the download links that are provided to customers.
As for securing the actual files, consider the following…
Create an empty “index.html” file in the directory that contains your downloads. For extra sarcasm, you might put a message in it like:
Find what you’re looking for?
Or better yet, a popup ad…
Or you can “play nice” and just redirect them back to your main page:
<meta HTTP-EQUIV=”REFRESH” content=”0; url=http://www.yourdomain.com”>
Also, inside the downloads directory, create an “.htaccess” file with one line:
Options -Indexes
In the server’s document root directory, create a “robots.txt” file. It should contain the following lines…
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-content/
Disallow: /wp-includes/
Disallow: /wp-content/themes/
Disallow: /wp-plugins/
Disallow: /downloads/
Basically, create a “Disallow” line for each directory you’d like robots and spiders to ignore. Note: the “robots.txt” is an optional “please don’t do that” type of thing. Search engines are not required to honor it.
To enforce mandatory exclusion of directories and files, you can add/edit the “.htaccess” file in the server’s root directory, but that gets into the “running with scissors” area. You can do some serious damage, if you aren’t careful…
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.
