HTMLarea and Classes

Next topic

Author	Message
alain boudard	Thursday 10 February 2005 2:21:54 am Hi 1. I try to find a way to integrate htmlarea 3 to my current EZP 3.5 website. I could not find a simple tutorial to reach my point, could anybody provide me some hints about this implementation ? 2. I tried to modify my Article Class, I wanted to change the "Body" field from XML to text. I kept the same name, but now the body field has a new ID and I don't see the content of it in any of my Articles... is there a way to go back or to display the values I previously filled in the XML Body field ? Thank you for any help Alain
Deane Barker	Thursday 10 February 2005 7:54:40 am 1. I think it's going to be tough to get help on this one. eZ sells their online editor for $300 or so, so I doubt anyone is going to be very interested in helping you integrate htmlarea. At any rate, it would involve creating a new datatype, which is tricky. 2. Yep, changing datatypes is a monster of a problem. If you change the type of a field (delete the old one and insert a new one), all the content goes with it. The fields are keyed by ID, not name (identifier). Someone correct if I'm wrong on point #2, but that's my understanding of it.

Author

Message

Thursday 10 February 2005 2:21:54 am

1. I try to find a way to integrate htmlarea 3 to my current EZP 3.5 website.
I could not find a simple tutorial to reach my point, could anybody provide me some hints about this implementation ?

2. I tried to modify my Article Class, I wanted to change the "Body" field from XML to text. I kept the same name, but now the body field has a new ID and I don't see the content of it in any of my Articles... is there a way to go back or to display the values I previously filled in the XML Body field ?

Thank you for any help
Alain

Deane Barker

Thursday 10 February 2005 7:54:40 am

1. I think it's going to be tough to get help on this one. eZ sells their online editor for $300 or so, so I doubt anyone is going to be very interested in helping you integrate htmlarea. At any rate, it would involve creating a new datatype, which is tricky.

2. Yep, changing datatypes is a monster of a problem. If you change the type of a field (delete the old one and insert a new one), all the content goes with it. The fields are keyed by ID, not name (identifier).

Someone correct if I'm wrong on point #2, but that's my understanding of it.

eZ debug

Timing:	Jan 18 2025 18:23:54
Script start
Timing:	Jan 18 2025 18:23:54
Module start 'layout'
Timing:	Jan 18 2025 18:23:54
Module start 'content'
Timing:	Jan 18 2025 18:23:54
Module end 'content'
Timing:	Jan 18 2025 18:23:54
Script end

Main resources:

Total runtime	0.0257 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	587.9141	152.6250
Module start 'layout'	0.0054	0.0030	740.5391	39.4453
Module start 'content'	0.0084	0.0148	779.9844	89.3359
Module end 'content'	0.0232	0.0025	869.3203	30.3047
Script end	0.0257		899.6250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	9.9275	14	0.0002
Check MTime	0.0012	4.5360	14	0.0001
Mysql Total
Database connection	0.0007	2.8546	1	0.0007
Mysqli_queries	0.0025	9.8692	3	0.0008
Looping result	0.0000	0.0583	1	0.0000
Template Total	0.0018	7.1	1	0.0018
Template load	0.0010	4.0230	1	0.0010
Template processing	0.0008	3.1036	1	0.0008
Override
Cache load	0.0006	2.5092	1	0.0006
General
dbfile	0.0045	17.6153	8	0.0006
String conversion	0.0000	0.0324	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs