New content that I create can't be published. In Publishing options I tick an option "Publish" and press save page are not published. I press Edit and I see that Publish option is unticked, I tick it again and save, but no luck. Sorry for my bad english, how can I solve this problem? Thanks.

Comments

theborg’s picture

theborg commented
Status: Active » Postponed (maintainer needs more info)

Cannot reproduce on 6.x-dev version, linux, ff 2.0.
Can you provide more info? Which system are you testing this? Modules enabled?

Aero-1’s picture

Aero-1 commented
Status: Postponed (maintainer needs more info) » Active

FF 2.0, I reviewed database and set 1 at status to publish it manually. All default modules are enabled.

cburschka’s picture

cburschka
they
commented
Status: Active » Postponed (maintainer needs more info)

I've successfully created a public node, unpublished and republished, and created a non-public node, then published. No problem...

This information would be very helpful in tracking the problem down:

- What database system, what version?
- What OS, webserver, PHP version on the server?
- What addons are enabled, what theme are you using?
- When did you last check out the CVS head?
- Is the site newly set up, or updated from an earlier version? (If so, what version?)
- Are you doing this as user 1 or not? (If not, what are the access permissions of your user?)
- What is the default setting of the content in admin/content/types/{your-content-type}?

Aero-1’s picture

Aero-1 commented

- I don't know.
- PHP 5.2.5.
- Garland. All default modules are enabled.
- I don't know.
- Updated from Drupal RC1.
- Yes, from user 1.
- Default setting is to publish content.

cburschka’s picture

cburschka
they
commented

Sorry, I see now that you tagged this RC2, so you are working with the downloaded release, not CVS (I'm used to the latter so I forgot that).

It's very likely you're using MySQL 5.x or 4.x, but even if you're not, I'm not sure how that could cause the issue. By "default" modules I assume you mean you didn't enable any of the other core modules that came with the site.

So to put it briefly, I'm stumped. If this happened on my site, the next step in debugging I'd take would be to open the node module's PHP files, find the form builders and submit handlers, and liberally stuff them with var_dump() calls to find out what is going on.

Can you tick the other options, such as "Sticky" or "Promoted to Front Page", or will those be lost as well?

webernet’s picture

webernet commented
Assigned: Aero-1 » Unassigned
Category: bug » support
Priority: Critical » Normal

Are you using trigger.module by any chance? http://drupal.org/node/210335

Aero-1’s picture

Aero-1 commented

Yes, I fixed problem by that link. Thanks for the help.

webernet’s picture

webernet commented
Status: Postponed (maintainer needs more info) » Fixed
Aero-1’s picture

Aero-1 commented
Status: Fixed » Postponed (maintainer needs more info)

Thanks for the help, problem solved. I just reconfigured Trigger module corractly and viola!

webernet’s picture

webernet commented
Status: Postponed (maintainer needs more info) » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.