Saving ezxmltext through ajax

Next topic

Author	Message
Sao Tavi	Thursday 16 June 2011 12:37:16 pm I tried to create something like an autosave feature for an ezxmltext, but I soon found out that it is not that easy to save the new data into the db in the correct format. I tried looking at ezxmltext datatype for getting help, but after several hours I gave up. So... if I have in php the contents from a tiny mce editor and the contentObjectAttribute, how can I save them into the database in the right format? What I did was either stripping the images or a lot of other things that were not right. Oh, and just as a note: something strange happened, when trying to add images to the xml text I was getting some errors (like 'ez publish "A file is required for upload, no file were found. No HTTP file found, cannot fetch uploaded file.') . Trying to find out the problems origins, without changing anything, it magically solved by itself after several tries and checking this on another ez publish install on the same server... Unfortunately, I cannot reproduce it. PS: The redirection system is not good when using multiple tabs on the same ez publish installation. Maybe it should use post variables instead of cookies? I believe I should post this in the issues tracker.
Sao Tavi	Thursday 16 June 2011 2:54:24 pm With a little bit of help, I found the answer eventually. It seems that I needed to use the parser from ezoe, it works with no problems now. Here is the code used: $parser = new eZOEInputParser( ); $parser->setParseLineBreaks( true ); if (!$document = $parser->process( $http->postVariable('val') )) return 'failed to parse'; // Create XML structure $xmlString = eZXMLTextType::domString( $document ); $options['description']->setAttribute('data_text', $xmlString); $options['description']->store();

Author

Message

Thursday 16 June 2011 12:37:16 pm

I tried to create something like an autosave feature for an ezxmltext, but I soon found out that it is not that easy to save the new data into the db in the correct format. I tried looking at ezxmltext datatype for getting help, but after several hours I gave up.

So... if I have in php the contents from a tiny mce editor and the contentObjectAttribute, how can I save them into the database in the right format?

What I did was either stripping the images or a lot of other things that were not right.

Oh, and just as a note: something strange happened, when trying to add images to the xml text I was getting some errors (like 'ez publish "A file is required for upload, no file were found. No HTTP file found, cannot fetch uploaded file.') . Trying to find out the problems origins, without changing anything, it magically solved by itself after several tries and checking this on another ez publish install on the same server... Unfortunately, I cannot reproduce it.

PS: The redirection system is not good when using multiple tabs on the same ez publish installation. Maybe it should use post variables instead of cookies? I believe I should post this in the issues tracker.

Sao Tavi

Thursday 16 June 2011 2:54:24 pm

With a little bit of help, I found the answer eventually. It seems that I needed to use the parser from ezoe, it works with no problems now.

Here is the code used:

                $parser = new eZOEInputParser( );
                $parser->setParseLineBreaks( true );

                if (!$document = $parser->process( $http->postVariable('val') ))
                    return 'failed to parse';

                // Create XML structure
                $xmlString = eZXMLTextType::domString( $document );

$options['description']->setAttribute('data_text', $xmlString);
$options['description']->store();

eZ debug

Timing:	Jan 18 2025 01:55:53
Script start
Timing:	Jan 18 2025 01:55:53
Module start 'layout'
Timing:	Jan 18 2025 01:55:53
Module start 'content'
Timing:	Jan 18 2025 01:55:54
Module end 'content'
Timing:	Jan 18 2025 01:55:54
Script end

Main resources:

Total runtime	1.1345 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	587.9141	152.6250
Module start 'layout'	0.0058	0.0034	740.5391	39.4531
Module start 'content'	0.0093	1.1235	779.9922	428.9844
Module end 'content'	1.1328	0.0016	1,208.9766	8.1641
Script end	1.1344		1,217.1406

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.2815	16	0.0002
Check MTime	0.0014	0.1209	16	0.0001
Mysql Total
Database connection	0.0007	0.0585	1	0.0007
Mysqli_queries	1.0901	96.0917	52	0.0210
Looping result	0.0005	0.0424	50	0.0000
Template Total	1.1031	97.2	2	0.5515
Template load	0.0021	0.1863	2	0.0011
Template processing	1.1010	97.0457	2	0.5505
Template load and register function	0.0005	0.0481	1	0.0005
states
state_id_array	0.0013	0.1133	1	0.0013
state_identifier_array	0.0014	0.1275	2	0.0007
Override
Cache load	0.0016	0.1431	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0636	1	0.0007
Fetch class attribute name	0.0011	0.0995	2	0.0006
XML
Image XML parsing	0.0001	0.0116	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0005	2	0.0000
General
dbfile	0.0023	0.2012	10	0.0002
String conversion	0.0000	0.0010	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 10 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs