Download the PHP package idetik/coretik without Composer
On this page you can find all versions of the php package idetik/coretik. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package coretik
Coretik : Wordpress framework
Manage models, queries, services and more...
Installation
composer require idetik/coretik
Get started
Dependency Injection Container
A coretik application uses Pimple as Dependency injection containers.
As many other dependency injection containers, Pimple manages two different kind of data: services and parameters.
Please read the official documentation on Github: https://github.com/silexphp/Pimple.
Coretik comes with severals services built in. You can find them in src/Services (doc in the todoux list...)
First, create your application container in your functions.php :
Schema : declare custom post type and taxonomies
Simple use case
Advanced
This is an advanced use case using macros
Post type
Taxonomy
Models
As model in MVC design pattern, it contains only the pure application data. This makes it easier to maintain and scale the application over time. It supports relathionships between post types and taxonomies or others customs stuffs.
Setup
Usage
Advanced
Models can handle post metas easily, including protected metas. Models provides a meta accessor like object properties. Metas have to be declared in the model constructor. Only declared metas will be saved in database on a CRUD action.
Create & save a model :
Use a model :
Queries
Use coretik queries to retrieve models behind complex clauses. Queries are more readables and useables than a basic wp_query who need to manage metas, taxonomies and settings directly. Four kinds of query are ready to use: PostQuery, TermQuery, UserQuery and CommentQuery.
Simple query
One way to query all wp_post filtered by default query args, and browse result models :
See src/Core/Query/Post::getQueryArgsDefault()
Others query
See src/Core/Query/Adapters folder.
Custom query
Setup
Usage
Handlers
Handlers were designed to be reusable, maintainable and flexible. Handlers allow us to hook anythings about a post type or taxonomy, and give us the capability to modify the default workflow as you want.
Your handler have to implement Coretik\Core\Builders\Interfaces\HandlerInterface;
Let's take an example of an application with many formations belongs to categories. Each formation has many events belongs to the same categories. We have a formation post type, an event post type and a category taxonomy. I want to update the event category when I change its formation category.
Macros
Use to extend a builder.
All versions of coretik with dependencies
pimple/pimple Version ^3.5
nesbot/carbon Version ^2.66
pelago/emogrifier Version ^7.0
wesbos/burner-email-providers Version ^1.0
globalis/wp-cubi-helpers Version ^1.0
illuminate/collections Version ^10.6
globalis/wp-cubi-transient-cache Version ^0.3.0