New on eZpedia

Solution: Running cronjobs.php with parameters in limited environment

Fri, 09 Jan 2009 14:15:30 GMT

Question

How can I run eZ Publish scripts and cronjobs with parameters on shared hosting without ssh.

You may only be allowed to run php files as a cronjob without any parameters and without the possibility to browse eZ Publish directory.

You also may not have command line access. Yeah, this can be pretty frustrating, but can not find or afford a better hosting solution.

Solution

When your provider doesn't allow you to run cronjob tasks with parameters and when your server runs php-cgi.
In order to run cronjob task with parameters, you can create a separate php file and then create a cronjob task pointing to that file.

Example

Here is an example of the solution using the data_import extension as an example.

File: /path/to/ezpublish/extensions/custom/cronjobs/custom_cronjob.php

<?php
 
$output = shell_exec('cd /path/to/ezpublish/; /path/to/php5 runcronjobs.php import_images_csv');
 
echo "<pre>$output</pre>";
 
?>

You may for very small tasks be able to run the above file from a web browser as long as the script completes quickly as browser requests do not work well with long running tasks.

References

eZ Publish 4

Mon, 22 Dec 2008 21:21:33 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Migrating from the eZXML library to PHP 5 DOM

Mon, 22 Dec 2008 20:53:34 GMT

API replacements

DOM Document

eZXML	DOMDocument	Remarks
$xml = new eZXML() $dom = $xml->domTree( $xmlDoc )	$dom = new DOMDocument() $success = $dom->loadXML( $xmlDoc )	there were some extra options which we need to check, like character set conversion

eZDOMDocument	DOMDocument	Remarks
->create_element( $name [, $attributes] )	$element = $dom->createElement( $name ) $element->setAttribute( $attrName, $attrValue )
->createElementNode( $name [, $attributes] )	$element = $dom->createElement( $name ) $element->setAttribute( $attrName, $attrValue ) ...
->createElementTextNode( $name, $text [, $attributes] )	$element = $dom->createElement( $name ) $element->appendChild( $dom->createTextNode( $text ) ) $element->setAttribute( $attrName, $attrValue ) ...
->dump_mem()	->saveXML()
->elementsByNameNS( $name, $namespaceURI )	->getElementsByTagNameNS( $namespaceURI, $name )	can be called on each DOMNode, not only on a DOMDocument
->get_root()	->documentElement	property
->Root	->documentElement	property
->root()	->documentElement	property
->setRoot( $element )	->appendChild( $element )
->toString()	->saveXML()

DOM Node

eZDOMNode	DOMNode and subclasses	Remarks
->append_child( $node )	->appendChild( $node )
->attributeCount()	->attributes->length	see below
->attributes()	->attributes	property, returns DOMNamedNodeMap instead of array now, use $attributes->length property instead of count( $attributes ), see above
->attributeValue( $name )	->getAttribute( $name )
->attributeValueNS( $name, $namespaceURI )	->getAttributeNS( $namespaceURI, $name )	pay attention to the changed order of the function arguments
->Children	->childNodes	property, returns DOMNodeList instead of array now, use $children->length property instead of count( $children )
->children()	->childNodes	see above
->childrenCount()	->childNodes->length
->content()	->textContent	property
->dump_mem()	$element->ownerDocument->saveXML( $element )
$element->dump_mem()	$element->ownerDocument->saveXML( $element)
->elementAttributeValueByName( $name, $attributeName )	$firstElement = $element->getElementsByTagName( $name )->item( 0 ) $attributeValue = $firstElement->getAttribute( $attributeName )
->elementByName( $name )	->getElementsByTagName( $name )->item( 0 )
->elementChildrenByName( $name )	$firstElement = $element->getElementsByTagName( $name )->item( 0 ) $children = $firstElement->childNodes
->first_child()	->firstChild	property
->firstChild()	->firstChild	property
->firstElementByName( $name )	->getElementsByTagName( $name )->item( 0 )	see elementByName
->get_attribute( $name )	->getAttribute( $name )
->get_elements_by_tagname( $name )	->getElementsByTagName( $name )	Returns all descendant elements with the name $name, not only direct children. To get only direct children with the name $name, use DOMXPath or loop over ->childNodes
->hasChildren()	->hasChildNodes()
->lastChild()	->lastChild	property
->localName()	->localName	property
->name()	->localName	property
->namespaceURI()	->namespaceURI	property
->nextSibling()	->nextSibling	property
->node_value()	->nodeValue	property
->parentNode()	->parentNode	property
->prefix(), ->setPrefix( $prefix )	->prefix	writable property
->previousSibling()	->previousSibling	property
->remove_attribute( $name )	->removeAttribute( $name )
->set_attribute( $name, $value )	->setAttribute( $name, $value )
->textContent()	->textContent	property
$element->toString()	$element->ownerDocument->saveXML( $element)
->type()	->nodeType	property, one of the predefined XML_xxx_NODE constants

Important notes

The DOMElement::insertBefore function returns the appended node, and you should use it! Otherwise you can get unexpected results or uncaught exceptions (like DOMException with message "Not Found Error").

When looping over the DOMElement::childNodes property, you can not remove or move any of the existing children, or insert new one. This will cause the property to change and your loop will apparently skip certain children or handle certain children twice. Instead of looping directly over childNodes, you can first make an array containing the children and loop over that array to make your modifications. In case you only want to remove certain items, looping over childNodes in reverse order (from the last one to the first one) is a solution as well.

The same applies to the DOMElement::attributes property.

Unpublishing content

Mon, 22 Dec 2008 17:45:37 GMT

Unpublishing one or multiple content objects, can be done in several ways:

delete them
- at a specified date & time, with the unpublish cronjob
hide them
- at a specified date & time, with the hide cronjob
move them to an archive section of your website
- at a specified date & time, with the archive extension

Solution: Clear Cache on eZ Publish

Wed, 17 Dec 2008 23:38:54 GMT

Introduction

How to clear cache using eZ Publish 4

Administration

Use the website administration interphase to clear all cache via a gui.

Simply navigate to Setup tab
Click the clear cache icon
Refresh browser window of website

Command line

If you know how to use the command line you can use it to clear cache.

Unix

If you are using a complete unix like operating system you can use the following command to clear and purge all cache within eZ Publish.

cd /path/to/ezpublish;
./bin/php/ezcache.php --clear-all --purge;

Windows

If you are using Windows you can use the following command to clear and purge all cache within eZ Publish.

# cd c:/web/pro/ezpublish/doc;
c:\php\php ./bin/php/ezcache.php --clear-all --purge;

Manual

If you are unable to use the administration gui or command line to clear cache, you can still remove the cache files manually.

cd /path/to/ezpublish;
rm -vrf /var/cache;
rm -vrf /var/ezwebin_site/cache

References

Hiding or unhiding subtrees

Sat, 22 Nov 2008 09:44:25 GMT

if ( $node->attribute( 'can_hide' ) )
{
    if ( $node->attribute( 'is_hidden' ) )
    {
        eZContentObjectTreeNode::unhideSubTree( $node );
    }
    else
    {
        eZContentObjectTreeNode::hideSubTree( $node );
    }
}

Solution: Publishing static pages from eZ Publish

Thu, 13 Nov 2008 01:34:44 GMT

Question

How does one publish static pages from a completed eZ Publish website installation?

Suggestion

Read the following reference and suggestion example.

Example

I used this to produce an inexpensive visual preview of a customer's eZ Publish website.

httrack http://ez  -O "."  -%v  -*layout* -*Calendar/* -*visual* --footer "" --preserve

References

Form: Publishing static pages

eZ Publish Test System

Wed, 01 Oct 2008 11:45:54 GMT

Warning

The test system is considered ever evolving and backwards incompatible changes may occur. We do invite you to start writing tests for it, just be warned that the tests may need some updating as we evolve the system.

Getting started

Requirements

PHPUnit 3.2.x or newer: http://www.phpunit.de/
eZ Components

Installation

Update to at least trunk rev 22408.
Generate autoloads for the test system:

php bin/php/ezpgenerateautoloads.php -s

Running tests

To run all tests do:

php tests/runtests.php -D mysql://root@localhost/testdb

The -D parameter is required and is used to tell the test system what type of database, username, host and which database to use. Make sure the username you specify is allowed both create and remove the database. The DSN uses the following format:

databasetype://username:password@host/database

If you want to run a single test suite, just point to the directory containing a suite.php file.

php tests/runtests.php -D mysql://root@localhost/testdb tests/tests/kernel

Filter which tests to run

To run a single test you can use the --filter option like this:

php tests/runtests.php -D mysql://root@localhost/testdb --filter=testGlobBrace

In the above example both eZSysTest::testGlobBrace and eZSys::testGlobBraceSupported will be executed. If you only want to execute eZSysTest::testGlobBrace run:

php tests/runtests.php -D mysql://root@localhost/testdb --filter="testGlobBrace$"

This works too:

php tests/runtests.php -D mysql://root@localhost/testdb --filter="eZSysTest::testGlobBrace$"

As of PHPUnit 3 --filter can also be used to filter on test class names. This is a handy way of running all tests in a test case. Example:

php tests/runtests.php -D mysql://root@localhost/testdb --filter="eZSysTest"

List tests

To list all test use the --list-tests option:

php tests/runtests.php --list-tests

You can also narrow the output to only list tests defined in a specific suite:

php tests/runtests.php --list-tests tests/tests/lib/ezutils

Running a group of tests (group annotation)

With PHPUnit you can group different tests together by adding the group annotation to a method's documantion block:

To list all groups run:

php tests/runtests.php --list-groups

To run a group use the -g parameter:

php tests/runtests.php -D mysql://root@localhost/testdb -g issue_13492

Writing tests

Naming conventions

The test system itself follows eZ Components naming conventions defined here: http://ezcomponents.org/contributing/coding_standards#id8.

The tests itself follows the naming conventions of the code that it tests. In this case this means the tests follows the eZ Publish naming convention.

File and directory layout

The file structure used in eZ Publish is mirrored inside the test system. As an example, if you want to write tests for kernel/classes/ezcontentobject.php the test file should be located in tests/tests/kernel/classes/ezcontentobject_test.php. Regression tests for ezcontentobject should be located in tests/tests/kernel/classes/ezcontentobject_regression.php

*_test.php is the suffix used for unit tests. *_regression.php is used for as the suffix for regression tests.

Writing a unit test

The test system comes with a handy CLI script for generating stub tests from an existing class to get you going quickly. As an example, you can generate a stub test from kernel/classes/ezpreferences.php like this:

php tests/toolkit/extras/scripts/create-test-from-class.php \
               -s kernel/classes/ezpreferences.php \
               -d tests/tests/kernel/classes/ezpreferences_test.php

The generated tests/tests/kernel/classes/ezpreferences_test.php file will then look like this:

<?php
 
class eZPreferencesTest extends ezpTestCase
{
    public function __construct()
    {
        parent::__construct();
        $this->setName( "eZPreferences Unit Tests" );
    }
 
    public function testSetValue()
    {
        self::markTestIncomplete( "Not implemented" );
    }
 
    public function testValue()
    {
        self::markTestIncomplete( "Not implemented" );
    }
    // [...]
}
?>

To make the new test case work we need to add it to the appropriate suite.php. For this test case that is tests/tests/kernel/suite.php. Add

$this->addTestSuite( 'eZPreferencesTest' );

to the __construct method of eZKernelTestSuite and remember to regenerate test autoloads. To verify that the new test case is working run 'runtests.php' with -v:

oh:/www/trunk $ php tests/runtests.php -D mysql://root@localhost/testdb -v 
Based on ezcUnitTest in eZ Components
 
PHPUnit 3.3.0 by Sebastian Bergmann.
 
eZ Publish
 eZ Publish Test Suite
  eZ Publish Kernel Test Suite
   eZPreferencesTest
   IIIIIIII
 
[...]

Success! We're now ready to start writing the test by filling in the test* methods.

Normally tests are short and straight forward and should require little or no documentation. Due to the complexity of eZ Publish not all tests ends up being in this way. If you are writing a somewhat complex unit test, please document it a way that makes it easier to understand.

Writing a regression test

Regression tests are created in the same way as with unit tests, except the classes end with "Regression" and the file suffix is _regression.php. When writing a regression test please document it with the following:

Issue number + title of the issue.
Short description of the issue if the title isn't descriptive enough.
If the test is longer than a few lines, include what the test does in order to reproduce the issue.
The result and the expected result.
Link to the issue.

Here's a doc header example taken from testLinksAcrossTranslations():

/**
 * Test scenario for issue #13492: Links are lost after removing version
 *
 * Test Outline
 * ------------
 * 1. Create a Folder in English containing a link (in the short_description attribute).
 * 2. Translate Folder into Norwegian containing another link (not the same link as above.)
 * 3. Remove Folder version 1. (Version 2 is created when translating).
 *
 * @result: short_description in version 2 will have an empty link.
 * @expected: short_description should contain same link as in version 1.
 * @link http://issues.ez.no/13492
 */

If the issue has multiple tests group them together to make it easy to execute all tests for a single issue using the group annotation "@group issue_ISSUE_NUMBER" where ISSUE_NUMBER is the issue ID in the bug tracker. Example:

* @group issue_13492

Using a database

A common thing for tests is to interact with a database. By extending your test class or suite from either ezpDatabaseTestCase or ezpDatabaseTestSuite your test class/suite will become database aware. By default ezpDatabaseTestCase and ezpDatabaseTestSuite sets up a clean database using the dba files included in eZ Publish:

share/db_schema.dba
share/db_data.dba

Inserting your own data

If you need to provide your own schema/data you can override which SQL files is loaded by ezpDatabaseTestSuite by specifing the path to one or more SQL files in the $sqlFiles class method:

Example:

class eZURLAliasMlTest extends ezpDatabaseTestCase
    {
        protected $insertDefaultData = false;
        protected $sqlFiles = array( array( "kernel/sql/", "kernel_schema.sql" ),
                                             "kernel/sql/common/cleandata.sql" );
        // [...]
    }

Setting $insertDefaultData to false tells the test system that it should not attempt to load any data. If $insertDefaultData is not defined or if it's set to true the test system will first load the default data, then load any SQL files defined in $sqlFiles.

The first entry in $sqlFiles, array( "kernel/sql/", "kernel_schema.sql" ) is a way to provide a SQL file for one or more of the supported database types. If you're using MySQL, the test system would try to insert kernel/sql/mysql/kernel_schema.sql. If the database type is postgresql, the test system would try to insert kernel/sql/postgresql/kernel_schema.sql, and so forth.

The database type is determined by the -D (--dsn) parameter provided to the test runner.

Note: you can specify $sqlFiles on either your test class or in your suite. The default test runner behaviour is to only create a new database per suite. If you provide $sqlFiles in your test classes you will need start the test runner with the --db-per-test argument.

Providing extra data

In the above exampe we discussed how to override what data gets initially loaded into the test database. If all you need is to provide some additional data you can leverage the ezpTestDatabaseHelper class to load some extra SQL files:

$sqlFiles = array( "myextension/sql/data.sql" );
ezpTestDatabaseHelper::insertSqlData( $this->sharedFixture, $sqlFiles );

Writing tests for an extension

Extensions can include their own tests. When running tests the test runner will not only look for tests inside the tests/ directory, it will also scan each extension looking for a tests/suite.php file inside the extension. The extension does not need to be in the list of active extension (ActiveExtensions[] in site.ini) for it to be included. The only critera for the extension to be included is that is has a folder "tests/" with a suite.php inside. The suite.php should then include all tests in the extension. Below is an example of a typical extension file layout and where the tests should be located:

extension
    |-- myextension
        |-- autoloads
        |-- design
        |-- modules
        |-- settings
        |-- tests
        |   |-- mytest1.php
        |   |-- mytest2.php
        |   `-- suite.php
        `-- translations

You can specify the path to an extension to only run tests for that extension:

php tests/runtests.php -D mysql://root@localhost/testdb extension/myextension

One database per suite

Currently, the default behaviour is that a database is created per suite, not per test. Creating/removing the database easily adds 1-2 seconds of overhead per test on the database management systems that eZ Publish supports out of the box (MySQL, PostgreSQL). However, there's an extension ezsqlite which allows you to use an in-memory SQLite 3 database to run the tests with.

If you pass in the argument --db-per-test to the test runner it will change from the default behaviour, one database per suite, to one database per test. It's strongly encouraged that you write tests that works with both --db-per-test turned on and off.

To illustrate the difference in speed, below is how long it takes to run all tests with --db-per-test:

php tests/runtests.php -D mysql://root@localhost/testdb --db-per-test
PHPUnit 3.3.0 by Sebastian Bergmann.
 
............................................
 
Time: 01:48
 
OK (44 tests, 99 assertions)

And without --db-per-test:

php tests/runtests.php -D mysql://root@localhost/testdb
PHPUnit 3.3.0 by Sebastian Bergmann.
 
............................................
 
Time: 19 seconds
 
OK (44 tests, 99 assertions)

Resources

List of API BC breaks

Mon, 29 Sep 2008 05:42:41 GMT

eZ Publish 4

4.1

4.1.0

eZContentObject::fetchAttributesByIdentifier() doesn't accept any longer a string as 3rd argument, it needs to be an array now. See issue #13668.

4.0

4.0.1

The constructor of eZSOAPClient has a new parameter $useSSL, which defines the protocol to use: either http:// when $useSSL is false (default) or https:// when $useSSL is true. Previously, when the $port argument was 443, it was assumed automatically that https:// should be used. This is not longer the case in eZ Publish 4.0.1. In eZ Publish 4.0.2 however, this BC break will be fixed. For more background information, see issue #12267.

4.0.0

eZContentObjectTreeNode::subTree() and eZContentObjectTreeNode::subTreeCount() can not any longer be called statically, they are instance methods now. Use eZContentObjectTreeNode::subTreeByNodeID() and eZContentObjectTreeNode::subTreeCountByNodeID() instead.
eZContentObjectTreeNode::createPathConditionAndNotEqParentSQLStrings() does not have a 3rd argument $treeNode anymore. Use the 4th argument $nodeID instead to pass the ID of the tree node.
To register workflow event types, use eZWorkflowEventType::registerEventType() instead of eZWorkflowEventType::registerType().

Deleting objects

Sat, 30 Aug 2008 20:18:19 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Question

How to remove many objects from a content tree.

References

Forum: Deleting many objects
Solution: Script to delete all nodes under a node in content structure

Invoking the node/object browser

Fri, 29 Aug 2008 10:51:27 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

You can use the eZContentBrowse class to invoke a content browser, with which the user can select one or multiple objects / nodes. The most important method, browse(), actually ensures that certain session variables are set, and that the user agent gets redirect to the content/browse view. When the user submits the selection he made in content/browse, it will be posted to the initial module that invoked eZContentBrowse.

The browse() method accepts an array with quite some options which are not very well documented in the source code. What follows is an overview of the options and a short description on how to use them.

Key	Default value when omitted	Description
from_page		URL to post the browser selection to, obligatory
cancel_page	value of from_page	A value for the BrowseCancelURI field that will be posted back.
action_name	value of the INI setting browse.ini [BrowseSettings] DefaultActionName	A value for the BrowseActionName field that will be posted back. When a module view might invoke the content browser for different purposes then it should use this post field to find out for which purpose it called the content browser. Usually the value of the BrowseActionName post variable is used to automatically trigger an action in the module view. See the post_actions key in the module view definition.
type	value of action_name	Corresponding browse type in browse.ini, make sure this type exists otherwise you will get an error in the content/browse module.
selection	value of the INI setting browse.ini [BrowseSettings] DefaultSelectionType	The type of selection, either single or multiple. Can also be configured with the SelectionType setting in browse.ini.
return_type	value of the INI setting browse.ini [BrowseSettings] DefaultReturnType	The type of the return values, either ObjectID or NodeID. Can also be configured with the ReturnType setting in browse.ini.
description_template		Template to include containing a description, which is showed by the content/browse view
start_node		Node ID to start browsing on.
class_array		Class IDs of objects that can be selected. Other content objects can't be selected. Can also be configured with the Class setting in browse.ini.
ignore_nodes_select		IDs of nodes that can not be selected.
ignore_nodes_select_subtree		IDs of nodes of which no descending nodes (subnodes) can be selected. Seems like the admin design respects this setting, but the standard design does not.
ignore_nodes_click		IDs of nodes that can not be browsed into.
keys		An associative array of browse override keys that will be used to fetch settings from browse.ini. See http://ez.no/community/forum/install_configuration/set_startnode_when_browsing_in_browse_ini.
persistent_data		Associative array of persistent data, will be posted back.
permission		This parameter can be used to make only certain nodes selectable, based on the permission system. It must be a policy array that, together with the object ID of each node in the content browser, can be passed to the content/access fetch function. The fetch function will return if access is granted or not. If not, the node won't be selectable. Example value: array( 'access' => 'create', 'contentclass_id' => $class->attribute( 'id' ) ). Only nodes under which the current user can create objects of the class $class will be selectable.
top_level_nodes
browse_custom_action
custom_action_data

Marc MEBTOUCHE

Tue, 19 Aug 2008 10:09:56 GMT

Writing database implementation independant code

Wed, 09 Jul 2008 13:40:43 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Use the API of the database handlers

Common mistakes in SQL

Quoting literal string values

Use single quotes ( ' ) to quote literal string values, not double quotes ( " ). Certain database servers interpret a double quote as an identifier quote character.

Example

Wrong:

UPDATE ezcontentobject SET name="Foo" WHERE id=500;

Right:

UPDATE ezcontentobject SET name='Foo' WHERE id=500;

MySQL

By default MySQL allows double quotes to quote literal string values. However, you can turn on the ANSI_QUOTES SQL mode to make sure MySQL treats a double quote as an identifier quote character.

Aliases for columns and tables

Columns should be aliased with the AS keyword (example 1), tables should NOT be aliased with the AS keyword (example 2).

Example 1

Wrong:

SELECT COUNT(*) row_count FROM ezcontentobject;

Right:

SELECT COUNT(*) AS row_count FROM ezcontentobject;

Example 2

Wrong:

SELECT o.id, u.name FROM ezcontentobject AS o, ezcontentobject AS u WHERE u.id=o.owner_id;

Right:

SELECT o.id, u.name FROM ezcontentobject o, ezcontentobject u WHERE u.id=o.owner_id;

Troubleshooting extensions

Sat, 31 May 2008 08:37:44 GMT

You might have to double check certain things when an extension does not seem to work.

Whitespace in INI files

The INI system does not automatically trim values, so any trailing whitespace behind a setting value will be part of the value.

Consider an extension called "myextension" containing template operators. In the site.ini.append.php of the extension, you will find something like this:

[TemplateSettings]
ExtensionAutoloadPath[]=myextension

This will instruct the template system to look for a file extension/ezxajax/autoloads/eztemplateautoload.php. In this file, there's information on which classes in the extension contain which template operators.

However, if there is a space behind ExtensionAutoloadPath[]=myextension, it will try to find the file "extension/myextension /autoloads/eztemplateautoload.php", which of course does not exists.

Setting arrays being cleared by other INI files

Consider the following code:

TemplateSettings]
ExtensionAutoloadPath[]
ExtensionAutoloadPath[]=myextension

ExtensionAutoloadPath[] will re-initialize the setting again as an array, and any items added to the array in previously loaded setting files are lost.

Solution: Add Location to Object / Add Usergroup to User

Fri, 23 May 2008 06:27:57 GMT

This function allows adding a location to an extisting object even adds a usergroup to an existing user. The Code was taken and modified from kernel/content/action.php where it says " if ( $module->isCurrentAction( 'AddAssignment' ) )"

/**
  * Adds User to the chosen Usergroup
  * objectID=UserobjectID
  * newNodeID=usergroupNodeID
  * @param integer $objectID
  * @param unknown_type $newNodeID
  */
 function addLocation($objectID,$newNodeID)
 {
  //$selectedNodeIDArray = eZContentBrowse::result( 'AddNodeAssignment' );
  eZDebug::writeDebug("LocationAdd: objectID".$objectID."\nnewNodeID: ".$newNodeID);
   $object = eZContentObject::fetch( $objectID );
   $nodeID = $object->attribute("main_node_id");
   //$version = $object->currentVersion();
  $ini = eZINI::instance();
  $userClassID = $ini->variable( "UserSettings", "UserClassID" );
  // $node = eZContentObjectTreeNode::fetch( $nodeID );
  $selectedNodeIDArray = array($newNodeID);
        $node = eZContentObjectTreeNode::fetch( $selectedNodeIDArray[0] );
 
  if ( !is_array( $selectedNodeIDArray ) )
            $selectedNodeIDArray = array();
 
        $nodeAssignmentList = eZNodeAssignment::fetchForObject( $objectID, $object->attribute( 'current_version' ), 0, false );
        $assignedNodes = $object->assignedNodes();
 
        $parentNodeIDArray = array();
        $setMainNode = false;
        $hasMainNode = false;
        foreach ( $assignedNodes as $assignedNode )
        {
            if ( $assignedNode->attribute( 'is_main' ) )
                $hasMainNode = true;
 
            $append = false;
            foreach ( $nodeAssignmentList as $nodeAssignment )
            {
                if ( $nodeAssignment['parent_node'] == $assignedNode->attribute( 'parent_node_id' ) )
                {
                    $append = true;
                    break;
                }
            }
            if ( $append )
            {
                $parentNodeIDArray[] = $assignedNode->attribute( 'parent_node_id' );
            }
        }
        if ( !$hasMainNode )
            $setMainNode = true;
 
        $existingNode = eZContentObjectTreeNode::fetch( $nodeID );
        $mainNodeID = $existingNode->attribute( 'main_node_id' );
        $objectName = $object->attribute( 'name' );
 
        $db = eZDB::instance();
        $db->begin();
        $locationAdded = false;
        $node = eZContentObjectTreeNode::fetch( $nodeID );
        foreach ( $selectedNodeIDArray as $selectedNodeID )
        {
            if ( !in_array( $selectedNodeID, $parentNodeIDArray ) )
            {
                $parentNode = eZContentObjectTreeNode::fetch( $selectedNodeID );
                $parentNodeObject = $parentNode->attribute( 'object' );
 
                /*$canCreate = ( ( $parentNode->checkAccess( 'create', $class->attribute( 'id' ), $parentNodeObject->attribute( 'contentclass_id' ) ) == 1 ) ||
                               ( $parentNode->canAddLocation() && $node->canRead() ) );*/
                $canCreate=true;
 
                if ( $canCreate )
                {
                    $insertedNode = $object->addLocation( $selectedNodeID, true );
 
                    // Now set is as published and fix main_node_id
                    $insertedNode->setAttribute( 'contentobject_is_published', 1 );
                    $insertedNode->setAttribute( 'main_node_id', $node->attribute( 'main_node_id' ) );
                    $insertedNode->setAttribute( 'contentobject_version', $node->attribute( 'contentobject_version' ) );
                    // Make sure the url alias is set updated.
                    $insertedNode->updateSubTreePath();
                    $insertedNode->sync();
 
                    $locationAdded = true;
                }
            }
        }
        if ( $locationAdded )
        {
            if ( $object->attribute( 'contentclass_id' ) == $userClassID )
            {
                eZUser::cleanupCache();
            }
        }
        $db->commit();
 
        //include_once( 'kernel/classes/ezcontentcachemanager.php' );
        eZContentCacheManager::clearContentCacheIfNeeded( $objectID );
 
 }

Works with ezpublish version 4.x

Lorem ipsum

Fri, 14 Mar 2008 06:31:35 GMT

For a general descriptiion of Lorem ipsum, we recommend Lorem ipsum on Wikipedia.

There is an eZ Publish extension called loremipsum to generate objects with a lorem ipsum placeholder text in batch.

References

Forum: How to handle a big tree of products
Forum: New Script, CLI version of Lorem Ipsum

Solution: How to handle Information Collection in template.

Mon, 04 Feb 2008 23:11:45 GMT

Solution

This piece of template code iterating the already stored and collected information has only the purpose of demonstration.

{def $collection=fetch('content','collected_info_list', hash('object_id', $obj.id))}
{foreach $collection as $col}
  {$col.creator.contentobject.name|wash} {* name of the user who stored something into the i.c. *}
  {foreach $col.attributes as $colAttr}
      {$colAttr.contentclass_attribute_name}
     {attribute_result_gui view=info attribute=$colAttr}
  {/foreach}
{/foreach}

red5

Tue, 08 Jan 2008 20:30:19 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

References

iframe

Mon, 07 Jan 2008 05:42:51 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

You can use an iframe to embed an external web page within eZ Publish

References

Forum: Opening up external url inside ez CMS
Forum: External site in ezpublish cms
Forum: Comments on webmail wanted
Forum: Browsing a ftp http folder in a view
Forum: extension to manipulate an external php application
Forum: How to setup frames
Forum: Using frames flash and google issues
Forum: PHP integration
Forum: A unique module with results from various modules

ezimagealiashandler

Mon, 17 Dec 2007 10:09:26 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Introduction

This eZ Publish kernel class provides for the simple PHP based interphase to fetch an original image alias and image alias properties (uri, width, height, etc).

Detailed examples of the methods provided by this class are available within the API documentation.

Brief examples of how to use the class methods are provided in the following solution reference documentation.

Details

Internal manager for the eZImage datatype.

Takes care of image conversion and serialization from and to the internal XML format.

Note:This handler was introduced in eZ Publish 3.3 and will detect older eZImage structures and convert them on the fly.

The XML storage was improved in 3.8, from then it always stores the attribute ID, version and language in the <original> tag. This was required to get the new multi-language features to work.

References

Doc: Kernel Class API, eZImageAliasHandler
Solution: Fetching ezimage datatype image alias properties using PHP
Forum: New image system
Doc: Reference: ezimagealiashandler
Forum: Import image into existing class
Forum: displaying custom class images ezimagealiashandler

Solution: Fetching ezimage datatype image alias properties using PHP

Mon, 17 Dec 2007 10:05:11 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Introduction

Did you know that you can use the eZ Publish kernel api to obtain image alias properties from content object attributes which use the ezimage datatype.

Example

This is a simple php example of how you may use the eZ Publish kernel api to obtain image alias properties. This example comes from a simple example custom module view.

<?php
 
/**
 * File image.php
 *
 * @package image.php
 * @version //autogentag//
 * @copyright Copyright (C) 2007 Brookins Consulting. All rights reserved.
 * @license http://www.gnu.org/licenses/gpl.txt GPL License
 */
 
$Module =& $Params['Module'];
 
// START
 
// Assume this type of module/view url:
// www.site.com/myextension/mymodule/myview/1234
// 1234 maps to the view parameter, MyNode (eg: $Params["MyNode"])
 
// 0. Include the necessary files -- I would imagine that some are include
 
include_once( 'lib/ezdb/classes/ezdb.php' );
include_once( 'lib/ezutils/classes/ezfunctionhandler.php' );
include_once( 'lib/ezutils/classes/ezoperationhandler.php' );
include_once( 'lib/ezutils/classes/ezhttptool.php' );
include_once( 'kernel/common/template.php' );
include_once( 'kernel/classes/ezcontentclass.php' );
include_once( 'kernel/classes/ezpreferences.php' );
include_once( 'kernel/classes/datatypes/ezimage/ezimage.php' );
include_once( 'kernel/classes/datatypes/ezurl/ezurl.php' );
include_once( 'kernel/classes/datatypes/ezurl/ezurlobjectlink.php' );
 
// 1. Create an instance of the database
$db =& eZDB::instance();
 
// 2. Query the node via node id
$my_node =& eZContentObject::fetchByNodeID( $Params["MyNode"] );
// $my_node =& eZContentObject::fetchByNodeID( '86' );
 
// 3. Get a copy of the data_map
$my_node_data_map = $my_node->fetchDataMap();
 
// 4. Get a reference to the image
$my_node_image = $my_node_data_map["image"];
// $my_node_image_data = $my_node_image->DataText;
 
// Example Usage of the eZ Image Alias Handler Class / System
include_once( 'kernel/classes/datatypes/ezimage/ezimagealiashandler.php' );
 
// 5. Fetch Alias Handler
$image_alias_handler = new eZImageAliasHandler( $my_node_image );
 
// 6. Fetch Alias Attributes*
 
// 7. Fetch Original Image Path as URI
$my_node_image_uri =  "/" . $image_alias_handler->attributeFromOriginal( 'url' );
 
// 8. Fetch Original Image Dimentions
$my_node_image_width = $image_alias_handler->attributeFromOriginal( 'width' );
$my_node_image_height = $image_alias_handler->attributeFromOriginal( 'height' );
 
// 9. Get the associated link
$my_node_link_object = $my_node_data_map["my_link"];
$my_node_link_url_object = eZURL::fetch( $my_node_link_object->DataInt );
$my_node_link_url=str_replace ( "/", "+", $my_node_link_url_object->attribute( 'url' ) );
 
// 10. Instantiate the template and set the template vars
$tpl =& templateInit();
$tpl->setVariable( 'parameters', $Params );
$tpl->setVariable( 'my_node_image_path', $my_node_image_uri );
$tpl->setVariable( 'my_node_image_width', $my_node_image_width );
$tpl->setVariable( 'my_node_image_height', $my_node_image_height );
$tpl->setVariable( 'my_node_link_url', $my_node_link_url );
 
// END
 
// phpinfo();
eZExecution::cleanExit();
 
?>

References

ezimagealiashandler

Zend

Mon, 10 Dec 2007 07:25:01 GMT

Related extensions

Zend Platform
- Download Server Extension
- Zend Cache Extension
Zend Studio/Neon
- Coding Standard Profile
- Template code for Zend Studio

JavaScript

Mon, 10 Dec 2007 06:34:38 GMT

Ceci est un article Stub. Aidez la communauté: développez-le.

Related extensions

Trim new line template operator