TNG 10.1.3, WP 4.5, Plugin v.9 display issue

[HeatherFeuer]

I am trying to get the plugin working for a site where for some reason the Kloosterman issue is not working as expected. Once installed and configured, the designated wordpress page displays the tng index.php and no matter what link you click on, it takes you back to the index page. Also the drop-down portions of the menu do not display.  If I do a search on a surname, the search results display correctly, but if you click on one of the names, you are sent back to the index page.

Any suggestions for why this is happening and how it can be fixed? Thanks! The site in question is http://www.cadfhs.org/family-trees

[theKiwi]

I would be first looking at the .htaccess file and the permalink settings to see if there's anything amiss there.

Roger

[HeatherFeuer]

Hi Roger,

There is one .htaccess file in the root directory that contains just:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

WordPress is installed in the root folder as required for Kloosterman's method, but that really shouldn't make a difference should it? Permalinks are set to %postname%. Should there be an .htaccess file in the tng (genealogies) directory directing tng to look in the root folder?

[theKiwi]

No, I think there should only be one .htaccess file. I'm not sure what a .htaccess in the tng folder would need to say

All of the setups I've got have the two folders in parallel

tng
wp

The .htaccess file you've quoted above is identical to one on my site where WordPress is in wp, not the root, but of course the root does hold index.php which is being referenced there, so maybe that's OK.

Looking at what is happening, links like

http://www.cadfhs.org/family-trees/browsemedia.php?mediatypeID=documents

 

are being rewritten to

http://www.cadfhs.org/family-trees/?mediatypeID=documents

the "browsemedia.php" is being stripped out of it.

If you have access to the Apache server, there's a way to get it to log the rewrite rules so you can see step by step what has happened and caused that to happen. See the "Logging" section here

http://httpd.apache.org/docs/current/mod/mod_rewrite.html

maybe that will offer a hint of what is going on?

Roger

[HeatherFeuer]

Hi Roger,

I did as suggested and may have found the problem but not sure how to fix it. The log shows this:

[Mon May 02 06:33:08.423934 2016] [rewrite:trace3] [pid 11093] mod_rewrite.c(468): [client 67.253.51.174:64306] 67.253.51.174 - - [www.cadfhs.org/sid#7/sid#7f84fefff4e0][rid#7f84fefbb3f0/initial/redir#1] [perdir /var/sentora/hostdata/cadfhs/public_html/] strip per-dir prefix: /var/sentora/hostdata/cadfhs/public_html/index.php -> index.php, referer: http://www.cadfhs.org/family-trees/

If I'm reading this correctly, every link is being referred back to family-trees/index.php?

[theKiwi]

I have no idea what's happening - when I have had that turned on, there is usually a series of lines logged as the request is processed, but in any case maybe the answer is somewhere here - a Google search

strip per-dir prefix

Roger

[HeatherFeuer]

Okay. So far, I have figured out that what is happening is as I suggested... If I have a url that is http://www.cadfhs.org/family-trees/getperson.php?personID=..., the rewrite rule is stripping the "getperson.php" and replacing it with "index.php", which, of course, defaults to http://www.cadfhs.org/family-trees/?personID=... What I can't figure out yet is how to prevent that from happening. I know there should be a conditional that will fix it, I just can't figure out what it would be. Still researching.

This is strange -- I have NEVER come across this before!!

[theKiwi]

Did you read some of the pages that Google search turned up - e.g. one of them suggested that FollowSymLinks has to be On for things to work correctly.

Something is happening on the server that is causing this, and if you can't see any other rewrite rules in the .htaccess file(s) you have access to then the problem is a server wide setting that has been made, or not made.

Roger