Closed (fixed)
Project:
Taxonomy display
Version:
7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Reporter:
Created:
28 Apr 2011 at 20:27 UTC
Updated:
23 May 2011 at 13:21 UTC
When you choose Associated content display as view and choose desired view from the drop down the list of available View's displays is not updated unless you save the settings and reenter the manage display again. Also unneeded View's display as Block is present even if selected view does not have any block defined.
I'm using current dev version of views
Comments
Comment #1
codycraven commentedVito do you have Javascript enabled and working? It sounds like it is not enabled or you have another script running on your site that is creating an error which is causing the Associated Content Display to not trigger it's Javascript (since Javascript has previously encountered an error).
Please open a separate ticket for "Also unneeded View's display as Block is present even if selected view does not have any block defined."
Comment #2
codycraven commentedForgot to mark need more info.
Comment #3
vito_swat commentedthe javascript is enabled and site is not very modified. Standard D7.0 with only popular modules like views, pathauto are installed. The JS is definitely doing something as blue circle is going for a while and FF console states:
POST http://[...]/system/ajax [HTTP/1.1 200 OK 2527ms]
and only indicates problems in CSS parsing as filter property is not undersood by FF in lines 24 and 48 of jquery.ui.core
For the Block issue I've opened: #1143628: Unneeded View's display as Block is present even if selected view does not have any block defined. but this seems very related to it as my first enabled views has only master and block displays... So as updating of displays does not work for me this is expected behaviour.
Comment #4
codycraven commentedvito_swat, are you able to reproduce this issue with the latest dev? I think my fix in #1143622: Not able to enable any build view mode when Taxonomy display is enabled solved this problem as I am unable to reproduce it -- and it would be logical for that problem to cause this one.
Comment #5
vito_swat commentedCurrent dev is working fine now, thanks
Comment #6
codycraven commentedChanged version to show where the issue is fixed.