CHANGELOG.txt 5.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. References 7.x-2.x
  2. ==================
  3. #1391814 by yched: Fixed encoded HTML entities in select widget (regression
  4. introduced in 2.0)
  5. #1354580 by bforchhammer, yched: Fixed unpublished referenced nodes not
  6. displayed to users that are allowed to see them (regression introduced in 2.0)
  7. #1345816 by bforchhammer: Added support for the 'view_unpublished' module.
  8. #1256280 by girishmuraly: Added query alterability in hook_field_prepare_view().
  9. #1183300 by scor: Fixed extraneaous #maxlength in node_reference_autocomplete
  10. widget.
  11. #1410300 by yched: Fixed hook_field_install() should live in .install files.
  12. #1409022 by yched: Fixed missing view name notification message in D6 migration.
  13. #1391814 followup by yched: Fixed raw HTML in Views exposed filters.
  14. #998848 followup by larowlan, stevector, yched: template suggestions for
  15. referenced node in a specific view mode are wrong.
  16. References 7.x-2.0
  17. ==================
  18. Note for users upgrading from References 7.x-2.0-beta3:
  19. There were a couple changes in the way 'References' views are handled
  20. ("referenceable nodes/users defined by a view"), which might require
  21. double-checking those existing on your site:
  22. - The 'label' (node title or user name) is no longer automatically added if not
  23. included in the view. If some of your 'References' views currently do not
  24. include it, you might want to add it explicitly, else it will no longer appear
  25. in the widgets.
  26. - The HTML generated by the view is no longer stripped out before being handed
  27. to "checkboxes / radios" widgets, thus allowing advanced formatting. You might
  28. want to check for Reference views having fields configured to display "as
  29. links", since the (probably unwanted) <a> tags generated by Views are not
  30. removed anymore.
  31. Note for users upgrading from CCK D6:
  32. - The Refernces project integrates with the content_migrate module present in
  33. CCK 7.x-2.x-dev to allow the migration of field definitions and field values
  34. from D6 nodereference and userreference fields. Field values are safely
  35. migrated, and a best effort is made for the field definitions, but the settings
  36. for widgets and formatters might need to be manually checked and adjusted after
  37. the migration.
  38. - The "referenceable nodes/users defined by a view" feature is now supported
  39. through the dedicated 'References' views Display type, as opposed to using the
  40. 'default' display in D6. A temporary backward-compatibility layer is included
  41. and the existing views should keep working as expected (if they have been
  42. properly adapted/migrated from D6 themselves), but it is highly recommended to
  43. edit them and add an explicit 'References' display - submitting the "field
  44. settings" will lose the currently selected view if it doesn't have a
  45. 'References' display.
  46. - The remarks in "Note for users upgrading from beta3" above also apply.
  47. #1157530 by yched: Fixed node-specific code in references.module code.
  48. #1157746 by yched: Fixed 'match' option not working in views.
  49. #1149600 by dafeder, yched: fix 'Undefined index error' in
  50. _[user|node]_reference_view_settings_validate().
  51. #1045019 by Les Lim, Steven Jones, rickvug, and KarenS: Added devel_generate
  52. integration.
  53. #1230550 by yched: Dispaly a warning about manual Views edits during D6 field
  54. migration.
  55. #1083902 by dereine, derhasi: Added backreference views relationships.
  56. #1157538 by yched: Enhance previews for 'References' views displays.
  57. #1094406 by h0tw1r3: Added Account for the 'view own unpublished content' perm
  58. when displaying referenced nodes.
  59. #1183300 by Pasqualle: Remove maxlength from noderef autocomplete widget.
  60. #1236096 by Dave Reid: fix fatal error on prepare_view (followup to #1094406)
  61. #1275096 by Scyther, dereine, and jenlampton: Fix column not found error for nid.
  62. #1275096 by jboese, dereine: Fix column not found error for nid (take 2).
  63. #1341148 by plach: Fix Check views_access() when using Views to get the potential
  64. references.
  65. #1085576 by henrrrik, stamina, yched: Added "raw ID" and "raw path" formatters.
  66. #1051624 by Stalski: Added "rendered user in a given view mode" formatter for
  67. user_reference fields.
  68. #988856 by Nephele, johnv, rickmanelius, BlakeLucchesi ... : Added Feeds mapper
  69. for node_reference and user_reference fields.
  70. #1219224 by kunago, michaelfavia, yched: Added support for optgroups in select
  71. widget (for referenceable nodes/users provided by a view).
  72. #1194086 by Dave Reid, mariagwyn, yched: Display entity labels through entity_label()
  73. (formatters only for now)
  74. #1288852 by yched: Fixed "Trying to get property of non-object" with fatal error
  75. on user_reference fields using a view (when the view does not include the
  76. user name as a field).
  77. #1378086 by yched: Stop implicitly adding the 'node title / user name' field in
  78. Reference views if it is not present in the view definition.
  79. #1155946 by yched: allow HTML in "checkboxes / radios" widgets (for lists of
  80. referenceable targets generated by views).
  81. #1139238 by wondex, s_leu: Add relevant meta data in the 'potential_references'
  82. db query to allow smart alteration.
  83. References 7.x-2.0-beta3
  84. ========================
  85. This release primarily aims at facilitating synchronized releases of 3rd party
  86. modules making use of the node_reference_potential_references() function.
  87. #1154998 by yched: Rename _node_reference_potential_references() to
  88. node_reference_potential_references().
  89. References 7.x-2.0-beta2
  90. ========================
  91. Initial beta release (starting directly at beta2, the beta1 git tag got borched)
  92. Note : If you installed a previous 7.x-2.x dev version, it is recommended to
  93. clear your sites caches after deploying this release.