- Fixed nested widget editing for existing widgets whose modal dialog boxes have been accessed (#1428).
- A clear warning message with instructions has been added for those who are seeing “unblessed” messages due to widget schemas and in-template
apos.areacalls that do not match (#1429). The easiest way to avoid this is to just mark the areacontextual: truein your widget schema so it is edited only on the page. But if you really want to do both, the widget options must match. - The mechanism that automatically makes slugs, paths and other keys unique now gives up eventually and reports the original duplicate key error. This makes it easier to debug your code if you are violating your own custom indexes that feature unique keys. It is possible to make the deduplicator aware of your own own properties that need to be made more unique on inserts if you wish, by implementing a
docFixUniqueErrormethod. Please note: this change is not a regression. Code that formerly never completed its task in this situation will simply report an error promptly rather than retrying inserts forever while degrading your database performance. - A new profiling API has been added: the
apos.utils.profilemethod. This method can be called to report how long code takes to run for later analysis. To be clear, this is not a complete profiler. It does nothing in the default implementation; modules like our forthcoming profiler module override it to give feedback on the speed of your code.
1 Like