Closed (outdated)
Project:
Context
Version:
6.x-3.0
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Oct 2008 at 11:36 UTC
Updated:
19 Mar 2020 at 16:41 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jmiccolis commentedInteresting. What browser and OS are you using?
Comment #2
z.stolar commentedFF3.0.3 on Ubuntu 8.04
Comment #3
daveparrish commentedSub. I'm having the same problem using Firefox 3.6.3 and Chrome 5.0.375.23 under Windows. My version of Context is 6.x-2.0-rc1.
Comment #4
steven jones commentedChanging to actively maintained version.
Is there anything in your JS console or any other visible errors?
Comment #5
daveparrish commentedNone that I can see. I had Javascript errors and warnings turned on with Firebug.
Comment #6
steven jones commentedWhat themes are you using with context when you got the errors?
Comment #7
daveparrish commentedSorry for the long delay on this response. I was using genesis theme and it has a known conflict with context. #763790: Unable to view Context.module's block delete link with Genesis Subtheme
Comment #8
Cyrilovich commentedI had the allmost the same problem. An uncaughed error in the js while the page was loading, and when trying to remove a block. After debuging i found this in "context_reaction_block.js" :
// Show blocks in selector that are unused
$('div.context-blockform-selector input').each(function() {
var bid = $(this).val();
if ($('table.context-blockform-region tr#'+bid).size() === 0) {
$(this).parents('div.form-item').eq(0).show();
}
});
$(this).val() was empty ! It makes jquery bugging on the call : $('table.context-blockform-region tr#'+bid).size()
I added the commented line : if (bid == '') return;
// Show blocks in selector that are unused
$('div.context-blockform-selector input').each(function() {
var bid = $(this).val();
if (bid == '') return; //We check bid. If empty we just return.
if ($('table.context-blockform-region tr#'+bid).size() === 0) {
$(this).parents('div.form-item').eq(0).show();
}
});
And now it works without- error.
May-be it can help some one.
I hope it will be integrated in the module core ?
Comment #9
fuzzy76 commentedAs far as I can tell, the maintainer got an answer
Comment #10
fuzzy76 commentedIn patch form
Comment #11
deaom commented