On a normal site when I go to
http://xxx.org/admin/content/types/audio
I see the links:
# Edit # Manage fields # Display fields # Add field # Add group
Or something like that, depending on which CCK modules I have. However, I have a 'broken' site that shows:
* List * Add content type * Fields * Export * Import
which is more like what I would expect to see at the URL
http://xxx.org/admin/content/types
On the 'broken' site I indeed see those same links on /admin/content/types
CCK (5.x-1.6-1) is of course enabled, but this site has a LOT of modules, including one custom one. This is what CCK says:
Required by: Asset Manager (disabled), Content Copy (enabled), Content Taxonomy (enabled), Content Taxonomy ActiveSelect (enabled), Content Taxonomy Autocomplete (enabled), Content Taxonomy Options (enabled), Date (enabled), Date Copy (enabled), EMail (enabled), Fieldgroup (enabled), Image (enabled), Node Reference (enabled), Number (enabled), Option Widgets (enabled), Text (enabled), User Reference (enabled)
I would think that next debugging step would be to disable CCK, but that requires disabling all those required mods. I am a bit concerned, however, that if I disable them, something may happen to our data.
Any advice as to how to proceed? This is not my site--I just inherited it and need to work on it.
I suppose I will make a backup and do my debugging idea, but if anyone has another idea, let me know. :)
Thanks!
Quoting Fred Jones fredthejonester@gmail.com:
I would think that next debugging step would be to disable CCK, but that requires disabling all those required mods. I am a bit concerned, however, that if I disable them, something may happen to our data.
Any advice as to how to proceed? This is not my site--I just inherited it and need to work on it.
I suppose I will make a backup and do my debugging idea, but if anyone has another idea, let me know. :)
You didn't give the Drupal version. I would start with the backup for sure.
The admin/content/types lists the content types available for your access rights. The admin/content/types/audio would give a page to edit the attributes regarding the content type audio. Other modules may add tabs to the page but only if your user has access to the function provided by the tab.
After the backup I would check the access to the functions for the user. Are you user id 1 or are you using some role with rights given?
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
You didn't give the Drupal version. I would start with the backup for sure.
Ooops - 5.7
The admin/content/types lists the content types available for your access rights. The admin/content/types/audio would give a page to edit the attributes regarding the content type audio.
Yes, correct on both counts! The only problem is our site is broken for some reason, as noted in my last post. I did see on d.o that module incompatibilities can cause this behavior. I saw such a post anyhow.
Other modules may add tabs to the page but only if your user has access to the function provided by the tab.
After the backup I would check the access to the functions for the user. Are you user id 1 or are you using some role with rights given?
User id 1 of course.
I am anyhow in the process of updating all contrib modules to latest versions. Interestingly enough, I had to degrade admin_menu b/c the latest version actually caused a completely blank page for user id 1. The older version works fine for us.
If that fails, then I will start to disable modules one by one I guess...
Thanks!
Quoting Fred Jones fredthejonester@gmail.com:
I am anyhow in the process of updating all contrib modules to latest versions. Interestingly enough, I had to degrade admin_menu b/c the latest version actually caused a completely blank page for user id 1. The older version works fine for us.
I'm glad to read that you have your issue resolved. For the blank page the following are interesting reads.
http://drupal.org/node/158043 http://drupal.org/node/173319
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
I'm glad to read that you have your issue resolved. For the blank page the following are interesting reads.
Thanks. My problem not debugged yet, but for now it's not pressing. :)
Thanks for your help!
Fred
On Thu, Apr 10, 2008 at 6:32 PM, Fred Jones fredthejonester@gmail.com wrote:
On a normal site when I go to
http://xxx.org/admin/content/types/audio
I see the links:
# Edit # Manage fields # Display fields # Add field # Add group
Or something like that, depending on which CCK modules I have. However, I have a 'broken' site that shows:
* List * Add content type * Fields * Export * Importwhich is more like what I would expect to see at the URL
http://xxx.org/admin/content/types
On the 'broken' site I indeed see those same links on /admin/content/types
Right, http://xxx.org/admin/content/types/foobar gives you a http://xxx.org/admin/content/types page when a "foobar" content type has not been defined or a module responsible for it is disabled/broken.
So, does the "audio" content type appear in your list of types in the http://xxx.org/admin/content/types page or not?
If it exists, is "audio" its exact machine-readable name, and does its link lead exactly to http://xxx.org/admin/content/types/audio ?
CCK (5.x-1.6-1) is of course enabled, but this site has a LOT of modules, including one custom one. This is what CCK says:
Required by: Asset Manager (disabled), Content Copy (enabled), Content Taxonomy (enabled), Content Taxonomy ActiveSelect (enabled), Content Taxonomy Autocomplete (enabled), Content Taxonomy Options (enabled), Date (enabled), Date Copy (enabled), EMail (enabled), Fieldgroup (enabled), Image (enabled), Node Reference (enabled), Number (enabled), Option Widgets (enabled), Text (enabled), User Reference (enabled)
I would think that next debugging step would be to disable CCK, but that requires disabling all those required mods. I am a bit concerned, however, that if I disable them, something may happen to our data.
Any advice as to how to proceed? This is not my site--I just inherited it and need to work on it.
I suppose I will make a backup and do my debugging idea, but if anyone has another idea, let me know. :)
Thanks!
[ Drupal support list | http://lists.drupal.org/ ]
Right, http://xxx.org/admin/content/types/foobar gives you a http://xxx.org/admin/content/types page when a "foobar" content type has not been defined or a module responsible for it is disabled/broken.
ah, very interesting.
So, does the "audio" content type appear in your list of types in the http://xxx.org/admin/content/types page or not?
If it exists, is "audio" its exact machine-readable name, and does its link lead exactly to http://xxx.org/admin/content/types/audio ?
Yes, it exists and that's the link. I chose that as an example, but this problem exists for ALL content types which I can click 'edit' on from /admin/content/types including:
http://xxx.org/admin/content/types/page
The live site works fine--all nodes appear to be in working order. I am still investigating the mod code. Slowly... :(
Fred
On Thu, Apr 10, 2008 at 8:07 PM, Fred Jones fredthejonester@gmail.com wrote:
Right, http://xxx.org/admin/content/types/foobar gives you a http://xxx.org/admin/content/types page when a "foobar" content type has not been defined or a module responsible for it is disabled/broken.
ah, very interesting.
So, does the "audio" content type appear in your list of types in the http://xxx.org/admin/content/types page or not?
If it exists, is "audio" its exact machine-readable name, and does its link lead exactly to http://xxx.org/admin/content/types/audio ?
Yes, it exists and that's the link. I chose that as an example, but this problem exists for ALL content types which I can click 'edit' on from /admin/content/types including:
http://xxx.org/admin/content/types/page
The live site works fine--all nodes appear to be in working order. I am still investigating the mod code. Slowly... :(
Interesting. In case this helps narrow it down, the "page" and "story" core types do not rely on CCK or any special modules (except if you have added more fields besides title and body) and they are created as user-defined types with a database INSERT during Drupal installation.
On the other hand, the "blog entry" core type does rely on a blog module.
Fred
[ Drupal support list | http://lists.drupal.org/ ]
Interesting. In case this helps narrow it down, the "page" and "story" core types do not rely on CCK or any special modules (except if you have added more fields besides title and body) and they are created as user-defined types with a database INSERT during Drupal installation.
I disabled the outdated ecommerce module that the site isn't using anyway and I uninstalled two modules which were disabled and now the CCK types are working!
Still don't know what it was, but now it's fixed. :)
Thanks!