I am not sure if this is a bug or it is supposed to work like this bit if the Force transition option is selected every new node, no matter if they have workflow or not, will be affected.

I discovered this the hard way, taken me the best part of two days, as I was creating other content types and test content that only was accessible for UID 1.

The reason I used the Force transition option is due to the bug I posted in this [[/node/431224||ticket]]. I did it because I thought that not doing so would still make new nodes remain in creation stage.

If this option is supposed to work this way it needs a much better info text explaining this.

I am might miffed at the moment, but also glad I managed to solve this problem. Hopefully it will save someone else a lot of pain...

Comments

tsvenson’s picture

tsvenson commented

Here's a working link. #431224: Wrong initial state for new nodes. Didn't notice the issue tracker uses a different format...

Can also add that the result for new nodes is that only UID 1 will ever be able to access them until each node_access row for non workflow nodes have been de-workflowed...

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (won't fix)

Since this request is over 2 years old, I'm going to assume a solution was found or you've moved on. If not, please get updated to the latest versions of all modules and see if things have fixed themselves. If not, open a new ticket and I'll be glad to look at it.