- Updated according to: 2.0.20
- Bootstrap 4 => 2.0.4
- Imagine => 2.2.0
- Auth Client => 2.2.3
- Debug => 2.1.5
- Queue => 2.2.1
- HTTP client => 2.0.11
Jun 17, 2019
Jun 12, 2019
Let’s try to get the best and most active Yii extension builders together and create a community effort to build and maintain an extensive collection of long-term supported, best-practice coded, well-documented, well-tested, multi-lingual, feature-rich Yii 3 extensions.
Join the discussion about community maintained extensions for Yii 3.x - Feedback and ideas are greatly appreciated!
May 30, 2019
Dana Luther about using Yii2 Queue, Redis and Docker Swarm to scale background jobs.
May 27, 2019
With this new version of the LUYA admin, we switch to strict semver versioning. This means that we will try to follow http://semver.org as good as possible.
Therefore the version constraint changed from the
~ to the
^ operator. With the previous versioning system, the admin module would have become version 1.3, with the new one it will be 2.0. This will also be the case for all other modules with breaking changes in the future (the CMS module will follow shortly with version 2.0 as well).
So make sure to use the correct version constraint in order to profit from upcoming updates.
The admin module now integrates the Yii Queue component upon which the new LUYA Scheduler is built.
This is a new generic Angular directive which turns any field into a scheduling option to plan the change of ANY value. Let's assume you have a CRUD system with a status field and its possible values "published", "archived" and "draft". Now you can enable scheduling for this field in order to have its value automatically changed at any given date and time in the future. No more need for datetime or timestamp fields in order to setup display limitations. You can enable a cronjob or have the system run a "fake cronjob" (which has to be turned on in the configuration of the admin module) in order to process the queue.
Also new is a notification system that highlights CRUD lists with new data added since your last visit, either through the administration or a frontend form. In order to receive these notifications, you simply have to visit a CRUD view once. This is especially interesting for frontend-generated inputs. As the notifications are only automatically enabled for visited CRUD views, the system will not overwhelm and annoy users with notifications that are not of interest to them – this is important with different users working in different sections.
And, of course, you can turn off these notifications for any CRUD view with a single click.
We have strongly enhanced the CRUD system. Searching, filtering and sorting is now context specific. So you can apply a filter and search in the results of the filter afterwards. There is also a new tags view which lets you filter the content by tags.
The tags view will automatically be displayed if the system detects that your ngrest model has the Taggable Trait attached.
With version 2.0 we introduce a new feature called "data pools" (this has been on our list for a long time). It's a common scenario to combine data in one table that should be managed in separate CRUD views. An example would be events on a website that includes both a public area and an intranet – you might want to keep the data separate in different CRUD views for the admin users (possibly with different field listings and program logic) while technically it is stored in the same table.
To enable data pools for a table, it usually has a field to distinguish the pool a record belongs to. With the new
itemPoolApi permission entry and the ngRestPools() method you are now able to display only data for a given pool. The information about the pool will even be passed to CRUD relation views, if available.
With this version we took a big step forward for using the admin as a headless API, therefore we have added a new tool to allow deeper insights into the requests coming to the API. What are the slowest URLs? Which API is called often? This helps you evaluate the requests that should be cached on the client.
In addition, the LUYA headless client has been released as version 2.0, too, with some new features and improvements. It was never easier to use LUYA admin as a data provider for different websites, modules and applications!
May 2019, LUYA developer team
May 21, 2019
Yii team released Queue extension version 2.2.1.
There are several interesting changes in this release:
Also there was a conceptual mistake in the previous release about adding handle method to cli queue class. It was moved
Full changelog is available at GitHub.