Users can post answers to their own questions, but no luck when another user tries to answer. The answer is submitted successfully but winds up *unpublished* when the question and answer are from different users.

I cannot reproduce this on fresh install of 3.8, so I guess it's something in my setup. but this is the first I've gotten around to trying to use the Q&A features and so don't think I've messed with anything that I can think would affect this.

I have checked all the answer related permissions i can find(site-wide and within the group) and they seem fine. I have checked the answer content type and it does default to published. My commons_q_a feature does not show any overrides that I can think would affect answer publishing (just the message_type modifcations I have to do to work around a totally unrelated email bug).
In fact the associated messages get created/emailed as I would expect, but the node itself does not get published.

But somewhere along the way it seems like depending on who is submitting the answer the node gets unpublished.

Any advice on where to keep looking for a solution would be much appreciated.

Comments

WebSinPat’s picture

Title: Cannot answer a question posted by another user » Users cannot answer questions
Version: 7.x-3.8 » 7.x-3.9

Just upgraded to 3.9 and still having this problem, or a variation of it.

Now a user can answer her own question, but admin users cannot answer any questions (their own or anyone else's). Again the answer node is created successfully, but it remains unpublished.

Stumped.

lsolesen’s picture

Status: Active » Closed (won't fix)

Closing out old issues. Please reopen if still relevant.

lsolesen’s picture

Category: Support request » Bug report
Status: Closed (won't fix) » Active

Closed by mistake. This might still be a valid issue. Please close it with the solution, if you already solved it.

jlscott’s picture

Hi. I had an issue that appeared very similar to this when I had the module commons_bw_ui installed. The issue went away when I disabled and un-installed that module.