My patht to the image is broken…

Geeze oneguy, sorry for not answering this. I rely on an RSS feed to notify me of requests, but it appears that this thread wasn’t added…something odd going on with WordPress.org.

As to your issues, it appears that you missed a trailing slash in the base URL. You should be using the following, instead:

{base-url}/slir/

If that still doesn’t work (the site being in a subfolder, and the tilde in the url may be causing issues) then you can use the following base URL as a quick fix:

{plugin-url}/slir/index.php?r=

Sorry for the huge delay – I got back to you as soon as I found out about the post, but that may have been two weeks too late. Let me know if that fixes the issue, if you’re still using the plugin.

You shouldn’t have to alter anything. That path to the image is correct, it looks like you have another error occurring. I can’t tell what it is from the generic error screen, but it may be related to a bug I’ve found with wordpress being hosted out of a subfolder. I’m going to be doing some testing on my own, to see if I can replicate and correct it. However, if you could find out the specific error message being thrown, it may help.

Ok – I’ve resolved a new bug with subdirectory installs. If you’d like to try that out, it’s available here:

http://downloads.wordpress.org/plugin/pb-responsive-images.1.4.zip

If that doesn’t work, we can look at how to find those php errors for you.

Lol. Excellent. That .htaccess rule shouldn’t insert, I’ll have to look at that. Go ahead and delete the following line:

RewriteRule ^wp-content/plugins/pb-responsive-images/slir/index.php?r=([^/]*)/(.*)$ /~orgad/wp-content/plugins/pb-responsive-images/slir/index.php?r=$1/~orgad/$2 [QSA,L]

We don’t want that extra complexity right now, it would be nice to just see an image, right?

Well, that .htaccess file looks fine, now. We’re bypassing it, so this isn’t the issue. We DO need to find out what actual error you’re throwing. Try pasting the following into the index.php file throwing the error:

ini_set('display_errors', 1);
 ini_set('log_errors', 1);
 ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
 error_reporting(E_ALL);

That should output the error. For the future, I’d recommend on getting your server configuration set up to display errors if you’re using it for development. If the script above doesn’t show the relevant errors, it may be worth googling php error reporting to get that set up.