Active
Project:
Boxes
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Aug 2010 at 21:28 UTC
Updated:
17 Aug 2011 at 13:16 UTC
Jump to comment: Most recent file
When using pressflow, boxes gives the error
Notice: Array to string conversion in boxes_footer() (line 155 of /ebs/platforms/sites/all/modules/boxes/boxes.module).
Looks like a similar issue/solution to http://drupal.org/node/601420
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | boxes.patch | 633 bytes | penyaskito |
| #6 | boxes-pressflow-headers.patch | 605 bytes | rpfmorg |
| #1 | 887260.patch | 605 bytes | teito79 |
Comments
Comment #1
teito79 commentedThe problem is caused by a patched version of drupal_set_header when using Pressflow. I am not sure this patch belongs to boxes or to Pressflow patch set. What do you think?
we gave it a fix and here's the patch file
Comment #2
jmiccolis commentedWell, if the pressflow version of `drupal_set_header()`returns an array... I actually like that better and have no problem adding this conditional.
@mzytaruk, does this patch work for you?
Comment #3
flevour commentedI applied this patch and the notice disappeared, I am using Pressflow myself too.
Cheers,
Francesco
Comment #4
mzytaruk commentedYep, works perfectly for me as well. Thank you.
Comment #5
deverman commentedsubscribing using pressflow and boxes but not sure if we have run into this yet.
Comment #6
rpfmorg commentedI got a malformed patch error when applying this to version 6.x-1.0. The actual fix worked fine - I just needed to update the range information to get the patch to work.
Comment #7
jmiccolis commentedThx for the patch! It has been committed.
Comment #8
david straussWhile I appreciate the change to the module to make it compatible with Pressflow, this appears to be a bug in Pressflow's API, which should be as close to Drupal's as possible. Now, it's pretty easy for me to change the return value of the function back to the Drupal 6 way, but I'll have to survey the impact to other parts of Pressflow core. Can you file this as a bug on bugs.launchpad.net/pressflow? Thanks.
Comment #9
jmiccolis commentedReported https://bugs.launchpad.net/pressflow/+bug/652027
Opening the ticket back up; we'll need to revert this patch once there is a upstream release of Pressflow which includes a fix.
Comment #10
eojthebraveI'm still getting this error with the latest release of boxes although #7 makes it sound like the patch was committed. Am I missing something?
The patch from #6 works great for me, but want to make sure that we're clear about the status of this so that other people don't get confused as well.
Comment #11
fuzzy76 commentedeojthebrave, the patch is committed, but there have been no new releases of boxes for 6.x since then, so it is not part of any release yet.
For what it's worth, the original patch worked fine for me. :)
Comment #12
penyaskitoI did another patch (my fault, I didn't look at the issue queue before).
It' s a different approach, so maybe it is worth taking a look.
It's a based on my own svn and the latest release of boxes. If you are intested on this approach I can make a patch against current HEAD in cvs.
Thanks.
Comment #13
Yura commented#6 works well
Comment #14
j0nathan commentedPatch #6 works for OpenAtrium (profiles/openatrium/modules/contrib/boxes) over Pressflow.