[RESOLVED] Evo 1.0.14 - Only New Documents Return 404 When Called by .HTACCESS Rule

Hello all.

Firstly, let me say that this issue has brought me to upgrade from 0.9.6 to 1.0.14.
Transition was quick, easy and flawless, and the new touch and feel is great.
It also seems that the Manager CP is so much lighter in its responsiveness.
Thank you, wonderful MODx developers and supporters for your dedication and outstanding outcome.

And now, to the issue itself: I have added a new document (DocID = 101)
I can render it perfectly by calling its DocID and a unique segment from its friendly URL:
http://www.celebrities-galore.com/index.php?id=101&filename=albert-einstein

However, it returns a 404 when called by its friendly URL:
http://www.celebrities-galore.com/celebrities/albert-einstein/contact/
even though the .HTACCESS rule is in place:
RewriteRule ^celebrities/(.*)/contact/$ /index.php?id=101&filename=$1 [PT, NC, L]

I have attached the .HTACCESS file.

Now, here are a few pointers to consider:
1. The new page is only one of many that adhere to the exact same tactics, and work perfectly.
For example: http://www.celebrities-galore.com/celebrities/albert-einstein/birth-data/ (DocID=419)
2. I have cleared and manually deleted assets/cache numerous times.
3. I have restarted my IIS7 and physical server.
4. I have tried to create some other documents or activate older, un-published documents
with different aliases, other than "contact", and they all fail to be served.
5. It has been over a year back when I have added or maintained documents for the last time.

Your help is greatly appreciated.

Thank you,
Shlomo Tommer [ed. note: shlomot last edited this post 11 years, 11 months ago.]

First: Try out the latest bugfix version from https://github.com/modxcms/evolution/archive/bugfix.zip

If that is not successful:

I'm not absolutely sure, but having FURL activated could cause MODX to redirect id=xx to the FURL of that id to avoid duplicate content. That could cause your issue if you have an own 404 handler when $_GET['filename'] does not exist. But that is just poking around in the dark, since I don't know your installation.

One thing you could try, is to use the real FURL of that resource in .htaccess and let MODX do the rest. Replace

with

[ed. note: Jako last edited this post 11 years, 11 months ago.]

Do you have System configuration > Friendly URLs > "Use SEO Strict URLs" enabled?
Try to disable it.
SEO Strict URLs always interferes with my custom rules

Thanks Banzai.

My FURL setting is disabled altogether.

.HTACCESS covers all published documents, and aliases are out of the picture altogether.

Quote from: banzai at Oct 09, 2014, 10:35 AM

Do you have System configuration > Friendly URLs > "Use SEO Strict URLs" enabled?
Try to disable it.
SEO Strict URLs always interferes with my custom rules

Now I have read some more about Microsoft IIS and found out that to allow for FURLs, the Apache MOD Rewrite rules are being imported into httpdocs/web.config (feel free to ask me more about how to perform the import).

web.config didn't include the new rule for the new document, BUT THAT HASN'T HELPED EITHER :-(

I wonder if there is a way to use the "Use Friendly URL alias path" setting?

Going back to http://www.celebrities-galore.com/celebrities/albert-einstein/contact/
It's easy enough to set a dummy container document for /celebrities/
But how would I set a document's alias on the fly for albert-einstein ?
albert-einstein is a unique row identifier in a table of ~300K celebrities.

Any idea?

Have you tried the bugfix version?

Which bug fix, Jako?

Quote from: Jako at Oct 10, 2014, 02:09 AM

Have you tried the bugfix version?

Look above.

Quote from: Jako at Oct 10, 2014, 09:53 AM

Look above.

It's a 404 because of the . at the end ;o)

https://github.com/modxcms/evolution/archive/bugfix.zip

Fixed.