Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I tested EntityForms 2.0 beta 2 on a completely freah and clean Drupal 7.24 with only the latest modules required to run Entityform. No other unneccessary modules are installed for a complete and clean testing. I tried to remove the date field in an entityforms type and then all EntityForms Type are no longer workable anymore with page not found.
Page not found
The requested page "/drupal724/eform/submit/wulala" could not be found.
Comment | File | Size | Author |
---|---|---|---|
wulala.PNG | 3.71 KB | jetwodru |
Comments
Comment #1
detroz CreditAttribution: detroz commentedI have the same problem but it happened when I updated the module and deleted a list (text).
Change a previous submission is ok but not creation.
Comment #2
animaluksmall CreditAttribution: animaluksmall commentedDrupal 7.24
Same issue here, deleted an entity form now all remaining forms display 'Page not found'
Same results in administration view when accessing the 'submission link'
After creating a new entity form or cloning same results as above.
Comment #3
detroz CreditAttribution: detroz commentedHi,
I've another mistake : the form is visibled for anonymous users but not for the connected users.
After search, I commented the conditionnal block "if (empty($empty_entityform))" of the function function entityform_empty_load($type). Now, my entity form is visibled for anonymous and connected users.
If it can help, the creation of the entity form is sometimes empty for connected users. But I don't know why...
Comment #4
tedbowThere is a patch here: https://drupal.org/comment/8439491#comment-8439491
That might solve this problem. Please try this patch and let me know if it fixes that issue.
Thanks
Comment #5
detroz CreditAttribution: detroz commentedHi,
The patch doesn't fixe this issue.
"Page not found" is coming for function "entityform_empty_load($type)".
The entityform isn't created. But if I comment the conditionnal block "if (empty($empty_entityform))", the entityform is showed !?
Another strange thing, anonymous users see the form and connected users a page not found.
Maybe it's because we deleted an entity submission or and the module cannot build the list of submited forms for this user... but why ?
Comment #6
gbirch CreditAttribution: gbirch commentedI see a patch to entityform_get_types for the 7.1 branch here: https://drupal.org/comment/8171495#comment-8171495
tedbow's comment notes "Ok this was being caused by logic in entityform_get_types that never got a fix that was put into 2.x."
But when I look at entityform_get_types() in the 7.2 -beta2 code, it appears to be the same as the 7.14 code -- i.e. if there's a logic error in 7.1, the same logic error is in 7.2. Inadvertent regression?
Could this be the underlying problem, rather than the cache?
Comment #7
gbirch CreditAttribution: gbirch commented1. My last comment was wrong, or it was at least not my problem.
2. As noted above, I too have the problem where I try to open an entityform and get BOTH Page Not Found AND the form. I have found one possible answer and fix, which worked for me.
After I deleted a number of entityforms, their entries were not removed from Drupal's menu_links table (I have not tracked down why this is so, and presumably this would be a good bug to fix). The short answer is that you can fix the bug by manually deleting the bad entries from the menu_links table.
For what it's worth, what happens is that Drupal iterates over all of the menu_links relevant to any menu on the page. In my case, this caused it to iterate over the deleted entity forms, calling entityform.module/entityform_empty_load() with the name of each deleted form. Upon hitting the first of these, entityform_empty_load() triggered drupal_not_found(), even though the actual form had already been rendered and sent for delivery. I suspect that entityform_empty_load() should simply return FALSE to _menu_load_objects() when presented with a bad form name (instead of triggering a not found and returning NULL), but have not tested.
Whew.
Comment #8
sandrajhall CreditAttribution: sandrajhall commentedI have the same problem as #7 and the manual fix worked for me. Thanks for saving me a lot of hair pulling!
Comment #9
PaulDinelle CreditAttribution: PaulDinelle commentedI made a patch for this issue and posted it in the thread about changing the machine name:
All Pages Not Found after renaming a Form's Machine Name
Comment #10
tedbow