-
Notifications
You must be signed in to change notification settings - Fork 68
emaillog.php returns no data #7
Comments
I have had a discussion on this with our programmer. He went and searched for what was causing the net error. He found that in the function "list_entries" in "lib.php" something is amiss. It is using a function what is supported only in 5.3.8 and not in our installed 5.3.6. By upgrading PHP we fixed the problems we were having. |
To elaborate on this issue... I would suggest adding a notification for users to use 5.3.8 :). |
@LCHEB, ha, thanks for that. I would have never guess that anonymous function behavior would change between versions, and it actually saddens me to think a language would. At any rate, I think the safest solution here would be to replace the problematic anonymous function with code that is not wrapped in an anonymous function, as I don't think it is right for the Quickmail module to require any other version of PHP than Moodle's required version. I'm looking into that right now. |
This discussion can now be moved to issue #8. Thank you everyone for bringing this to our attention. |
I am running 2.1.2 (20111019) and the block installed fine. This is an older website that has been through several upgrades. Before installing I made sure that all references to quickmail were removed from the codebase and the database. With the latest build available from the official moodle plugin database I have one major error; on the emaillog.php page it returns no data. Whether I want to check for drafts, or the history of messages in general.
The browser displays a (net::ERR_EMPTY_RESPONSE). Our client has informed me that on your clean 2.1.2 installation the module runs fine; without the server closing the connection on the emaillog.php page. The biggest hint I could figure out is that I don't see the emaillog.php requests in webservers acces logs. Though, I made sure all the directory rights and ownerships were set properly.
I am wondering what could be wrong with our setup and/or with the module. I hope we can work together towards a solution so that we can provide a bigger knowledgebase to other users of this block running into this issue.
The text was updated successfully, but these errors were encountered: