OESF Portables Forum

Everything Else => OESF Wiki => Topic started by: mars on March 30, 2009, 09:03:04 pm

Title: Error Accessing "playing With Python" Page
Post by: mars on March 30, 2009, 09:03:04 pm
I was perusing the OESF wiki, and noticed that the "Playing with Python" page has an error when I tried to access it:

https://www.oesf.org/index.php?title=Playing_with_Python (https://www.oesf.org/index.php?title=Playing_with_Python)

Precondition Failed

The precondition on the request for the URL /index.php evaluated to false.
Apache/2 Server at www.oesf.org Port 80
Title: Error Accessing "playing With Python" Page
Post by: Meyer on April 14, 2009, 11:15:40 am
We've encountered a similar problem (https://www.oesf.org/forum/index.php?showtopic=26150) before. It seems that certain article text sequences (a three-period ellipsis) cause the PHP interpreter to barf. I've tried editing the page in question and replacing the ellipses with &hellip entities, but the page is still generating errors. However, the page is displayable if you enter via the revision history page: https://www.oesf.org/index.php?title=Playin...amp;oldid=11024 (https://www.oesf.org/index.php?title=Playing_with_Python&oldid=11024). Check it out.

I will keep this problem in mind, but it's hard to tell when I'll have time to do the research to really solve it.
Title: Error Accessing "playing With Python" Page
Post by: tux on March 31, 2011, 05:08:03 pm
Quote from: Meyer
We've encountered a similar problem (https://www.oesf.org/forum/index.php?showtopic=26150) before. It seems that certain article text sequences (a three-period ellipsis) cause the PHP interpreter to barf. I've tried editing the page in question and replacing the ellipses with &hellip entities, but the page is still generating errors. However, the page is displayable if you enter via the revision history page: https://www.oesf.org/index.php?title=Playin...amp;oldid=11024 (https://www.oesf.org/index.php?title=Playing_with_Python&oldid=11024). Check it out.

I will keep this problem in mind, but it's hard to tell when I'll have time to do the research to really solve it.

The page is now accessible without needing any tricks....