Upon Exporting:

- I see a message that I need to rebuild permissions, i think this is not the proper time to show such a message.

- Also the exported object does not retail the access settings for the respective cck field, i.e. I have to reconfigure the permissions after importing !!

All in all, Very Nice Module .

Comments

danielb’s picture

- I see a message that I need to rebuild permissions, i think this is not the proper time to show such a message.

I don't decide when the message shows, only whether permissions needs to be rebuilt, which is usually after you submit the config.

- Also the exported object does not retail the access settings for the respective cck field, i.e. I have to reconfigure the permissions after importing !!

Yeah I don't attach the settings to the content type :/ I'll have a think about it.

danielb’s picture

Hmm looking at the content_field_edit_form_submit() code, it seems like it should automatically attach? I will have to investigate.

danielb’s picture

ok it does actually export/import but the settings used in the form and this module do not look at those settings in the default storage, they look at a custom storage place.
So this does need a rethink.
Either we start relying on the default storage of the settings - and theres a few things to weigh up in regards to that, or find a bandaid solution for this specific problem.

bakr’s picture

All in all, it is not that major, except for projects which rely heavily on these features.

As far as the import and export is done, that is more than half-way through.

danielb’s picture

Status: Active » Closed (won't fix)

Looks like this won't be fixed. I'm focusing development on drupal 7 and backporting where convenient. In Drupal 7 the ability to export/import content types appears to be removed so it feels even less like it's worth working out how to do.
I would still like to improve the way settings are stored one day, but it won't happen in Drupal 6.