QuickAppsCMS v2.0.0-beta2 released

[Chris]

Here is it, the second beta preview of QuickAppsCMS. Although this release is mainly focused in polishing UI look and bug fixes, it includes some new and exciting features. Below a brief list of changes introduced in this release.

New Backend Theme

A new and gorgeous backend theme has been introduced based on AdminLTE 2. Fully responsive and multiple colors schema available.

Introducing AOP (Aspect-Oriented Programming) API

The GO! AOP framework has been introduced as part of QuickAppsCMS's core, this brings customization to a whole new level. The old fashion `alter()` events are no longer supported in favor of AOP method interception.

Content Types Permissions

Now is possible to restrict who can edit, create, translate, delete or publish contents of certain types. These permissions are assigned per Role basis; this allows you to create complex organizations where for instance, you may have a process in place where editors produce content, but only the leader editor can decide if and when it is published.

And Much More

For installation instructions and further information about this new release please check the official repository at GitHub: https://github.com/quickapps/cms/releases , and also the brand new QuickBook at this link: http://api.quickappscms.org/book/

[Gabri]

Very interesting features, Chris!

I'll try it soon!

AOP is so good.

Regards Permissions I like the more granular way, I think it could be interesting to have the chance to "restrict" content for users, I mean, ie: I'm the editor X and I can post content but I cannot edit (or view) content of the editor Y.

Anyway I let you know about what you've done till now! 

[Gabri]

Hi Chirs,

A few question regards the new version:

- there is something similar to Site App of the previous version?

- there is a QuickApps Cli for administrative tasks and for creating plugin/theme structure?

- how can I make a search (using the framework search engine) for a specific content type? (something like $this->requestAction("/search/type:my_type");)

- it is possibile to set time duration for static::cache? (or in that case is better using Cakephp cache?)

Thanks!

On Wednesday, May 27, 2015 at 11:48:21 PM UTC+2, Chris wrote:

[Chris]

HI,

- SiteApp:

v2.0 allows to overwrite templates, here an extract from the API:

Allow users to overwrite ANY template by placing it at site's

ROOT/templates/Front and ROOT/templates/Back directories. These

directory has the highest priority when looking for template files. So in

other words, this directories behaves as some sort of "primary themes". Each

directory represents a "Frontend" and "Backend" respectively. For common

templates -shared across front & back- the ROOT/templates/Common

directory can be used instead.

-  CLI:

In v2.0 CLI is now part of the core. It provides shells aimed for administrative/maintenance tasks. You can find CLI at "ROOT/bin", just open a new terminal there and run "qs" to start the CLI.

However, the new CLI does not provide baking tasks for creating themes/plugin, BUT dont worry in v2.0 all plugin & themes are just CakePHP plugins, actually any cakePHP plugin can be installed in QACMS. So if you need to create a new Theme or Plugin just use CakePHP's bake shell. http://api.quickappscms.org/book/designers/themes.html

- Search API:

Simply import the "Contents" table (within the "Content" plugin) and use the "search()" method, for instance in your controller method:

    $this->loadModel('Content.Contents');

    $contentEntities = $this->Contents->search("type:CONTENT_TYPE_SLUG");

- Cache duration:

I dont get what you mean, what is "static::cache"?

If you are refering to QACMS's "StaticCacheTrait" I can tell you that it's not a persistent cache. Actually it is used for "Static" classes, commonly used to speed up script execution. Description from the API:

    Allows classes to optimize their methods by providing a simple `cache()` static method for reading and writing values.

Regards!