Frog CMS - Page not found [Plugin]

FORUMS CLOSED DUE TO SPAM. YOU STILL CAN ADD POST!

Page not found [Plugin]

5 posts, 5 voices

Dec 16, 2007 12:31 vitormcosta 11 posts	I am trying to create a 404 page with the page_not_found plugin Revision 89: / from svn but i'm getting the following error: Fatal error: Call to undefined function statistic_save() in /Users/~/Sites/madebyfrogs-read-only/frog/plugins/page_not_found/index.php on line 29 Does anyone have the same issue? Thanks

Dec 16, 2007 16:12 David 1493 posts	Here's what I did: Read the "readme.txt" with the `page-not-found` plug-in. Created a page as a `child` to "Home" called "Page not found" Set the Layout = "inherit"; Page type = "Page not found"; Status = hidden. Put a little text in the page with no filter set. Saved it. Put a nonsense page on the address line, and... Got this error message: `Fatal error: Call to undefined function statistic_save() in C:\Program Files\xampp\htdocs\frog4\frog\plugins\page_not_found\index.php on line 29` Line 29 = `statistic_save($page->id);` in case that's any help to ... Philippe. ;)

Dec 16, 2007 20:31 philippe 541 posts	sorry about that !!! copy past done too fast ;) bug fixed in the svn!

Dec 17, 2007 14:59 David 1493 posts	Thanks, Philippe -- that works great! (And now that I've worked out how to use SVN, it is super easy to grab the latest file! :)

Aug 29, 2008 19:50 BcHoward 1 posts	I am still not having any luck after doing all of the above. I have checked out the latest from Subversion (rev.205) through SSH to the hosting server. Any ideas? Here is the error? "Not Found The requested URL /cgi-bin/php/index.php was not found on this server. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request." The plugin works fine on my local server on OS X. I can't seem to figure out what the host is doing differently to cause the error.

Aug 30, 2008 14:31 Martijn (mvdkleijn) 651 posts	Try turning on the debug option in Frog's config.php.... if you have access to the http server's error logfile, that would probably help in trying to determine the cause of the problem.