ApostropheCMS changelog

Changelog History

Page 30

• v2.5.0 Changes

  October 21, 2016

  ✅ All tests passing.

  • Implemented apos.areas.fromPlaintext, which accepts a string of plaintext (not markup) and returns an area with a single apostrophe-rich-text widget in it, containing that text. Useful in implementing importers.
  • The so-called csv import mode of apos.schemas.convert works properly for areas, using the above. Although it is called csv this mode is really suitable for any situation in which you have plaintext representations of each property in an object and would like those sanitized and converted to populate a doc.
  • 🐛 Bug fix: emit the enhance Apostrophe event only once on page load. This event is emitted only when there is new content that has been added to the page, e.g. once at page load, and also when a new widget is added or updated, etc. The first argument to your event handler will be a jQuery element which will contain only new elements.
  • 🚀 Legacy support for data/port and data/address files has been restored. (Note that PORT and ADDRESS environment variables supersede these. In modern Stagecoach deployments data/port is often a space-separated list of ports, and the deployment/start script parses these out and launches multiple processes with different PORT variables.)

• v2.4.0 Changes

  October 19, 2016

  ✅ All tests passing.

  ↪ Workarounds for two limitations in MongoDB that impact the use of Apostrophe cursors:

  • The addLateCriteria cursor filter has been introduced. This filter should be used only when you need to invoke $near or another MongoDB operator that cannot be used within $and. The object 🔀 you pass to addLateCriteria is merged with the criteria object that is built normally by the cursor. Use of this filter is strongly discouraged unless you must use operators that do 👍 not support $and.
  • Custom filters that invoke $near or other MongoDB operators that are incompatible with $text queries may call self.set('regexSearch', true) to force the cursor to use a regular expression search rather than full MongoDB full-text search, if and when the search() filter is called on the same cursor. This was implemented to allow combination of full-text and geographical searches, subject of course to the limitation that regular expression search is not indexed. It also doesn't sort by quality, but $near provides its own sort by distance.

  Since these are new features a minor version level bump is appropriate. However neither of these is a feature that a typical site developer will need to call directly.

• v2.3.2 Changes

  October 17, 2016

  ✅ All tests passing.

  • 0️⃣ The quality of the autocomplete search results shown when selecting pages or pieces via a join was low. This has been corrected by calling the .sort('search') filter to sort by search result quality rather than the default sort order for the doc type manager in question.
  • 🚑 All of the autocomplete suggestions fit on the screen on reasonably sized displays. With the recent addition of the "flip" feature to push the suggestions up rather than down if the bottom of the screen would otherwise be reached, this is critical to show the first and best suggestion. Further discussion for future UX improvement in issue 704.

• v2.3.1 Changes

  October 13, 2016

  ✅ All tests passing.

  • 🛠 Fixed a bug in the new "copy page" feature that affects pages that have null properties.
  • 👌 Improved the experience of using the widget controls to manage the widgets in an area.
  • The login module now has an alias, apos.login, like other core modules.
  • ⚡️ Updated the jquery projector plugin to the latest version.

• v2.3.0 Changes

  October 06, 2016

  ✅ All tests passing.

  • 🛠 Fixed a bug affecting the use of arrangeFields in modules that extend another module's use of arrangeFields. Added unit test based directly on a real-world project.
  • baseUrl project-wide option added, yielding the same benefit as in 0.5: you get absolute URLs for all pages everywhere. (If you don't want absolute URLs, just don't set it.) This is very beneficial when generating og:meta tags for Facebook, or generating emails.
  • A direct link to the original file has been added to the file manager's editor modal.

• v2.2.2 Changes

  October 05, 2016

  ✅ All tests passing.

  • ➕ Addition of slugs to projection for autocomplete is now done in a way that still allows overrides at the doc level to add other properties.
  • ➕ Addition of slugs to projection for autocomplete works for joins with a specific page type, too.
  • 🛠 Fixed a chicken-and-egg problem in the global module that kicked in if the "global" doc contains widgets powered by modules not yet initialized at the time the global module checks for the existence of the doc.

• v2.2.1 Changes

  October 04, 2016

  ✅ All tests passing.

  🛠 Fixed an oversight: the new pageBeforeCopy global method now takes req as its first parameter. Since 2.2.0 was first published 5 minutes ago and this method has not yet been documented this is not regarded as a bc break.

• v2.2.0 Changes

  October 04, 2016

  ✅ All tests passing.

  • 🛠 Fixed bug that broke removal of permissions for pages.
  • "Copy Page" feature added to the page menu.
  • Automatically reposition the autocomplete dropdown for joins if it would collide with the bottom of the window.
  • Include page slugs in the autocomplete dropdown for joins with pages.
  • ⏪ chooserChoiceBase.html restored; some projects were depending on extending it, which is a useful technique.

• v2.1.5 Changes

  October 01, 2016

  ✅ All tests passing.

  • 🔧 Admin bar: previously grouped fields can be re-grouped successfully, so concatenating admin bar configuration works just as well as concatenating addFields arrays
  • Files widget displays upload button in the same user-friendly position as the images widget
  • Font size for tabs and help labels is explicit to avoid side effects from project-level CSS

• v2.1.4 Changes

  September 23, 2016

  ✅ All tests passing.

  • Previously chosen items that now reside in the trash no longer break the chooser for editing joins
  • All joins editable; certain edge cases weren't getting blessed
  • A field appears properly when two diferent choices list it for showFields
  • As in 0.5, a required field hidden by showFields is not required (but will be if you elect the choice that shows it)

• « First
• ‹ Prev
• 26
• 27
• 28
• 29
• 30
• 31
• Next ›
• Last »