I'm working with the biblio module and I'm having a problem where the publishing options I set under Workflow Settings at admin/content/node-type/biblio (Default options>Published) are not respected when creating a new biblio node at node/add/biblio - the Published checkbox is not checked even if I set it to be checked in the settings. This is the first time I've encountered this and I'm new to Drupal but I wonder if it is connected to other modules I have installed and not biblio? Some of the other modules I'm using that have an effect on the admin/content/node-type/biblio page are Fivestar and Vertical Tabs. I've tried doing a general search for this problem but I'm not having any success.

Thanks in advance.

Comments

rjerome’s picture

I just tested it on my system, and the options on admin/content/node-type/biblio are respected when I create new Biblio types, so I suspect there might be some intervention by other modules.

Ron.

gpiersol’s picture

Thanks for your reply Ron.

Unfortunately after more searching around and after disabling a number of different modules, the problem remains, and I don't know how to proceed with locating the source of the issue. Do I need to reinstall biblio? And if so how will deleting and re-installing it affect the existing biblio nodes?

Thanks,
Geoff

rjerome’s picture

If you uninstall the module on the /admin/build/modules/uninstall page you will lose all your existing biblio nodes. Simply disabling the module on the /admin/build/modules page will not harm your biblio nodes.

Have you tried turning off caching (if it's enabled on the admin/settings/performance page)?

There was another report today (http://drupal.org/node/634030), while not the same, it seems like they may be related.

Ron.

gpiersol’s picture

Thanks again for responding so quickly Ron.

I followed your suggestion re: caching but with no luck.

I'm not sure if its a separate or related issue but after I select a publication type when I create a new biblio node I get the form validation error "Title field is required" even though I have not tried to save the node yet. This is not happening with other content types.

Geoff

rjerome’s picture

The validation error is "normal", just a side effect of how that form is rebuilt.

What version of Drupal are you using?

gpiersol’s picture

I'm using 6.14 and according to the status report page my server details are: Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.7 with Suhosin-Patch

rjerome’s picture

There have been a number of "strange" problems surrounding 6.14 and I'm beginning to wonder if this isn't falling into that category.

I'm going to do a clean install of 6.14 later today to see if I can reproduce any of these. Strangely my 6.14 installation that was upgraded 6.9 -> 6.10 -> 6.11 ->... doesn't seem to have any problems, so I think it may have something to do with clean installs.

Ron.

gpiersol’s picture

Thanks again Ron. I'll wait to see what you discover with 6.14.

I just made another discovery of my own. I created a new user without the administer nodes permission, created a new biblio node with that user, and the node was published.

rjerome’s picture

I did a clean install of 6.14 and still can't reproduce this issue, so I'm guessing it's one of your other modules or configuration.

If possible, it would be helpful if you could do a clean install of 6.14 with only the biblio module and see if the problem persists.

Ron.

liam morland’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.