Actually this might be:

  1. node registration issue,
  2. core issue,
  3. my ISP issue,
  4. collision with other modules issue,

but I got it while enabling this module so I'm reporting this here.

Enabling module coses in my case:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, admin@example.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

I've checked server log and I get:

Premature end of script headers: index.php, referer: http://example.com/admin/modules

In my php.ini there is:

register_globals = 0

memory_limit = 500M
max_execution_time = 320

so I have plenty of room and execution time.

I've tried to remove module completely (even with dropping tables ans system rows) and reinstall it - same result so it is deterministic and repetitive in my case. I don't know where to find some indication how to deal with it.

Check points:

@1) No idea
@2) No idea
@3) I've made some clean installation on the same server to check this module and it works with fresh D7(12).
@4) On my site, where I wish to enable this great module there is a lot of modules installed:

  • AddToAny
  • Administration Development tools
  • Administration menu Toolbar style
  • Administration menu
  • Administration views
  • Aggregator
  • Automatic Nodetitles
  • Better Formats
  • Block
  • Blog
  • Book
  • Calendar
  • Chaos Tools (CTools) Plugin Example
  • Chaos tools
  • Color
  • Comment
  • Computed Field
  • Contact
  • Context layouts
  • Context UI
  • Context
  • Contextual links
  • Dashboard
  • Database logging
  • Database search
  • Date All Day
  • Date API
  • Date Context
  • Date Migration Example
  • Date Migration
  • Date Popup
  • Date Views
  • Date
  • Devel
  • Email
  • Entity API
  • Entity Reference
  • Entity tokens
  • Field collection
  • Field extract
  • Field Permissions
  • Field SQL storage
  • Field UI
  • Field
  • Fieldgroup
  • File Field Sources
  • File
  • Filter permissions
  • Filter
  • Flag actions
  • Flag
  • Follow
  • Form builder examples
  • Form builder
  • Forum
  • GMap Location
  • GZ form Addition
  • Help
  • Hierarchical Select Taxonomy
  • Hierarchical Select
  • Image
  • Imagecache Actions
  • Imagecache Canvas Actions
  • Imagecache Color Actions
  • IMCE Wysiwyg API bridge
  • IMCE
  • jQuery plugins
  • jQuery Update
  • Libraries
  • List
  • Locale
  • Menu
  • Module filter
  • Node clone
  • Node registration
  • Node
  • Number
  • Options element
  • Options
  • Path
  • Pathauto
  • Prepopulate
  • RDF
  • Rules translation
  • Rules UI
  • Rules
  • Search API
  • Search
  • Serial
  • Simplenews
  • Superfish
  • System
  • Taxonomy
  • Text
  • Token
  • Transliteration
  • Trigger
  • Unique Field
  • Update manager
  • User Import Framework
  • User
  • Value is (form element validators)
  • Viewfield
  • Views jQfx
  • Views jQFX: Cycle
  • Views jQfx: Galleria
  • Views jQFX: Imageflow
  • Views Nivo Slider
  • Views PHP
  • Views Slideshow
  • Views Slideshow: Cycle
  • Views UI
  • Views
  • Wysiwyg

Comments

rudiedirkx’s picture

rudiedirkx commented

Premature end of script headers: index.php sounds like a server issue... I've never seen it before.

  • When does this happen? When enabling the module?
  • And after that: is it enabled and are the tables (2) created?
  • If the tables are created and the module is enabled, does it work or do you get that error every request?
  • Does it happen for all pages, only admin pages or very specific (node registration?) pages?

I've never seen it, so I'm not sure I can be of much help... What will help for debugging: set your error_reporting to E_ALL and display_errors to 1 (in php.ini or a .htaccess or something).

AndreasST’s picture

AndreasST commented

I'm using Node Registration 7.x-1.1-beta3

I get a similar error when enabling the module.
Premature end of script headers: php5.3, referer: http://dp7.domain.tld/admin/modules
Ending in a server error 500.
It looks like the module is enabled after this.

Same error when running update script - also ending in server error 500.
Premature end of script headers: php5.3, referer: http://dp7.domain.tld/update.php?op=info

In Drupal-Log there are more than 800 entries with the same error after one run of the update script.
Notice: Undefined property: stdClass::$old_type in node_registration_node_type_update() (Zeile 631 von /home/www.domain.tld/dp7/sites/all/modules/node_registration/node_registration.module).

nfavrod’s picture

nfavrod commented

Hello,
I got the same issue as #2 : Notice: Undefined property: stdClass::$old_type in node_registration_node_type_update() (line 600 in modules/node_registration/node_registration.module)

I use node_registration 7.x-1.1-beta2

it happened when I tried to enable a new module :
EMPLACEMENT http://mylocal.domain/admin/modules/list/confirm
RÉFÉRENT http://mylocaldomain/admin/modules
(sorry in french emplacement and référence, means going to and page from probably)

It caused an infinite loop in httpd...

nfavrod’s picture

nfavrod commented

Hi,

I investigate a little : it seems that the $info->old_type of Content Type that have not been activated with node_registration have no value. The hook is called on a content type that have never been node_registration enabled...

In the hook, there's a drupal_flush_all_cache(), that cause the hook_node_type_update() to be called again, starting an infinite loop...

I added a condition to check (isset($info->old_type). if not, it skip all the update.

That solve temporarily the problem, cause behind : why is my content type "XYZ" called in the node_registration_node_type_update(), instead of the right one?

rudiedirkx’s picture

rudiedirkx commented

I've fixed the old_type bug in hook_node_type_update, but I'm not sure that fixes the weird "Premature end of script headers" error.

beta5: http://drupal.org/node/1533596

@nfavrod What do you mean with

why is my content type "XYZ" called in the node_registration_node_type_update(), instead of the right one?

? Do you wonder why that hook is called? Or do you think it calls the hook for a wrong node type?

achikas’s picture

achikas commented

same here.

drush says on drupal-7.12:

node_registration is incompatible with the Drupal version.

what da heck?!?

rudiedirkx’s picture

rudiedirkx commented

Maybe because you're not running PHP > 5.3. Node registration requires 5.3.

Come on guys. PHP 5.4 has been out for a few months. 5.3 has been for years. 5.2 isn't even supported anymore!

AND GOD SAID: UPGRADE THY SERVERS!

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@rudiedirkx: That may be a valid point, but Drupal 7 only requires PHP 5.2 and that will not change.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Ah, does look like you added http://drupalcode.org/project/node_registration.git/commit/96ce242 and is set in the latest release. Probably at the time of 7.x-1.1-beta2 (when this issue was filed) the PHP restriction was not set in the .info file?

rudiedirkx’s picture

rudiedirkx commented

Yes, that's possible. It wasn't always in there. (Definitely after beta1.)

Did you happen to come across the "Premature end of script headers" error too? I don't understand (and can't reproduce) that one.

rudiedirkx’s picture

rudiedirkx commented
Status: Active » Closed (cannot reproduce)