Raider10

Thanks, Sam! The developer of the photo plug-in I use sent out an update yesterday and that fixed the issue I was having. I appreciate the response!

Hi Jacob,

I did exactly as you said above – updated to today’s version and unticked that option in Table IV – and it WORKED!

Brilliant!

THANK YOU for all of your time and help on this issue – so good to see my pictures again! ??

Hi Jacob,

I contacted my hosting provider and this is what they responded:

“IISPassword parses the .htaccess files to handle the list of users allowed to view a site or subfolder. If the user’s plugin is adding custom code into the .htaccess file, then it is possible that is causing problems for IISPassword. IISPassword is very picky about extra things in the .htaccess file. If the user’s plugin adds extra Apache specific lines to the .htaccess file, then that will cause problems on the Windows 2003 platform.”

All of this is Greek to me, as I’ve never heard about IISPassword until a few days ago. Does WPPA add custom code to the .htaccess file? I believe you when you say the plug-in isn’t the issue, but I wanted to double check this fact with you before I follow-up with my host.

Hi Jacob,

Thanks for the update – I wasn’t aware that IIS Password had been installed – but I will look into this and see what I can find.

Thanks for all of your time and help!

Hi Jacob,

One other thing – I noticed the coding looks different now when I insert photos into the article. I don’t know if this is the cause of the issue or if this is how it is supposed to look – what do you think?

This is the coding that shows when I insert a photo:
[wppa type=”photo” photo=”401″]Any comment[/wppa]

Hi Jacob,

I don’t see an htaccess.php file in the wp-content folder – just in the folder it is supposed to be in.

I shut off BruteProtect for a few minutes and the pictures still didn’t show. I also tried shutting off my other security plug-in, but that didn’t change anything either.

Anything else I should be trying?

Hi Jacob,

Thanks for the quick response – I checked the wppa-htaccess.php file and didn’t see anything that looks like what you sent me above.

As for security plugins, I just recently added BruteProtect because the site was experiencing large brute force attacks. Do you think this plug-in is interfering somehow with the WPPA plug-in? I’d be hesitant to deactivate BruteProtect because I don’t want to make the site vulnerable to more attacks.

Anything else I can be telling you to help you narrow down what the issue might be?

Thank you for your help!

https://www.offenburger.com

I was never able to figure out why only the homepage was down – but I have now successfully transferred my WP blog to the root folder, and the WP blog shows up on the homepage. Therefore, this is no longer an issue. Thank you everyone for your help!

Thanks, Tara! I just figured it out – instead of “saving as” in PhotoShop, I selected “save for web” – which saved it as a .gif and it works perfectly. ??

I was finally able to get through to my host and asked them to check the error logs for my HTTP 500 message. The webmaster I spoke with said she is forbidden from seeing that page, but through visiting with her we concluded that my issue was having the index.php file in the wrong location. I currently have it in the subfolder along with the WordPress files, but it needs to be in the root folder. However, when I move it to the root folder, then the WordPress site gives me a 403 error code, saying that the site was found but “website requires you to log in.” Can anyone tell me what I am doing wrong?

Ok – thanks, Esmi. When I get home from work tonight I’ll see about accessing these error logs and will let you know what I find out.

mort3n: The General site URL is https://www.mysite.com, the WP URL is https://www.mysite.com/blog. I’m moving from a seven simple steps CMS (which is ancient) to a WordPress CMS. If this tells you how new I am to this, I’m not even sure what you mean by “static file site.”

esmi: I realize my host doesn’t need to know about WordPress to help me access the error logs – but after all I went through visiting with them last night, I’m looking for things I can be doing on my own without having to contact them again. But I will, if that’s what I need to do.

Thanks, Esmi. I spent a couple of hours visiting with someone from my host, and they didn’t know much about WordPress. Seems like there is a way to modify the index.php file? I followed the directions on WordPress about giving wp its own directory, but it’s not working the way it should.

It’s ok for the homepage to be down for a few days while we shift everything over to wp, but I would rather not have people thinking the entire site is down.