Forums / Upgrading from 1.3.x to 1.3.9 / .htaccess prevents using FCKeditor in 1.3.9a

.htaccess prevents using FCKeditor in 1.3.9a

Locked

Started by frank18 on 20 Apr 2010, 12:55 PM · Views: 3,699

Results 1 to 5 of 5
This thread is locked. New replies are disabled.
20 Apr 2010, 12:55 PM
#1
frank18 avatar

frank18

Deceased

Join Date:
Nov 2007
Location:
Sunny Coast, Australia
Posts:
3,427
Plugin Contributions:
2

.htaccess prevents using FCKeditor in 1.3.9a

Upgraded from 1.3.8a to 1.3.9a

Zen Cart 1.3.9a
Database Patch Level: 1.3.9a
HTTP Server: Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Server OS: Linux 2.6.18-164.10.1.el5xen
PHP Version: 5.2.13 (Zend: 2.2.0)

Problem:

Unable to use FCKeditor in 1.3.9a, returns 403 Forbidden

Solution:

Edit STORE/editors/.htaccess from this

but now allow just certain necessary files:

<FilesMatch ".*.(js|css|jpg|gif|png|html)$">
Order Allow,Deny
Allow from all
</FilesMatch>

to this

but now allow just certain necessary files:

<FilesMatch ".*.(js|css|jpg|gif|png|xml|html)$">
Order Allow,Deny
Allow from all
</FilesMatch>

and editor becomes accessible and functional

In case this change creates a security issue an alternative solution should be found.

Frank

NOTE: We are sorry that Frank is no longer with us.
We are grateful for all his contributions to the Zen Cart community.

21 Apr 2010, 9:14 AM
#2
blessisaacola avatar

blessisaacola

Totally Zenned

Join Date:
Feb 2004
Location:
Georgia, USA
Posts:
1,875
Plugin Contributions:
1

Re: .htaccess prevents using FCKeditor in 1.3.9a

I am currently getting a 403 error when accessing product page on the admin side using fckeditor 2.6.4.1. This issue started after upgrading to 1.3.9a.

I am sure it has something to do with the .htaccess that was uploaded to the editor folder from 1.3.9a (this is a new file). If I delete the .htaccess file from the editor folder then everything works fine with regards to fckeditor.

I looked inside the new .htaccess file and there instruction of what to include in httpd.conf file. This file is generated by the server and I am not sure if the lines below are correct or not. Can you some please help me troubleshoot this issue. I'd prefer to be able to us fckeditor.

<Directory "/">
    Options ExecCGI FollowSymLinks Includes IncludesNOEXEC -Indexes -MultiViews SymLinksIfOwnerMatch
    AllowOverride All
</Directory>

<Directory "/usr/local/apache/htdocs">
    Options Includes Indexes FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all

</Directory>

The above is the section from current httpd.conf file.

Thanks!

21 Apr 2010, 9:36 AM
#3
jynxy avatar

jynxy

New Zenner

Join Date:
Jul 2005
Posts:
34
Plugin Contributions:
0

Re: .htaccess prevents using FCKeditor in 1.3.9a

Try changing .htaccess inside the folder editors by adding |xml as shown:

# but now allow just *certain* necessary files:
<FilesMatch ".*\.(js|css|jpg|gif|png|html[B]|xml[/B])$">
21 Apr 2010, 9:43 AM
#4
blessisaacola avatar

blessisaacola

Totally Zenned

Join Date:
Feb 2004
Location:
Georgia, USA
Posts:
1,875
Plugin Contributions:
1

Re: .htaccess prevents using FCKeditor in 1.3.9a

Thank you! You're a genius! That solved my problem.

24 Apr 2010, 8:36 AM
#5
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,515
Plugin Contributions:
176

Re: .htaccess prevents using FCKeditor in 1.3.9a

FYI: You may find that the more contemporary CKEditor is a more preferred choice: http://www.zen-cart.com/index.php?main_page=product_contrib_info&products_id=1626
It also doesn't require any .htaccess edits to work.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.