can't set field default value to null?

Originally, I thought there had to be at least [gmap ]. But you are right, there should be the ability to have nothing.

fixed in dev version.

nope - reopening: i am now *unable* to save a default macro for a CCK gmap field (odd) - works when manually entered in node, but default can not be saved...

perhaps a leave as default with a little ajaxy 'empty this' button to wipe text?

@zilla

The button is a little unnecessary.

I will look into this soon. I want to integrate some SimpleTests into this module as well, so that I can easily see these problems. And testing is awesome.

i hear you on the button, just meant that if this is 'by design' then there should be an easy way for users to erase it without having to read a text instruction placed by admin like 'if you don't want to be on the map...'

still not seeing any entered "default value" appear in the node add process - is this by design??? for now i just do a manual cut and paste of a macro each and every single time which is not a realistic thing to present to users (fine for admin, though tedious)

Just to clarify, you are using the CCK Default Field field when creating the CCK field? Every CCK Field allows for defaults. It is usually collapsed by default.

yes, i paste the macro into the default field (where the default macro is to be placed) and then when i go to create a node with the field it is still empty....

@zilla

Sorry. I am currently writing tests for this module, and for myself for the first time, so its a learning experience. This will allow a lot easier maintainability and stability for the module. I will update as soon as my time allows.

@zzolo - thanks! glad that you're working on it period, figure a fix will come eventually - otherwise the field works just fine!

New dev version should have default problems fixed in it. Probably wont show up as a release until tomorrow.