Closed (fixed)
Project:
Block Cache Alter
Version:
7.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Sep 2011 at 15:29 UTC
Updated:
22 Sep 2016 at 18:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
benys commentedi fix it
Comment #2
swentel commentedCommitted and pushed, thanks!
Comment #4
mukesh_k_see_node_1875610 commentedThis patch is working. Thanks!
Comment #5
damien_vancouver commentedI was also getting a lot of these errors and upgrading to 7.x-1.x-dev fixed it! Thanks!!
any chance of a 7.x-1.1 recommended release that contains this and the other fixes since 1.0?
Comment #6
vacilando commentedAgreed; 7.x-1.x-dev removes these notices -- could a new stable version be published, please?
Comment #7
tobiberlinI still get this error messages... so I re-open this issue.
I applied the patch in #1 but still I get masses of these messages in Drupal logs sometime... It seems that sometimes when I edit a block in views and then got to blocks administration page something seems to fire these error. Additionally it seems that sometimes on cron it happens as well.
Comment #8
damien_vancouver commented@tobiberlin,
can you try installing 7.x-1.x-dev and see if the problem still happens? That release worked for everyone else on the thread, so maybe the patch from #1 is not all that's required.
If you're still having the problem in 7.x-1.x-dev then it might be a different problem causing the same error.
Comment #9
tobiberlinok... thank you for this hint... changing to the dev version fixed it. I do not feel comfortable with this situation as I use this module on a productive project... any plans to release a next stable version including these changes soon?
Comment #10
damien_vancouver commented@tobiberlin,
Great to hear that the -dev version fixed it. So to be clear for anyone new coming along, you need to upgrade to 7.x-1.x-dev, not just apply the patch here.
As for when a new version will come out, that's a question for the maintainer. New releases can obviously cause a bunch of support requests so it's often very difficult as the maintainer to actually get the trigger pulled if you don't have a nice big time window available for providing support.
I wouldn't be scared of running the 7.x-1.x-dev at this point - just make note of the date you installed it and then if it changes you can always return to this exact version just as it it was a stable release. Eventually when the next stable version comes out, you can upgrade to that and stay on that instead of -dev.
I'm setting this issue back to Closed (Fixed) since -dev is working for you.
Comment #11
tobiberlinthank you!
Comment #12
lammensj commentedI hate to be the partypooper here, but the patch isn't working for me on the dev version. I'm still getting undefined notices about the bid. So the attached patch file should fix that. Can someone confirm?
Comment #13
joshuautley commentedI can confirm combining patch #1 with #12 works for me
Comment #14
dotoree commentedHere is a patch for version 7.x-1.0
Comment #15
dotoree commentedPrevious patch is not working for version 7.x-1.0 use #15