When a user with limited permissions (see attached list of permissions) wants to create a stormticket, stormproject or other storm related node, he gets a WSOD after clicking on "Save".

In the PHP error log there is the line Unsupported operand types in \includes\common.inc on line 2877 but I tried to figure out what was wrong there and the only variable used is $elements and that is an array, as it should be. I have no idea what could cause this error message.

I thought it was a permission issue, because user 1 can create storm nodes without a problem.

Also, when I temporarily grant permission to create a page node, that works just fine.

Any ideas?

CommentFileSizeAuthor
#6 stack.zip179.71 KBjurgenhaas
permissions.txt1.95 KBjurgenhaas

Comments

Magnity’s picture

Is this something that was working until a recent update?

jurgenhaas’s picture

Unfortunately I can't tell because only recently the users with limited permissions started creating tickets in the system. In fact, that was today and never before.

Magnity’s picture

I haven't been able to reproduce this issue on the latest -dev.

Are you creating the nodes directly within Storm rather than via QTT or Dashboard?

Is the WSOD on submitting the node form or viewing the form?

jurgenhaas’s picture

Originally I created the nodes through dashboard but when I saw the error I went to /node/add and selected one of the node types from there. I also tried from the original Storm dashboard with no luck (which isn't a surprise, that also calls node/add anyway).

The WSOD occures when submitting the form.

Magnity’s picture

I haven't been able to track this down unfortunately so far.

Other info:
- Version of PHP?
- Other modules installed?
- Is there a backtrace available from the error?

jurgenhaas’s picture

StatusFileSize
new179.71 KB

OK, here is some good news, all discovered because of your last series of questions:

- attached is the stack trace and the last stack is the one that caused the error

- as the last module that was calling drupal_render() - the function that's crashing - was Mollom, I tried disabling Mollom and suddenly the crash disappeared. So it sounds as if Mollom is causing this issue!?

@Magnity, do you want to contact the Mollom maintainers directly? Probably the most efficient way to find out what's going wrong in the combination of Storm and Mollom.

Magnity’s picture

Project: Storm » Mollom
Component: Storm.module » Code

Glad to hear we're closer to finding the problem.

... Moving to the Mollom issues queue for review.

dries’s picture

Status: Active » Fixed

This will be fixed in the upcoming version of Mollom. We no longer use node_rebuild().

Status: Fixed » Closed (fixed)

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