Just found this description of the problem, in which the issue is traced to an ambiguity in the HTML spec rather than a definite Firefox bug:

http://weblog.200ok.com.au/2008/01/dashing-into-trouble-why-html-comments.html

I do think that the Elgg source needs to be careful to delete HTML code that may contain user generated content rather than simply commenting it out.

After all, the content *could* have contained the string "-->" which then would have broken the layout in any browser.

I put the comment issue in Trac here:

http://trac.elgg.org/elgg/ticket/882

thanks Kevin

Just found this description of the problem, in which the issue is traced to an ambiguity in the HTML spec rather than a definite Firefox bug:

http://weblog.200ok.com.au/2008/01/dashing-into-trouble-why-html-comments.html

I do think that the Elgg source needs to be careful to delete HTML code that may contain user generated content rather than simply commenting it out.

After all, the content *could* have contained the string "-->" which then would have broken the layout in any browser.

I put the comment issue in Trac here:

http://trac.elgg.org/elgg/ticket/882

thanks Kevin

Just found this description of the problem, in which the issue is traced to an ambiguity in the HTML spec rather than a definite Firefox bug:

http://weblog.200ok.com.au/2008/01/dashing-into-trouble-why-html-comments.html

I do think that the Elgg source needs to be careful to delete HTML code that may contain user generated content rather than simply commenting it out.

After all, the content *could* have contained the string "-->" which then would have broken the layout in any browser.

I put the comment issue in Trac here:

http://trac.elgg.org/elgg/ticket/882

thanks Kevin

Just found this description of the problem, in which the issue is traced to an ambiguity in the HTML spec rather than a definite Firefox bug:

http://weblog.200ok.com.au/2008/01/dashing-into-trouble-why-html-comments.html

I do think that the Elgg source needs to be careful to delete HTML code that may contain user generated content rather than simply commenting it out.

After all, the content *could* have contained the string "-->" which then would have broken the layout in any browser.

I put the comment issue in Trac here:

http://trac.elgg.org/elgg/ticket/882

thanks Kevin

Just found this description of the problem, in which the issue is traced to an ambiguity in the HTML spec rather than a definite Firefox bug:

http://weblog.200ok.com.au/2008/01/dashing-into-trouble-why-html-comments.html

I do think that the Elgg source needs to be careful to delete HTML code that may contain user generated content rather than simply commenting it out.

After all, the content *could* have contained the string "-->" which then would have broken the layout in any browser.

I put the comment issue in Trac here:

http://trac.elgg.org/elgg/ticket/882

thanks Kevin

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

@Andy

best way for right now would be to read thru the OpenDD.php code with referencing the OpenDD specs.. ;-)

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

Known issue: http://trac.elgg.org/elgg/ticket/857

@Cash,

thx re: trac..

I had noticed -- correct handlers and views,  code -- actually exist w/ the "status" <select> -- just not triggered when click on "Edit Topic" ==> edit contents ;-)

( I ought to read /trac more myself ;-)

@Dave

don't post raw elgg code -- not everyone is multi-lingual ! ;-) b/c they doan read the doxygen'd api docs ;-)

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

@Andy

best way for right now would be to read thru the OpenDD.php code with referencing the OpenDD specs.. ;-)

@ Chalkiex

I've found mention of a different solution here:

http://priit.pudisoo.com/2009/03/elgg-15-and-missing-message-board/

However, I still can't reduce the size of the input box even with that suggestion.
Let me know if you find a solution

Thanks,
Ugo

@ Chalkiex

I've finally managed to fix it, contact me if you still have problems.

Hi Ugo! How did you squeeze the message box back into the right space?

Thanks!

Sean

Known issue: http://trac.elgg.org/elgg/ticket/857

@Cash,

thx re: trac..

I had noticed -- correct handlers and views,  code -- actually exist w/ the "status" <select> -- just not triggered when click on "Edit Topic" ==> edit contents ;-)

( I ought to read /trac more myself ;-)

@Dave

don't post raw elgg code -- not everyone is multi-lingual ! ;-) b/c they doan read the doxygen'd api docs ;-)

nope ;-)

All Elgg manipulation is handled via the c*lasses and *methods provided by ELgg

From your comments - I think you're thinking "add a field here, there.." -- cannot do that in Elgg

To help get you started in getting Elgg wrapped arround your head.. ;-) for example -- read thru these pieces of code which relates to "send a message"

/mod/messages/actions/send.php

line -  
$result = messages_send ($title, $message_contents,$send_to,0,$reply);
calls the actual message send rotuine

/mod/messages/start.php
code from// Initialise a new ElggObject
thru ==
$success = $message_to->save();

triggers the actual database write method

engine/lib/objects.php

public function save()
{
// Save generic stuff
if (!parent::save())
    return false;
    // Now save specific stuff
    return create_object_entity($this->get('guid'), $this->get('title'), $this->get('description'), $this->get('container_guid'));
}

create_object_entity
is about the final call after which your data has been written to database 
- no sql call to write involved for you.

I have some fair amount of my time preparing these notes for you to help yourself guide yourself,

I hope you spend some fair time too ;-)

cheers.

Ok I think I understand most of your example above.  I see the function that writes it to the database. Now the ? is do I need to manually create a new field in the database before trying to write something to that field?  I think that is where I am still confused.

So for the example of saving the coppa data to teh database. I think I know how to have the function write it to the database but if there is no exisiting field in the database what happens when the command  to write the coppa data is called ?

Thank you for your examples above. That is something that I have been needing.

read the source, David ;-)

Some really interesting reading --

• http://docs.elgg.org/wiki/Engine/DataModel
• http://docs.elgg.org/wiki/Engine/DataModel/Metadata

Read these over and over.. once you have a grip on the ELgg DataModel, you'll  forget php's mySql_xxx calls

Known issue: http://trac.elgg.org/elgg/ticket/857

@Cash,

thx re: trac..

I had noticed -- correct handlers and views,  code -- actually exist w/ the "status" <select> -- just not triggered when click on "Edit Topic" ==> edit contents ;-)

( I ought to read /trac more myself ;-)

@Dave

don't post raw elgg code -- not everyone is multi-lingual ! ;-) b/c they doan read the doxygen'd api docs ;-)