Thread

I encountered this problem while working with brandon kelly’s wygwam, however it is not a problem with his extension but rather with the setup of expression engine.

my problem is that any php files higher than the extension folder are not being processed properly…I found this out when it wasn’t possible to connect to the connector.php file in the wygwam, making the image browser through the fckeditor not function properly.

Running EE 1.6.8
Build 20091002

for example:

http://www.mysavu.com/eesystem/extensions/test/test.php
returns the expected echo “hello”

whereas
http://new.mysavu.com/eesystem/extensions/test/test.php

returns a 404 which is set to a footer file right now.

another example is
http://www.mysavu.com/eesystem/extensions/fieldtypes/wygwam/lib/ckfinder/core/connector/php/connector.php - works while
http://new.mysavu.com/eesystem/extensions/fieldtypes/wygwam/lib/ckfinder/core/connector/php/connector.php - doesn’t

http://new.mysavu.com is an MSM site, but it is the primary site of an MSM install, not a MSM that is in any way related to the WWW, it is an entirely different development install of EE which I am getting ready to move live and take over the current install.

I’m wondering what might be causing this because it the same site is functioning with as far as I know all of the same settings on my localhost, and it doesn’t look like .htaccess or any of the file paths seem to be the problem…

I feel like there is some sort of setting that is not letting this happen but I can’t find anything on the control panel, nor any sort of permission problems for the files…

Any help would be greatly appreciated, I’m trying to move forward with this project in the next day or so and this is the only thing that seems to be holding me up.

Tim,
are you removing index.php with htaccess, whats in that file?
Do you have any extensions running?

Do you have strict URLs switched on in your template preferences?

I tried disabling all the extensions and that didn’t help. But as for the list it’s

Fieldframe (Plus Ngen and WYGWAM)
SL Developer Info
User
Jquery for CP
Solspace UI
Gypsy
Rating
SL Freshview Subscribe

Also, the .htaccess file is pretty standard and just allows EE to handle errors if files and directories are not present

RewriteCond $1 !\.(gif|jpe?g|png)$ [NC] 
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ /index.php?/$1 [L]

I guess my main question is how does EE decide what PHP files should be allowed to run and which ones shouldn’t be allowed to run.

nevermind, it was a directory permissions problem…got it sorted out.

Glad you were able to figure out what the problem was. Don’t hesitate to post again as needed.