Okay, I got the issue; it was #access. I must have mis-read API docs where I thought #access meant "hide it from those with no access". On 5 February 2015 at 14:02, Erik Stielstra <info@erikstielstra.nl> wrote:
As I said "I can not reproduce your problem” and what I can’t reproduce I can not fix.
I would go looking for working examples. You can try the examples module. It has a.o. an entity- and a field example module. You can also try to add a field via the interface and then export its code using features. That will give you some PHP-code that should almost be what you need to create a field programatically.
Erik Stielstra
On 5 feb. 2015, at 12:51, Muzaffer Tolga Ozses <tolga@ozses.net> wrote:
This is what happens when I re-install the module:
https://dl.dropboxusercontent.com/u/11918318/Screenshot%20from%202015-02-05%...
On 4 February 2015 at 13:16, Muzaffer Tolga Ozses <tolga@ozses.net>
wrote:
Not the field label, field name.
On 4 February 2015 at 13:15, Erik Stielstra <info@erikstielstra.nl> wrote:
On 4 feb. 2015, at 10:15, Muzaffer Tolga Ozses <tolga@ozses.net> wrote:
Thank you Eric for replying,
Like I said, this started happening after I renamed the field. Could this be why? I don’t know. You should not rename a field (change machine name) unless you know exactly what you are doing. Just create a new one. Changing the field label should not have this effect.
Erik Stielstra
-- mto
-- mto
-- mto