I have a dilemma. I’m not sure if this is a bug.
I created an error page, but it doesn’t show in IE 8. All I see in IE is the default 404 page. It works in FF. If I change the error_page setting to the resource with id 1, it works fine in both browsers.
It did work before. This is what I did that caused it to stop working (but it may have just been a coincidence). I wanted to see if I could off the trailing / from my urls.
So I wanted this:
mysite.com/page
Instead of this:
mysite.com/page/
I have a content type: ’HTML - backslash’ that had a file extension of ’/’, so I deleted the ’/’ and clicked save. The error page then broke in IE and I can’t get it to show anything in IE except the default 404 page.
Tried clearing cache, clearing browser history, restarting computer, other things. I searched other similar problems with no luck.
Awesome, huh?
This is happening to me with a plain vanilla install of MODx 2.0.8 -- FURLs off.
I get My own error page fine in FF.
Both IE7 and Chrome give me the browser’s 404 page instead of my own.
I do get the unauthorized page for all browsers if the page is published and the (anonymous) user has "load only" permission for the resource group.
interesting
on Mac OS 10.6 your test page works in Safari 5 but does not work in Chrome - so its not just a IE thing
It does work in Opera 11, and Firefox 3.6.13 did not try iCab - getting lazy I guess
-
☆ A M B ☆
- 24,524 Posts
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.michaelfokken.com%2Fthis-page-does-not-exist;No200=1
Thank sottwell, I got the character encoding fixed.
It still does the same weird thing in IE, though. I tested it on IE 7 and it acts the same as IE 8.
Even cleared the cache, cookies, etc. in IE and on my site.
(I wish I could come here to help answer questions, instead of having to ask them. Sorry.)
-
☆ A M B ☆
- 24,524 Posts
I wasn’t referring to the character encoding, it was the fact that you aren’t using a doctype. Without a doctype, IE reverts to "quirks mode", and weird things can happen.
Sorry, that’s what I meant. But it still isn’t working right.
I got the same problem with subdomain (setup as a context). I can't get the error page working for my subdomain under FF and Explorer on Windows XP
Did someone find a answer or a solution for this problem?
Thank
While I was testing for the error page for my subdomain with Firefox on Windows, FireFox offered me an update, I accepted. I had version 4.01 of Firefox, now I have the latest version 6, and my error page works with this version.
If it can help someone, it only remains to find a solution for Internet Explorer...
Thank you