Closed (fixed)
Project:
Bitcache
Version:
6.x-1.0-alpha3
Component:
Upgrade
Priority:
Minor
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
2 Dec 2008 at 16:27 UTC
Updated:
2 Jan 2014 at 23:45 UTC
Jump to comment: Most recent
Comments
Comment #1
Wound commentedI 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:
Comment #2
justin.hopkins commentedI had this problem also - downgraded to alpha2 and it went away.
Other installed modules:
bitcache
cck
drush
fileframework
dav
rdf
views
Comment #3
abu3abdalla commentedsubscripe
Comment #4
Arto commentedMy 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.
Comment #5
abu3abdalla commentedstill 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
Comment #6
spiffyd commentedI confirm this error!
Comment #7
jdenniss commentedI 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.
Comment #8
mdgrech commentedsame 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
Comment #9
nmashruwala commentedSubscribing
Comment #10
jayelless commentedHi. 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
Comment #11
vladimir_e commentedRan 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.
Comment #12
justin.hopkins commentedI 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!
Comment #13
nmashruwala commentedJustin, 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 =)
Comment #14
justin.hopkins commentedCool, glad you made use of it!
Comment #15
akwala commentedsubscribe
Comment #16
rherrick commentedAs 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.
Comment #17
digital.wannabe commentedsame here like rherrick...
Comment #18
digital.wannabe commentedsame here like rherrick...any attempt to view created filenodes/nodes with attachements leads to stated error.
Comment #19
chawl commentedOn 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.
Comment #20
markmck1 commentedThanks - installing the 6.x-1.x-dev tarball fixed it for me. I appreciate the help!
Comment #21
Arto commentedIf anyone's still experiencing these problems after upgrading to 6.x-1.0-beta1, please reopen this issue.