Komentáře k příspěvku: Simple Download Monitor plugin

Od: pepak

pepak — Wed, 03 Feb 2010 20:29:53 +0000

I am afraid there is little I can do to help you. Apparently your WordPress is set up without mod_rewrite. It may be that it is not supported by your webhost, in which case there is nothing you can do to make Simple Download Manager work. Alternatively, it is possible that mod_rewrite is supported but isn’t used – in that case you can try to place this in your .htaccess file:


	RewriteEngine On
	RewriteBase /
	RewriteRule ^(files/.*) /index.php?sdmon=$1 [L]
	RewriteCond %{REQUEST_FILENAME} !-f
	RewriteCond %{REQUEST_FILENAME} !-d
	RewriteRule . /index.php [L]

Note: Unless you are really sure you want to have Options +Indexes I would turn it off – it can be a serious security hole in certain circumstances.

Od: rafu

rafu — Wed, 03 Feb 2010 20:06:21 +0000

i have installed the plugins and didnt worked well i check my .htaccess file didnt got any line writen that called RewriteCond %{REQUEST_FILENAME} !-f

it’s just writen

Options +Indexes

# BEGIN WordPress

# END WordPress

PLEASE TEL ME WHATS SHOULD I DO

Od: pepak

pepak — Sun, 24 Jan 2010 07:50:36 +0000

Version 0.10 provides compatibility with PHP 4 and a belarussian translation by FatCow.

Od: pepak

pepak — Mon, 11 Jan 2010 05:20:42 +0000

It seems your hosting doesn’t use PHP 5. While it would be possible to rewrite SDM to work with PHP 4, I have no way of testing it.

Od: Kyle

Kyle — Sun, 10 Jan 2010 22:50:23 +0000

when i install this plugin, both manually or threw wordpress, i get this error message opon activation: Parse error: parse error, unexpected T_CONST, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /ndd5/wp-content/plugins/simple-download-monitor/simple-download-monitor.php on line 34

Od: pepak

pepak — Sun, 10 Jan 2010 13:18:11 +0000

What kind of shortcode do you mean?

Od: esanstudio.net

esanstudio.net — Sun, 10 Jan 2010 12:56:35 +0000

Any shortcode given to apply into WP PAGE?

Od: pepak

pepak — Sun, 10 Jan 2010 07:55:52 +0000

Version 0.09 fixes the issues reported by Angelo. Thanks!

Od: pepak

pepak — Thu, 07 Jan 2010 19:50:31 +0000

1) If I use content-size, it is an error – content-length is the correct one. I will check it out and correct it. Thanks for the alert.

2) I didn’t know about that. I will see about adding range support to SDM (it would be easier to use HTTP/1.0, but I expect range support will allow the users to continue broken transfers).

Thanks!

Od: Angelo Mandato

Angelo Mandato — Thu, 07 Jan 2010 19:39:20 +0000

First problem is your script is not including the „Content-Length“ header. I do see „Content-size’, but that is not a valid HTTP header. Typically the second world is Capitalized though most clients will handle content-length or Content-Length.

Second problem is with the protocol returned, you need to change the protocol to HTTP/1.0 or add support for range requests. PowerPress plugin requests the first 500KB of the file by using an HTTP „Range: 0-500000″ request. I just took a look at your plugin and it does not support byte ranges, which can create a problem for anyone who may want to resume downloads. It does not create a problem for PowerPress so as long as you change the returned HTTP Headers return HTTP/1.0 (rather than HTTP/1.1). You can detect and appropriately handle a byte range request with the following: isset($_SERVER['HTTP_RANGE']) and parse it to know what portion of the file to return.

Please refer to the RFC (http://www.faqs.org/rfcs/rfc2616.html) for HTTP to learn more about ‘Content-Length’ and ‘Byte Ranges’. This page has an example how to handle multiple and single byte range requests in PHP: http://www.coneural.org/florian/papers/04_byteserving.php