Timeline for Mark deletion on custom fields
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2015 at 14:02 | comment | added | Wordzilla | Not sure if its a bug as in other core modules they set deleted as 1. Thanks for your help :) | |
| Jun 9, 2015 at 14:01 | comment | added | Clive♦ | Correct - maybe that's why that did it? Not sure, I'm not too familiar with the mongo field module | |
| Jun 9, 2015 at 13:38 | vote | accept | Wordzilla | ||
| Jun 9, 2015 at 13:38 | comment | added | Wordzilla |
Thanks @Clive. In the field_purge_batch a condition of deleted = 1 is passed meanwhile the mongodb migrate module sets it as deleted = 2. So the fields will not be deleted right in that case?
|
|
| Jun 9, 2015 at 13:17 | comment | added | Clive♦ |
There's not a lot of config, it happens in field_cron() so that's the best place to start, then have a read through the code and comments of field_purge_batch() (which does the actual deleting)
|
|
| Jun 9, 2015 at 13:00 | comment | added | Wordzilla | Thanks @Clive . Can u please explain the cron script that deletes the data and how its configured and where could I find it? | |
| Jun 9, 2015 at 12:51 | history | edited | Clive♦ | CC BY-SA 3.0 |
added 181 characters in body
|
| Jun 9, 2015 at 12:45 | history | answered | Clive♦ | CC BY-SA 3.0 |