"Unsupported operand" error on installing Bitcache
ariedels - December 2, 2008 - 16:27
| Project: | Bitcache |
| Version: | 6.x-1.0-alpha3 |
| Component: | Upgrade |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Arto |
| Status: | closed |
| Issue tags: | bitcache_link, hook_link |
Jump to:
Description
Hi -
I have twice tried to install this module and twice gotten the following error on my homepage afterwards:
Fatal error: Unsupported operand types in ~~~/includes/common.inc on line 1445
Has anyone else gotten it? I did see this issue posted here http://drupal.org/node/308437, but the fix there did not seem work for me.
I am on v6.6 and PHP 5.2
Thanks

#1
I have the same issue. It appears as soon as I try to go to the start page. When I navigate to one of the admin pages I get the following log messages:
#2
I had this problem also - downgraded to alpha2 and it went away.
Other installed modules:
bitcache
cck
drush
fileframework
dav
rdf
views
#3
subscripe
#4
My apologies for this problem. It should now be fixed in changeset [156488]; please try the 6.x-1.x-dev tarball once it gets rebuilt (happens automatically every 12 hours).
If you guys can report back that this resolves the problem for you, I will cut a new release containing the fix.
#5
still i have problem but not that error its in common.inc line 1445
i am also use it because the fileframework need it .
when i use the alpha 2 is good and untill now i have no error
but the alpha3 and the new dev i have error
#6
I confirm this error!
#7
I have it as well.
I get the following when I use the back button (back to 'content' page)
recoverable fatal error: Argument 3 passed to bitcache_link() must be an array, boolean given in /var/www/localhost/htdocs/DP/modules/bitcache/bitcache.module on line 459.
recoverable fatal error: Object of class stdClass could not be converted to string in /var/www/localhost/htdocs/DP/modules/bitcache/bitcache.module on line 460.
#8
same here :( Ive been for forever to get fileframe work to work...I which someone would write a comprehensive tutorial for this module...note Ive seen the tut on installing on a server
#9
Subscribing
#10
Hi. I encountered this problem with the alpha3 release. Worked fine until I loaded a file into the bitcache repository; then the error occurred. Upgraded to latest 1.x-dev release as suggested, and the error disappeared.
Thanks
James
#11
Ran into the same bug, downgrading to alpha2 or installing the newest 6.x-1.x-dev tarball as of today fixes it for me too.
#12
I did try to write it up over at http://justin-hopkins.com/blog/2008/12/02/how-to-setting-up-drupal-file-...
Please comment and help me improve if you can!
#13
Justin, your tutorial is beyond terrific! FF's dependency list is complex enough that I probably wouldn't have managed it nearly as cleanly without your write-up and bhuga's write-up.
Also, it got me addicted to drush =)
#14
Cool, glad you made use of it!
#15
subscribe
#16
As of today, I'm seeing this version of this error:
Fatal error: Unsupported operand types in .../drupal-6.8/includes/common.inc on line 1539This occurs when I activate the Bitcache module then log out and go to the front page. I'm very up-to-date (this might be part of the problem :): I updated Drupal to 6.8 yesterday and downloaded and installed all of the dependencies for fileserver, including bitcache, today. Let me know if you have any other questions about my configuration.
#17
same here like rherrick...
#18
same here like rherrick...any attempt to view created filenodes/nodes with attachements leads to stated error.
#19
On Drupal 6.8, alpha3 made homepage blank immediately after install.
Also when you try to create a file node, preview seems ok but when you save, all you got another blank page, no matter what the file type was. Other non-blank pages that you can browse always show the same error with #1, but not just 2 lines, sometimes pages of them alternating randomly for 459 and 460.
Though alpha2 fixes everything back.
#20
Thanks - installing the 6.x-1.x-dev tarball fixed it for me. I appreciate the help!
#21
If anyone's still experiencing these problems after upgrading to 6.x-1.0-beta1, please reopen this issue.
#22
Automatically closed -- issue fixed for 2 weeks with no activity.