If the {{/path/to/config.xml}} to substitute {{config1.xml}}, then everything works correctly. But if you substitute {{config2.xml}} error

Notice: Trying to get property of non-object in D:\www\index.php on line 7

How can I iterate all items {{file}}, if their number is not known in advance (one or more than one)?

Comments

Posted by Rob Allen (rob) on 2009-04-05T12:04:41.000+0000

Can't fix at Zend_Config level. Workaround is to use UTF8 files without a BOM marker.

Posted by Rob Allen (rob) on 2009-04-05T12:12:32.000+0000

(Closed wrong issue!)

Posted by Rob Allen (rob) on 2009-04-05T12:19:40.000+0000

I'm not sure there's any way to resolve this issue due to the other than creating a dummy key to force an array:

<?xml version="1.0" encoding="utf-8" ?>

might work, but don't forget to test for id being null.

Posted by Patrick van Dissel (tdm) on 2009-09-03T00:56:22.000+0000

This issue also exists when using the toArray() method of Zend_Config.
The problem is that you just want the array to ALWAYS have the same layout.
Config files tent to grow and be extended, just like XML files.

In my opinion the Zend_Config API should work the same as the of SimpleXml, here two extended examples and their output:
h2. Using SimpleXML

And then just work with the $files variable as array. That works pretty well.

Posted by Wim Godden (wimg) on 2011-04-28T14:25:29.000+0000

Although this is fixable, fixing it will always break backwards compatibility.
When a developer knows there's only 1 item, code such as this will be broken :

echo $config->files->file['id'];

Because it will in fact have to become :

$file = $config->files->file->toArray();
echo $file[0]['id'];

I would advise against modifying this for ZF 1.x - not sure how this will be handled in ZF 2, but introducing this backwards incompatibility is not a good idea in any case...

The only other option is to modify just the magic/fluent notation, but that will make things complicated and will cause inconsistency between fluent notation and array notation, which should be avoided.

Posted by Rob Allen (rob) on 2011-04-28T14:47:51.000+0000

One idea I have had is to introduce a children() method that always returns an iterator/array regardless of whether there is is one or many children: