Namespace Conflicts

There is a markup module floating around (http://drupal.org/node/83787) that adds a CCK field to add markup. This is a good alternative to the form_markup module whenever you need to do field privacy and don't want your markup to be tied to another field but stand alone as it's own field instead.

In comment #10 of the issue linked above you can see a d5 version of the module which uses form elements named 'markup' which ends up breaking the form_markup module since it is looking for 'markup' elements as well. Comment #12 fixes this by changing the 'markup' elements in markup.module to 'text_markup' elements, but I think a more appropriate fix would be for form_markup.module to be looking for 'form_markup' elements.