[RESOLVED] ERROR: Too many forward attempts!

Hello,
I have just finished install 0.9.6. if I try to go http://ns25227.ovh.net/~lugthudi/ I have this msg:
ERROR: Too many forward attempts!

The request could not be completed due to too many unsuccessful forward attempts.

If I go into manager There is no problem?
Could you help?

Best regards

First, make sure you have an error page (and unauthorized page) that is published, accessible, and executes without fatal errors. The manager should warn you of this when you first login and are directed to the Home view.

Quote from: OpenGeek at May 30, 2007, 12:23 PM

First, make sure you have an error page (and unauthorized page) that is published, accessible, and executes without fatal errors. The manager should warn you of this when you first login and are directed to the Home view.

Well I have no error page and unauthorized page; the manager warm me about this but I have no idea how to create these pages and where to put them.

Best regards. and thank you for your fast responce

For the time being, enter the same number as your site start page.

Both of those pages are merely site documents (preferably not shown in main menu) you need to create. They can have any content you want as long as they are set Published and public accessible.

Then go to the top menu "Tools/configuration" and on the first tab you see (Site), set the Error Page and Unauthorized Page with the corresponding document id’s (which is in brackets beside the document in the tree in the left frame.

Which makes me think... shouldn’t we set this as default config (have the site start as default error and unauthorized page) ?
Could help prevent those situations...

Thank you everybody.
I have created 2 new pages and assign their ID to error and unauthorized pages; it Works. By the way I had try before to put ID 1 but it is not works.
Best regards.

I just had a big problem with this error on version 1.0.2 (Evolution)
It is generated in the document.parser.class.inc.php in the following function:

(line 110 in that file)

Looking at the function I notice that the original responceCode is
not shown. Therefore I changed the ’die’ command to include the original
responseCode and ID the function wanted to forward to.


To make this reply complete:
I had a "Not Found" and ID was empty.
It appeared that the config was not read.
Tracking back that error I made the mistake of upgrading to 1.0.2 by copying
everything including the siteCache. The siteCache had wrong settings and therefore
the document parser could not find the right files.
Solution was to manually delete the files, go into Manager, change something, Save document,
and clear cache. Then a new cache is created and everything working.

An upgrade install should have cleared the cache for you.