7.7 upgrade unable to add/node

related: #1233092: can't add nodes / any content type?

Bumping this to critical until we can rule out core, two separate bug reports suggests it's not a one-off.

Marked #1233092: can't add nodes / any content type as duplicate.

We need more information though..

Which contrib modules do you have installed? Is Entity module one of them?

Is this the node/add/content_type page you're getting the error? Or immediately after posting a node?

Could you install devel module or similar and post the output of debug(entity_get_info()) or similar?

Do the other nodes on your site load OK - is it just the form that's broken?

also see http://drupal.org/node/1233092 im having the same or a similar issue

that's going to be another registry_rebuild issue then.

Yeah that seems likely, I'm marking this needs more info.

If you're running into this, please provide the following:

1. List of modules enabled.
2. Did you upgrade any modules when you upgraded core?
3. If you have the problem, does saving the modules page, or clearing all caches from admin/config/development/performance fix it?
4. If not, does http://drupal.org/project/registry_rebuild help fix it?

edit: if the answer to #3 or #4 is 'yes', this should be marked as duplicate of #534594: [meta] system info cache writing and registry rebuilding is broken without a full bootstrap.

I tried disabling then renenabling modules that hasn't worked.

1 - modules in use:

cck 7.x-2.x-dev
Chaos tools 7.x-1.0-beta1
Devel 7.x-1.2
AudioField 7.x-1.0-beta3
SMTP Authentication Support 7.x-1.x-dev
Advanced help 7.x-1.0-beta1
AntiSpam 7.x-1.1
Backup and Migrate 7.x-2.2
Views 7.x-3.0-rc1

2 - I upgraded audiofield, smtp auth, views and backup / migrate during the upgrade.

3- Tried with no help

4 - Will try

reg rebuilt

DRUPAL_ROOT is E:\inetpub\wwwroot\degimedia 2011 d7.
Bootstrapping to DRUPAL_BOOTSTRAP_SESSION
Doing registry_rebuild() in DRUPAL_BOOTSTRAP_SESSION
Bootstrapping to DRUPAL_BOOTSTRAP_FULL
Doing registry_rebuild() in DRUPAL_BOOTSTRAP_FULL
Flushing all caches
There were 420 files in the registry before and 420 files now.
If you don't see any crazy fatal errors, your registry has been rebuilt.

Cleared cache's but still no go.

when I create a new test content type, it shows up in the menu. but none of the defaults do.

@captaingeek. What do you mean by defaults?

Could you attach an SQL dump of your content types table to this issue?

@captaingeek I noticed you added an sql dump to #1233092: can't add nodes / any content type, that is definitely a different issue to the one here, see my questions on that issue.

Moving this back to needs more info again.

FYI, I added the following line after line 7486 in includes/common.inc to see what was causing the problem.

echo $entity_type;

That pointed to one of the wysiwyg modules being the culprit. I went to module admin, disabled the wysiwyg modules (wysiwyg and wysiwyg imce), the add page started working. Then I re-enabled the two modules and things seem to be back to normal.

fixed my issue by http://drupal.org/node/613292 not sure of cause

I was also experiencing this while running tests via drush after upgrading to 7.7, it was occuring when enabling a feature export of the content types on the site.

Oddly enough, moving the node/add/* menu item for that content type out of the navigation menu and into the administration menu did indeed result in a passing test as suggested for the actual node/add fix by 613292.

I can post a full log/dump if interested, but I have just such a hard time believing that could have really been the problem, more likely just a fluke.

Per http://drupal.org/node/613292 it seems this may happen on certain installs if the menu items for the Create Content items are disabled.

After over a year of inactivity I'm demoting this. If someone can provide steps to reproduce this we'll be happy to examine it in more detail and adjust the priority as appropriate.

Wow, D8 has come quite far, I can't even install now due to the minimum requirements of PHP 5.3.x, I'll have to get a new VM going before I can try to make some steps to reproduce.

(Merging "node system" and "node.module" components for 8.x; disregard.)

This is a genuine D7 bug. Not one I expect to be fixed though...