HTMLAREA Image Manager htaccess help

[beasleybub]

I need a bit of help and hope someone can get this worked out.

I installed HTMLAREA Image manager many moons ago and it did not work when initially installed. I played with the htaccess file and got it to work.

Recently I restored my cart from a backup and now the image manager is goofing once again. I've tried temporarily removing the htaccess file to make sure the manager still works and it does.

I've also tried directly accessing an image from the images folder in the browser using a url like mywebsite/mystore/images/image.jpg and it shows up.

I tested a theory that something inside the folder is causing the htaccess to block access. ( htacces is doing it's job ) I edited the htaccess and removed the extension jpg and retried directly accessing the image. The result was of course a 403 error as expected.

So I believe the image manager is working right but the htaccess is blocking something.

What do you think?

[beasleybub]

Well, So far my theory just got shot down. I deleted everything inside my images folder except some jpg images and even deleted the htaccess file inside the images folder. Still have the 403 error. It seems to be an issue with the htaccess from inside the editors folder.

Here is the htaccess file contents.

# @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
# @version $Id: .htaccess 16685 2010-06-08 17:19:53Z drbyte $
#
# This is used with Apache WebServers
#
# The following blocks direct HTTP requests to all filetypes in this directory recursively, except certain approved exceptions
# It also prevents the ability of any scripts to run. No type of script, be it PHP, PERL or whatever, can normally be executed if ExecCGI is disabled.
# Will also prevent people from seeing what is in the dir. and any sub-directories
#
# For this to work, you must include either 'All' or at least: 'Limit' and 'Indexes' parameters to the AllowOverride configuration in your apache/conf/httpd.conf file.
# Additionally, if you want the added protection offered by the OPTIONS directive below, you'll need to add 'Options' to the AllowOverride list, if 'All' is not specified. 
# Example:
#<Directory "/usr/local/apache/htdocs">
#  AllowOverride Limit Options Indexes
#</Directory>
###############################

# deny *everything*
<FilesMatch ".*">
  Order Allow,Deny
  Deny from all
</FilesMatch>

# but now allow just *certain* necessary files:
<FilesMatch ".*\.(js|css|jpg|gif|png|html?|xml)$">
  Order Allow,Deny
  Allow from all
</FilesMatch>
## NOTE: If you want even greater security to prevent hackers from running scripts in this folder, uncomment the following line (if your hosting company will allow you to use OPTIONS):
# OPTIONS -Indexes -ExecCGI
IndexIgnore */*

what in the world!