Just after installing node_registration I am getting some warnings.
I'm using PHP 5.3.8 and all my modules are current
I thought I just needed to associate a node_registration with a content_type but I then get 6 notices about line 165 of entity_views_field_definition.
Here are the warnings just after installing. The later warnings are repeats of the undefined index in line 165.
Notice: Undefined index: node_registration in field_info_instances() (line 687 of /Library/WebServer/Documents/drupal7/modules/field/field.info.inc).
Notice: Undefined index: label in entity_views_field_definition() (line 165 of /Library/WebServer/Documents/drupal7/sites/library.mskcc.org/modules/entity/views/entity.views.inc).
Notice: Undefined index: label in entity_views_field_definition() (line 165 of /Library/WebServer/Documents/drupal7/sites/library.mskcc.org/modules/entity/views/entity.views.inc).
Notice: Undefined index: label in entity_views_field_definition() (line 165 of /Library/WebServer/Documents/drupal7/sites/library.mskcc.org/modules/entity/views/entity.views.inc).
Comments
Comment #1
muzzye@mskcc.org commentedI also tried this with the dev version and am also getting these errors.
I'm also wondering if these notices would keep a user, or admin from registering for an event?
Just what is the register URL anyway; I surmised that it was node/%/register but all that shows is the drupal message 'You are not authorized to access that page'
Then I guess the question would be, how can I generate a register link when a user is viewing the content for the event/ content_type using node_registration.
Everything else seems to work and be pretty feature complete but I can't find anyway to get to a register page.
I've taken an existing Event content type (in my case a workshop) and configured it for node_registration at:
/structure/node_registration/manage/workshop_class/settings
I added a couple of fields at /structure/node_registration/manage/workshop_class/fields
I was given an option of both full registration and simple registration in /structure/node_registration/manage/workshop_class/display
Permissions have also been generously assigned so I don' think that is a problem.
Comment #2
alunadelamer commentedit happened to me, I couldn't see the register link anywhere and everything else worked fine, then I cleaned the cache and installed the devel module and then it just happened to work.
Comment #3
rudiedirkx commentedThe warnings aren't familiar, but I'm looking into them right now. There's nothing I hate more that a module creating PHP errors when enabled.
I'm starting with a clean, simple, default Drupal 7.13 installation.
Comment #4
rudiedirkx commentedI'm not getting any errors... When enabling Node registration, I also had to enable Entity API, Entity tokens and Value is (form element validators), so they enabled at the same time.
Now I'm trying with Entity API enabled before (since it is an entity thing).
Comment #5
rudiedirkx commentedStill nothing... Have enabled node types etc.
Comment #6
rudiedirkx commentedadmin/structure/types/manage/party/display/teaser)The URL is indeed
node/%/registerand obviously sufficient access is required. Some 6 factors apply. For debugging purposes you can add?debug=1to the URL (e.g.node/14/register?debug=1) and then check the Recent Log Messages. It should explain why you got the Access Denied.Comment #7
lipinponmala007 commentedMe too have the same issuse..but just before all these i had the following experience
when enabling the modules
Got An error
PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/planetek/includes/registry.inc on line 92, referer: something/admin/modules/list/confirm
i refreshed the page and it seemes it worked to enable the module
then our Notice came
I thought that the enabling of module may not be worked properly.. i tried a uapade.php run
there i got this error with white page
PHP Fatal error: Maximum execution time of 30 seconds exceeded in something/includes/registry.inc on line 132, referer: something/update.php?op=info.
i continued with the home page link
but the error/Noticed disappeared..Do not know what happened exactly.was not sure if the error is with node register module
Comment #8
rudiedirkx commentedIt's a combination of Entity, Views and Node registration. I might not see it because I'm using an 'old' version of Entity.
What version of entity.module are you using?
Comment #9
rudiedirkx commentedThe 3 'label' notices (in Entity) are fixed in beta4: http://drupal.org/node/1533584
I'm not sure this fixes the first notice though (in field_info_instances). Debugging appreciated =)
Comment #10
mortenp commentedSame here:
Warning: Illegal offset type in isset or empty in node_registration_type_load() (line 70 of ..../public_html/sites/all/modules/node_registration/includes/node_registration.entity.inc)
call_user_func_array('node_registration_type_load', Array) entity.controller.inc:675
Also seeing no way to register, there is no registration link on node view, even though it is visible in fields display for the node type.
node/%/register returns not found
node/%/register?debug=1 returns not found, and no messages in log
Comment #11
rudiedirkx commented@mediehuset Immediately after install? Flushing the cache once should do the trick. Enabling Node registration has a lot of effect on the menu router and entity cache etc. Maybe flushing the menu cache is enough.
Comment #12
rudiedirkx commentedComment #13
rootworkI got the same thing immediately upon installing, and got it again on flushing the cache. It's definitely still there in 1.4.
Comment #14
rootworkOh and just to clarify: I get it on every page.
Comment #15
rootworkAlso getting this when editing or viewing nodes for which registration is enabled:
Warning: Parameter 4 to node_registration_access() expected to be a reference, value given in module_invoke_all() (line 850 of /<siteroot>/includes/module.inc).Comment #16
rudiedirkx commentedIf you (know how to) fix it, I'll add it.
Comment #17
rudiedirkx commentedI'm trying again with dev (1.9+).
Comment #18
rudiedirkx commentedI can't reproduce any of it... Not anything in
node_registration_type_load()nor anything withnode_registration_access().I'd like to know how to reproduce this. Can I borrow anyone's database?
Comment #19
ikaros123 commentedIf you go to wwwroot\....\sites\all\modules\node_registration\includes\node_registration.entity.inc on line 71, you can change the code in this line to this -> ["{$bundle}"] , and the error "llegal offset in node_registration_type_load " goes away.
I think it may have something to do with trying to index an array with something that isn't an integer or possibly trying to index something that wasn't actually an array.
But I also cannot see tha register link, although I checked and it is visible in the field settings.
Comment #20
ikaros123 commentedI finally figured it out!
To get the registration link to be shown on a content type , the registration start date must be set to your current date. Otherwise it seems that the event is closed and no one can register for that event ...
Comment #21
rudiedirkx commentedNot seeing the registration link is due to one of many reasons. You can add ?debug=1 to the URL to add the reason to the logs table and watch that message on admin/reports/dblog.
But that's not this issue. This issue is about an offset notice in node_registration_type_load() that I can't reproduce. Need database or reproduction steps.
Comment #22
vrwired commentedI resolved the offset issue after reading the above by clearing out data I must of accidentally set earlier when testing. I imagine I deleted something related from entity_type table that caused this error to prompt when turning this node registration module back on just now.
To clear the date I temporarily edited node_registration/includes/node_registration.entity.inc
I set $bundlename = null right before checks isset, refreshed admin, errors went away, undid my mod, errors cleared out now...
Well looks like error came back - hmm
Comment #23
vrwired commentedI can send a copy of db for you...
On another note, I'm looking at DEVELOPERS.md for a better understanding of possible mods I need to make
Comment #24
rudiedirkx commentedI'd like the db, yes. You can do what I'd do yourself: catch the error and
dpmadebug_backtrace(). Only dpm if the error will occur (so check type). Add insidenode_registration_type_load():That will dpm a backtrace when the input argument isn't a string (like it's supposed to be) and that will allow you to track where it comes from. Who calls the function via what function etc?
Comment #25
yuriam commentedThis problem still exists; I have it too. The problem seems to be that the function node_registration_type_load does not receive a string as it expects, but an entire object. I have dumped this object, and the backtrace. As they are both quite huge I won't paste them here; instead, here it is.
I hope this is useful to you, rudiedirkx, and that you can fix the error.
Comment #26
yuriam commentedComment #27
rudiedirkx commentedI know that much, but I can't find out why.
The backtrace isn't useful. I'll need the whole tring, like
debug_backtrace()makes. And more formatted so it's readable.But since I've never been able to reproduce, I'm probably not going to search very hard... That's sucky for you, sorry, but I really can't find it. (Unless, maybe!, I have a good backtrace dump.)
If you can fix it, that would be best, of course ;)
Comment #28
rudiedirkx commented(Needs Review is for reviewing patches etc. This doesn't have a patch, so it's Active.)
Comment #29
yuriam commenteddebug_backtrace() then. I'd (and perhaps others) appreciate it if you looked at it!
Comment #30
rudiedirkx commentedDisable Entity Registration. You can't have Node Registration and Entity Registration enabled both.
Comment #31
yuriam commentedOh, d'oh. Thanks!
Comment #32
rudiedirkx commented