Table of contents:
Afin de répondre aux questions relatives aux perspectives de développement et de savoir où implémenter les différentes fonctionnalités des extensions pour eZ publish, cet article vous donnera une vue d'ensemble pour atteindre vos objectifs de programmation.
Avant de commencer à programmer, vous devriez lire les debugging tips. Il vous faudra apprendre comment ajuster les paramètres de configuration de votre site pour rendre plus facile le débogage de votre nouveau code et pour tracker les erreurs .
Create segmented functionality and avoid future upgrade conflicts by implementing your solutions as an extension instead of changing base eZ publish files (core/kernel).
Creating a new setting, types of settings, settings overrides, settings security.
Making eZ publish secure, issues, experiences and footnotes.
What are plugins?
A login handler handles authentication of a user. The login handler is provided with a login id and a password, and returns a valid eZ publish user for the system to
use. This information can be used to authenticate against an external system.
Give an example of a useful uses of single sign on handlers
Give an examples of when to create or use a datatype?
When you need to store data in eZ publish database, as content object attributes and the data (type) format is not already supported by eZ publish (stock) or existing free/open-source software contributions on ez.no or pubsvn.ez.no
What is a workflow event type? Give examples of when to create a workflow event.
What is a content action handler? With a content action handler you can extend the content/action view.
What is a content edit handler? With a content edit handler you can extend the content/edit view.
With the Lucene search plugin or other eZ search plugin you can customize and extend searching in eZ publish completely!
Templates plug directly into eZ publish and are programed in eZ template language (also known as tpl, eztpl). eZ publish templates have been called similar to ... lisp? Templates represent the display formating, templating and internationalization layer of eZ publish.
While simply elegant to use templates are a very powerful tool comprised of even more powerful tools and information. eZ publish templates come with a large number of built in template features. This allows functionality to be implemented very quickly and simply.
While larger templates may benefit in reduced performance load in implementing some functionality as a custom extension.
Template operators plug into the Template system in eZ publish and are programmed in PHP. Template Operators can take input, transform it, and return a result to the template. eZ publish comes with a lot of built in template operators.
Typical usage of a template operator is like this:
{'input'|mytploperator('param1','param2')}
If you have a lot of loops, ifs and fetches to manipulate variables, that is usually a good idea to put in an template operator.
It is typically useful for:
In the administration interface of eZ publish there is a wizard that helps you creating template operators. Go to "Setup" - "RAD" - "Template Operator wizard"
Put more detailed example here..
When to use template operators? Why there are so few template operators or documentation on them as a category or subject?
Template functions are built in language constructs, functions which provide features within the template language.
When to use notifications?
When to use notification events?
When are notification handlers a way to implement what functionality, wait, what are notification handlers?
See collaboration handler development.
What is a module, why not to confuse modules and extensions, when are modules needed
When to write a script and what type? If you need automated execution you would write a cronjob, while if you only supported manual execution you would write a command line script.
Examples of simple, basic and advanced cronjobs.
Term: cronjobs
Examples of simple, basic and advanced cli scripts.
At times one needs to use intimidate knowledge of eZ publish internals (kernel) to archive certain specific functionality. It is _not_ recommended to change the kernel or stock eZ publish core, because upgrades will be much harder. Patches mean merges often by hand, which can become time consuming and or tedious.
If you really want to do it, learn more about the design of eZ publish, kernel limitations and solutions. Custom solutions based on eZ publish may find that kernel modifications are required to provide extended features or functionality.
The code samples will help you getting started with some commonly used parts of the eZ publish API. They can be really useful in your custom modules, scripts and cronjobs.
Solutions to a common need to extend eZ publish in similar ways. These solutions can be minimal / direct or longer articles with source code examples.
Upgrade documentation from eZ systems
All text is available under the terms of the GNU Free Documentation License
Powered by eZ publish 3.9.3