|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Monday 05 April 2010 3:14:20 pm
I keep having to refer to the online docs to see what '1' and '2' mean in the admin <select> menus. As a suggestion, could the text-labels for each <select> menu for this extension be improved:
* Use "Multiple files (N-Mode)" instead of just 'n' as label in admin "Slicing mode" <select> menu
* Use "Single file (1-Mode)" instead of just '1' as label in admin "Slicing mode" <select> menu
* Use "Relations not exported, referenced only (Level 1)" instead of just '1' as label in admin "Related object handling" <select> menu
* Use "Relations exported (Level 2)" instead of just '2' as label in admin "Related object handling" <select> menu
Cheers
Russ
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Monday 05 April 2010 5:51:42 pm
A minor adjustment: When removing individual exports from a channel, I was expecting the related contents of the 'export' directory to be deleted too. Failing that, a prompt that asks the user " Delete all export-related files from 'export' directory?"
Also: Not sure why the same extension directory structure ('/extension/ezxmlexport/exports/xml/') is re-created when an export is created: /ezpublish/extension/ezxmlexport/exports/xml/my-export/extension/ezxmlexport/exports/xml/
Might it be less complex to create it in:
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Sunday 11 April 2010 7:23:18 pm
When previewing an export, it would be very handy to add a third button at the bottom: "Edit this Export". That would save a couple of clicks going back to the export channel list and selecting the 'Edit' link again.
Cheers
Russell
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Monday 12 April 2010 4:02:25 pm
The XSL stylesheet bundled with this extension is empty. It would be useful for those new to XSL and what it does to supply an example - e.g. transforming the default XML into the simple XML format understood by the excellent data_import extension.
Regards,
Russell
[UPDATE]
Here is a functioning XSL stylesheet which I have (very basically) tested, which transforms native ezxmlexport XML to native data_import (extension) XML format. I have updated it with the <xsl:output> element. Using the cdata-section-elements="field" means that all our transformed XML will be enclosed in <![CDATA[ ]]> blocks. Not sure of the ramifications of this being used for *all* fields yet but I'll keep an eye out:
|
|
|
Nicolas Pastorino
Member since:
09 January 2008
Posts: 22
|
Monday 19 April 2010 12:56:12 am
Thanks Russell, this is very useful !
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Monday 19 April 2010 1:22:28 pm
By default ezxmlexport will only export the *child nodes* of the parent node you select after pressing the "Choose Contents" button.
I had simply assumed that the node I selected would be exported along with its sub-tree which is not the case.
This situation could be improved I think:
1) If not already, the docs could make sure this is made clear.
2). An additional form-widget in the export interface labeled: 'Export Behaviour' with option1: 'default' and option2: 'complete' - where 'default' is the behavior as it is now, and 'complete' includes the parent directory the user selects when choosing his content. This could even simply be an .ini setting.
Cheers
Russ
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Wednesday 21 April 2010 4:57:33 pm
I believe I have found a bug:
1). Setup an export within a channel and set its "Related object handling" to 1.
2). Run the export #> php runcronjobs.php -s <siteaccess> ezxmlexport
3). Copy the exported .xml file somewhere as relations_1.xml
4). Modify the same export and set its "Related object handling" to 2.
5). Run the export #> php runcronjobs.php -s <siteaccess> ezxmlexport.
6). Copy the exported .xml file somewhere as relations_2.xml
7). diff the two. Nothing has changed except the value of the <export_date> element.
Cheers
Russ
|
|
|
Russell Michell
Member since:
06 April 2008
Posts: 14
|
Wednesday 21 April 2010 5:42:27 pm
Another bug I think - in the logging XML:
The log XML format will be invalid due to the <appliedxslttransformation></appliedxslttransformation> element being empty (in my case anyway).
I am using the stylesheet posted above but there is no content for the <appliedxslttransformation> element. If this is meant, shouldn't a self-closing element be used in its place? <appliedxslttransformation/>
Cheers
Russ
|
|
