After a recent update form 1.8.4 to 1.8.6 Build 20081008 the forums are now producing blank pages when the Post to Forum button is pressed. It looks like it no longer knows where to return.
Also when editing almost anything the editor at first returns and tells you the field you just entered is required. Then, you hit Save and it take the input. You just have to do it twice.
There were no error reported in the upgrade and with debug set to ALL no errors are reported on the screen or on the logs.
Anyone else having this problem? Anyone know what went wrong? Better yet, how to fix it?
Thanks
This may be completely unrelated, but it might be worth trying. Take a look at the solution for this discussion http://moodle.org/mod/forum/discuss.php?d=107067
Thanks for the suggestion.
Perhaps a better description of the problem would help.
After the upgrade, anyone making a post to any forum would proceed as normal up until they hit the 'Post to Forum' button. Then
the screen goes blank and the url showing is "http//[your host name]/mod/forum/post.php". The 'continue' page that would normally show up, the one that tells you that you have 30 minutes to edit your post, does not show up. The page just stays blank.
The user would then navigate back to the course and back to the forum and their post would show up like normal.
I found where the problem was. The file /mod/forum/post.php has been updated. The updates did not work for our sites.
I swapped out the new post.php file with the old post.php and and every thing worked. This should be a concern for anyone thinking of upgrading to 1.8.7. Since the security warnings went out, I'm sure many are thinking of upgrading.
We have not detected any problems switching back to the version 1.134.2.14 of the post.php file.
Here is a 'diff' output for the post.php file.
1c1
< <?php // $Id: post.php,v 1.134.2.15 2008-10-07 08:11:47 scyrma Exp $
---
> <?php // $Id: post.php,v 1.134.2.14 2008-01-28 03:22:41 moodler Exp $
517c517
< if ($subscribemessage = forum_post_subscription($fromform, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($fromform)) {
547c547
< if ($subscribemessage = forum_post_subscription($fromform, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($fromform)) {
607c607
< if ($subscribemessage = forum_post_subscription($discussion, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($discussion)) {
Perhaps a better description of the problem would help.
After the upgrade, anyone making a post to any forum would proceed as normal up until they hit the 'Post to Forum' button. Then
the screen goes blank and the url showing is "http//[your host name]/mod/forum/post.php". The 'continue' page that would normally show up, the one that tells you that you have 30 minutes to edit your post, does not show up. The page just stays blank.
The user would then navigate back to the course and back to the forum and their post would show up like normal.
I found where the problem was. The file /mod/forum/post.php has been updated. The updates did not work for our sites.
I swapped out the new post.php file with the old post.php and and every thing worked. This should be a concern for anyone thinking of upgrading to 1.8.7. Since the security warnings went out, I'm sure many are thinking of upgrading.
We have not detected any problems switching back to the version 1.134.2.14 of the post.php file.
Here is a 'diff' output for the post.php file.
1c1
< <?php // $Id: post.php,v 1.134.2.15 2008-10-07 08:11:47 scyrma Exp $
---
> <?php // $Id: post.php,v 1.134.2.14 2008-01-28 03:22:41 moodler Exp $
517c517
< if ($subscribemessage = forum_post_subscription($fromform, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($fromform)) {
547c547
< if ($subscribemessage = forum_post_subscription($fromform, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($fromform)) {
607c607
< if ($subscribemessage = forum_post_subscription($discussion, $forum)) {
---
> if ($subscribemessage = forum_post_subscription($discussion)) {
Hmm ... something is wierd ... I'm not sure you have a correct copy of the code.
Alex can you go to
Admin > Server > Debugging
And turn "debug" level to DEBUG_DEVELOPER and make sure debugdisplay is on.
Then visit the forum again and see what errors you get. Please follow up in MDL-16925
Alex can you go to
Admin > Server > Debugging
And turn "debug" level to DEBUG_DEVELOPER and make sure debugdisplay is on.
Then visit the forum again and see what errors you get. Please follow up in MDL-16925