furls (Wayfinder/.htaccess) issue (?)

Hi Folks
I'll get my first local site up and running if it's the last thing I do!

After running into problems I couldn't solve, I have begun rebuilding it from scratch and following instructions to the letter.
I now find that when I turn 'furls' on (and they show correctly at the bottom of the browser on mouseover)
I cannot navigate to any other page…
I get this message
'The requested URL /index.php was not found on this server.'

However, if I switch 'furls' off, navigation seems fine.

I have tried many solutions/suggestions to common hiccups that I've found on this forum and others…

ie.
System Setting: 'automatic_alias' on and off.
System Setting: 'use_alias_path' on and off.
System Setting: 'compress_css' on and off.
System Setting: 'compress_js' on and off.
<base href="[[!++site_url]]" /> exists inside a chunk called by my baseTemplate.
Re-installing and caching a number of times.
Manually emptying core/cache.
etc.

re '.htaccess':
As '.htaccess' remains in the original folder with MODX,
these lines look like this:

'RewriteEngine On
RewriteBase /'



As a shot in the dark I ran Everett Griffiths' diagnostic script and I get this…


???

So it's last resort time again…

I'm using:
MODX (latest (2.3.3))
MAMP (latest (3.0.7.3))
PHP (5.5.18)
MySQL (5.5.38)
Chrome: Std and Canary (latest versions)…(although I have tried other browsers)
Mac OX (Lion-10.7.5)

Any guidance would be much appreciated
Kind Regards
Chris Ray [ed. note: geordiechris last edited this post 11 years, 4 months ago.]

I assume your AllowOverride directive is set to All? This sounds more like a MAMP config issue than a MODX issue.

Thanks a lot for the response…

It was set to 'None'. I switched to 'All'.
Relaunched MAMP. Cleared MODX/browser cache etc.
No Change.

Also made sure 'LoadModule rewrite_module modules/mod_rewrite.so' was (already) uncommented.

I did at one point have the site working quite well (albeit rough around the edges)…including furls and Wayfinder,
but not at any point did I fiddle with MAMP.
This is the first time MAMP has been mentioned in this context in all the stuff I've read up on.

So should the 'AllowOverride' be set to 'All' as a rule then?
(this is something I've not been aware of at all).

Should I be concerned with this excerpt of .htaccess?
(namely the bottom line)



Thanks again [ed. note: geordiechris last edited this post 11 years, 4 months ago.]

My understanding is AllowOverride should be set to All but I'm no MAMP expert. Given that you're using the default .htaccess (stupid question, but I assume you did convert it from ht.access to .htaccess?) and you don't have a funky config (core outside of web root, that sort of thing) I'd be pretty surprised if this wasn't either a server issue or a config.inc problem.

Have you tried re-running MODX setup? It can often iron out issues with your config setup if that's the trouble.

Yeah .htaccess is correctly named.
I've re-run setup a few times.
Nothing funky config-wise.

"It can often iron out issues with your config setup if that's the trouble"

Is that core/config/config.inc.php?
If so, what would I need to be looking at there would you say?

Otherwise, I'm at a loss...

It sounds like MAMP isn't detecting the .htaccess file at all, try http://stackoverflow.com/questions/7670561/how-to-get-htaccess-to-work-on-mamp

Hi Paulp

I've looked at the link you kindly sent me and it suggests…

"...and change these from ...

<VirtualHost *:80>
ServerName ...
DocumentRoot /....
</VirtualHost>

To this:
<VirtualHost *:80>
ServerAdmin ...
ServerName ...

DocumentRoot ...
<Directory ...>
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory ...>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
</Directory>
</VirtualHost> "

I cannot locate the '<VirtualHost *:80>' bit anywhere in the 'httpd.conf' file.
Should that (<VirtualHost *:80>) be read literally or does it represent some kind of placeholder?

Also re MAMP PHP Cache'ing…I'd read a while ago that APC is the way to go.
Any thoughts on that or that that might have some bearing on things here?

Last of my hair about to be pulled out!

Many Thanks

(Great work with ref the campsites site btw)

Hey Guys


It looks like it was to do with these two lines in .htaccess after all…

RewriteEngine On
RewriteBase /

I have my MODX in a subfolder of the root i.e. HTDOCS/mySite

I think before where I'd entered 'RewriteBase / mySite' (as I gather is correct),
without making the changes you guys have suggested i.e. 'AllowOverride All' it just wasn't playing ball.

So I omitted the 'mySite' thinking I'd misunderstood which was the root folder and
exactly where my .htaccess was within the file system.
And this strangely still worked but only to the point which prompted my original query.

So maybe it was a case of me simply looking in the wrong place for the answer.

I hope that makes sense.

Any further thoughts or differing opinions would be appreciated.

Many Thanks
Chris

Quote from: geordiechris at Jun 11, 2015, 07:48 AM

Hey Guys
I have my MODX in a subfolder of the root i.e. HTDOCS/mySite

That's kinda what I meant by "funky config". If the web root configured in your server is different than the root directory you have MODX installed in you definitely need to indicate that in your htaccess RewriteBase setting. If you haven't done that since changing your AllowOverride setting that may be the fix. If it doesn't do the trick, absolutely check your core/config/config.inc.php file to be sure all the paths are correct.

Yes I think the htaccess RewriteBase setting was correct, then I changed it along the way while I was trying to get things back on track.

This bit still puzzles me though…
my core/config/config.inc.php shows the correct paths for everything and yet
when I ran Everett Griffiths' diagnostic script I got this…

/home/myDomain/public_html/site_name/connectors/browser folder does not exist!
/home/myDomain/public_html/site_name/connectors/context folder does not exist!
/home/myDomain/public_html/site_name/connectors/element folder does not exist!
/home/myDomain/public_html/site_name/connectors/layout folder does not exist!
/home/myDomain/public_html/site_name/connectors/resource folder does not exist!
/home/myDomain/public_html/site_name/connectors/source folder does not exist!
/home/myDomain/public_html/site_name/connectors/workspace folder does not exist!

Just by adding empty folders with the names of those that don't exist I get the
'All looking ok' message…
That doesn't make a lot of sense to me.
A strange niggle really...


Anyway, thanks a lot for your time,
Much appreciated