Closed (fixed)
Project:
Coder
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 May 2011 at 19:04 UTC
Updated:
8 Jun 2012 at 09:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
solotandem commentedBased on the information you provide, why is this automatically an issue with Coder? A web search for that error string would suggest a firewall or security software as being the cause?
Comment #2
kd8fre commentedSolotandem,
If i remove the coder module files, everything works. If I put them back, it does not. This is a local server, only accessing from the machine the server is on, so Firewall is not a problem.
Russ
Comment #3
solotandem commentedLet's explore, "I have made sure I am meeting all of the dependencies of the module, still no difference." What are the dependencies you have met? Be specific, possibly include a screen shot of the modules page for the coder related modules. Does your web server have write access to appropriate files directories?
Comment #4
kd8fre commentedSolotandem:
These are the dependencies I have met:
The 7.x branch requires:
the Grammar Parser (as a library, not "enabled" as a module)
the Grammar Parser Library
the Libraries API (2.x-dev)
Russ
Comment #5
solotandem commentedThe code dependencies appear to be met. Thanks.
Still, the error message suggests a site configuration problem, which seems unlikely to be caused by enabling a module.
Are there messages in the Apache logs when you try to access the site with Coder enabled? Have you enabled other contributed modules, added content, etc.?
Comment #6
kd8fre commentedsolotandem:
Once i upload the files, the site breaks, before I am even able to enable it.
Here is the portion created in the Apache error log:
And in the Apache Access Log:
Thanks for the help with this.
Russ
Comment #7
solotandem commentedDo a web search on "[notice] Parent: child process exited with status 255 -- Restarting". You will find some interesting stuff related to WAMP. Things like out of memory, PDO issues, etc.
If you don't find something quickly, you could try outputting more debug information from Apache to see if it will tell you what is causing the restart.
You claim, "Once i upload the files, the site breaks, before I am even able to enable it." This, again, does not suggest a problem with Coder (it is not even enabled so Drupal should not be invoking any of its code).
Changing issue status until you can provide definitive evidence that Coder is the cause.
Comment #8
kd8fre commentedsolotandem:
I will attempt the Google search you specified.
The reason that I am fairly sure it is coder, is if I place the files in the modules directory, bam, site broken. If i remove the files from the module directory, site fixed.
I am able to add other modules just fine.
Russ
Comment #9
kd8fre commentedIt is only the /admin portion of the site that breaks, not the regular (user viewable) portion.
Russ
Comment #10
solotandem commentedIs Grammar Parser placed in the "libraries" directory? Hop on IRC sometime and let's see if we can't figure this out. Or Skype with screen share.
Comment #11
kd8fre commentedsolotandem:
I am usually around #drupal-support. I do have the ability to do screensharing. I will most likely be on IRC tomorrow after 9am eastern. I have the same nick there as I do here.
Thanks again for the help.
I did get my issue that I wanted the module for figured out elsewhere, but I would like to know what the problem is now.
Russ
Comment #12
kd8fre commentedI'm Changing status on this as I will be out of town for some time.
Thanks for the attempts at help. Hopefully I will get it figured out and post back.
Russ
Comment #13
kd8fre commentedSeems to have been a strange WAMP issue.
Now have it working. Thanks for the help.
Russ
Comment #14
robidigital commentedAny way you might be able to post what the issue was so that others like myself can troubleshoot our same issue?
Thanks
Comment #15
kd8fre commentedrobidigital,
I ended up having to reinstall WAMP, for another non-drupal reason, and that fixed it. Not sure if it was just a bad WAMP install or what.
Russ
Comment #16
odegard commentedI am experiencing the same thing.
By trial and error (deleting files, then commenting out parts of the offending file) I managed to narrow it down to.... (drumroll)... the length of the description in coder_upgrade.info, but only if it is wrapped in double quotes!
Here are all my findings, they are bizarre...
* Removing the double quotes, works
* Keeping the double quotes but concatenating the three description lines into one, works
* REDUCING the length of the double quotes description to under 190 bytes, WORKS
It's the weirdest thing... I edited the .info file of a random module adding words to the description field. If number of bytes of the description inside the quotes is 189 or less... it works. Adding a single letter breaks the modules page. Again, removing the double quotes unbreaks it.
My guess is that it's something about how WAMP configures apache or php, but this is out of my area of expertise. If anyone else has some input, please share.
If this is the case, we probably should consider giving notice in the writing .info files page (http://drupal.org/node/542202) where it says "Quoted values may contain newlines."
Comment #17
rennevat commentedodegard, thank you for sharing your solution. We experienced the same "The connection to the server was reset while the page was loading" issue on all admin pages immediately after downloading Mass Contact module to local WAMP server. Editing the .info file to reduce the description to a single line immediately fixed the problem. Again, many thanks.
Comment #18
favosys commentedI just ran into the same problem, thankfully I found this page.
If this is a known issue and we have the solution, why isn't fixed? You might say it's a WAMP problem but how many people use WAMP? I'll tell you, a lot of people. Do you really want every person who uses WAMP to get their site broken just by copying it in the modules folder? You know what the problem is, just fix it.
Comment #19
solotandem commentedThe issue with WAMP was addressed in #1277726: coder_upgrade.info bug on Windows systems and a commit was made. Are you running the latest development release as recommended on the Coder project page? If you are, then you shouldn't have the problem.
Comment #20
Misura commentedDoes anybody know how to fix the issue with WAMP? I understand the issue with Coder is fixed with the newest release but other modules have the same issue with WAMP and it is suppppper annoying!
What is it with the line breaks in the .info files, etc?
If anybody knows how to fix it, you are a god to me lol
Comment #21
ANDiTKO commentedI had the same problem in WAMP. I had the stable version of the coder module.
Upgrading to the dev version fixed this problem.
Comment #22
lmeister commentedReal cause and proper fix here. This is not a coder problem but a WAMP setup issue:
http://drupal.org/node/1597820#comment-6094060