This page is part of the BugReports series. Please go there to submit a new bug or to see the list of all existing reports.

mpi_insert bug

*UrsHunkler: As you can see on *InsertTestPage in this ewiki after the 4th insert the error message "Redirection loop detected Operation stopped, because we're traped in an infinite redirection loop with page ..." is printed. how comes? i didn't find nothing about insert limits in the docu.

-- *UrsHunkler 2004-09-30

MarioSalzer: Seen it. Funny example.

It is there to prevent that somebody accidently inserts the one page in itself (which could end in an infinite loop). Suddenly it uses a plain stupid counter for that, which doesn't really detect loops (the simplest prevention I could come up with).

If you need more inserts in a page, you can simply kill that code from it. Right now, I don't have any better idea to safeguard against the loops I fear so much.

*UrsHunkler: one idea - define a counter in the config one can set to the maximum of inserted pages needed. can you please give me some hints how to do this and which files are involved? Thank you.

-- *UrsHunkler 2004-10-03

MarioSalzer: Making the actual max number configurable isn't such a big deal IMO. It uses the $_REQUEST[EWIKI_UP_REDIRECT_COUNT] global var I think. The number was hard-coded in plugins/jump and mpi/mpi_insert, but I'll add an constant for that.

*UrsHunkler: in plugins/jump you wrote

20: define("EWIKI_UP_REDIRECT_COUNT", "redir");

I don't understand how you use the constant.

-- *UrsHunkler 2004-10-04

MarioSalzer: The constant isn't important here as I found out. Your problem lies fully within plugins/jump.php. You must currently change the line containing "static $redirect_count = 5;" to get over this error. I'll add a configurable constant for that later.

Seems like this snippet of the jump plugin gets activated always and decreases the jump counter (originally only meant for stopping external link loops). I left in this side effect, because it is actually useful for the insert plugin (to prevent loops in there, too); though in reality it is only a workaround - the insert plugin should better have its own loop protection...