Fatal error: Unsupported operand types in includes/common.inc on line 1275 - after user registration

Thanks I was getting this as well for Boost for new user registration. I disabled Boost for now, and the registration works again.

I am getting a similar error

Fatal error: Unsupported operand types in /home/cyour3/public_html/drupal/includes/common.inc on line 1369

when a guest tries to create a new forum topic. (http://drupal.org/node/349942)

It works fine when this Boost module is disabled...

I have disabled the boost module because of this error and so any fixes to this issue would be really useful

Deepak

www.1your.com/drupal

I am also getting this error when a new user submits his registration form... I am disabling boost for now....a fix would be nice...

Same thing here when Boost is enabled. Will there bee a fix soon? Thanks for this great Module! :)

Try this:

boost was creating problems with password reset and registration with my installation. I haven't tried the patch yet.

Patch is working with my site,

Thanks!

This path works fine for me as well.

Thanks for your help.

www.1your.com/drupal

patch worked for me also. Thanks

This is only a slight modification to what you have here, I was getting line 1369 for mine.

slantview, maybe it's something wrong with your drupal? According to drupal api: 'query' A query string to append to the link, or an array of query key/value properties.
Both our patches should not cause errors.

Sorry, I used a comma to indicate two unrelated things. I was getting line 1369 because of using Drupal 6.8, not because of your patch. The only reason I changed it was because I thought it was more consistent with the "Drupal way" to use an array instead of just appending the string. Both are technically correct, I just think it looks cleaner this way. Either one works.

guys,

Another question may be related to this.

I have allowed anonymous users to post new forum topics. When anonymous users creates new forum topics, they get created but does not appear in the forum view (list of threads in the forum) as that page is cached. Is this an acceptable behaviour from your perspective? If so, is there a way to disable boost just for the forums?

Thanks,

Deepak

Deepak, I think it is not this topic issue. It is a boost caching feature. Try to exclude pages with forum view from caching. This can be done at admin/settings/performance page.

Thanks very much nagibator for pointing this out!

Walked through that setting so many times but somehow failed to identify its usage.

Cheers,

Deepak@1your.com

Either patch works fine and is minor. Let's get this into boost asap :)

The second (slantview's) patch works just fine for me, too.

can anybody commit that?
Tested #11 and working fine.

Tested #11 and it worked.

Tested and saved #11 and working fine for me too.
Thanks everyone.....

This is ready to be committed. Hello Boost devs, are you out there?

Tested #11 and it works as suggested.

Thanks much alex s and slantview!

(Helping googlers: )
This also affects the Contact Form and other form submissions, and results in a WSOD.

Issue should be unassigned so Boost developers catch it.

#11 follows the 6.x url api
http://api.drupal.org/api/function/url
Good Job!

committed patch from comment #11

Confirmed patch from #11.
Thanks Steve :)

I'm still having trouble with anonymous forms, and I looked at the patch. But I'm confused. I don't have lines anything like

         // If no query string was previously set, add one just to ensure we
         // don't serve a static copy of the page we're redirecting to, which
         // would prevent the session messages from showing up:
-        $destination = url($path, 't=' . time(), $fragment, TRUE);
+        $destination = url($path, array('absolute' => TRUE, 'query' => 't=' . time()));

in my boost. module. I downloaded the latest boost and I don't see lines like that there either. So what file does the patch change?

@Dracolyte
This is a really old issue, open up a new issue for what ever problem your having. This issue will not fix it, code has changed a lot since April. Also please explain what is not working for you.