Beta-1 problems, can't edit new content types

Are you using the very latest version? I made several changes to it yesterday to fix problems with the menu tabs and I believe the final version is working right.

Hi,
I installed the newer version (November 2, 2006 - 08:16), but it still doesn't work.
you can check it here (and also administrate the 'content type').

Cheers,
Amitai

(using Drupal 5 beta 1)

If you updated the module, you also need to clear the menu cache to force it to regenerate correctly. That cache is now separate from the other caches. See if you still have a problem after that.

I am having exactly the same problem. Clean beta-1 install. CCK is the only module. Site is running MySQL 5.0 in version 4.0 compatablility mode. Latest version (Nov 1 Commit #44250) of CCK

One more thought--I'm not sure that the CCK module is even installing properly because there are no references to it in user management / access control and I would have thought there would be some kind of persmissions settings.

Let's take this one step at a time. I've done several clean installs with no problems, so there may be something about your installation that's different, so what are you using (mysql version, php version, etc.)? For anyone who tried to do this with an earlier version and then updated the module, let's just go back to a fresh install of the latest version and see if it still is a problem.

As to access control, the creation of content types is handled by the node module in 5.0, which sets up all the access control for those node types. CCK used to do this in 4.7 but doesn't need to in 5.0. In 5.0 CCK only manages fields, so you won't see anything about CCK in access control in 5.0 unless or until someone adds in capability for field-level access control.

I just tried another clean install myself (php 4, mysql 4.1) and everything works fine. I can create a new content type with any name and the field tabs are displayed and work, and I can add fields to both my new type and the existing types. I can't think of any reason why the mysql version would be a factor, but the php version might possibly be. If this is still a problem on a clean install, what php version are you using?

I just realized I'm using the latest cvs of Drupal rather than Beta-1 so I re-tested with beta-1 and had the same problem everyone else is reporting. Things work fine with latest cvs of Drupal, so something in Drupal core has changed that we need. I don't know what it is, though.

You need the latest cvs version of the node module rather than the one in beta-1. After updating that module, empty your caches (cache and cache_menu). Then it should work.

Hi KarenS,
* Do you mean I need to re-install the node module with the last CVS?
* Can you explain how to empty the cache and cache_menu?
Cheers,
Amitai

Go get the latest version of the node module from http://cvs.drupal.org/viewcvs/drupal/drupal/modules/node/ and put it in your installation to overwrite the one that came with beta-1. The important files are node.module and content_types.inc, the others don't matter and haven't changed.

Once you have replaced the files, empty the cache tables using phpmyadmin, if you have it. If you don't have a way to manually empty the cache tables, I'm not sure how you do it in 5.0. It used to work to go to the modules page and save it, but I'm not sure that works in 5.0.

Actually, it's the menu cache that needs to be cleared, so going to the menu page and saving it should clear the menu cache if you don't have any other way to do it.

Yo,
I got some problems on the node.module installation… Here are my steps
* In this link
* download node.module and content_types.inc
* I copy those file to http://***my site***/modules/node/
* When I go back to my site I get the CVS page, and not my site.

What am I doing wrong in this process?
Maybe I copied the wrong files? Can you send a link to the correct files?

Thank you for your help!
Amitai

Those are the right files but it sounds like you copied the link to the cvs page instead of the files themselves. You need to follow the link until you get to each of the files that you need, and then download the files and place them on your site.

Works like a charm :)

This is fixed by overwriting the node module in beta-1 with the current cvs version of the node module, or by using the current cvs version of Drupal. I'm going to leave this issue open because others are going to have this problem and I want them to be able to find this solution. If I had access to the project page, I'd add a message above the issue submission form, but I don't.

I better change this from being a critical bug report or it's going to look like there's something that needs to be fixed.

Bumping this to keep it on top of the list so people don't keep re-reporting it.

Bump again.

Now that Beta-2 is out, I think it's safe to close this issue.