Initial work

Sorry for the dealy, but I have been pretty busy these days. I'll try to give this a look tomorrow.

A quick note while I find the time for a proper review: the project has born as a helper for Translation but will live as an independent project: AAMOF many sites might need node titles behaving as fields besides their multilingual capabilities (e.g. think of HTML titles).

For this reason:

1. I'd change the field name to title_field
2. To answer your latest question: we just need a per-content-type option telling us if we have to attach the field to the bundle. Multilingual options should not influence this. For now we could adopt Field UI's behavior to preserve data consistency: once data has been created we don't allow this setting to be changed anymore.

Well, to make the initial code easier to design and review I'd like having this patch split into smaller ones: first we should focus on the basic behavior (node title replacement), then we can work on integrating other modules. I'd like an issue for each different module so we can discuss every one separately.

That said, here is my first review (to be continued):

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+      'label' => t('Translatable title'),

Please, change this to "Title". As I said before translatability is only one of the benefits we get by having node title as a field. In my mind the replacement should be as transparent as possible to the users.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+      'description' => t('This field stores a translated node title.'),

I'd change this to something like "A field replacing node title."

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+ * @TODO Do we need an index?

Yes, node title has it so I'd say we definitely need one.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+      'description' => 'The language specific title of a entity',

See above.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+/**
+ * Implements hook_entity_info_alter().
+ *
+ * Overwrite the common EntityController of the entity type with the one
+ * from this module.
+ */

This looks pretty complex to me, why not simply using http://api.drupal.org/api/function/hook_node_load/7?

Edit: we might want to check if this feasible by implementing http://api.drupal.org/api/function/hook_field_load/7.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+/**
+ * Implements hook_field_attach_submit().
+ *
+ * @TODO How to make sure this module is the first whichs called?
+ */

Since we need to perform this on node save (no matter if the node comes from a form or an API call) I'd implement http://api.drupal.org/api/function/hook_field_presave/7. This way we are sure that no module implementing http://api.drupal.org/api/function/hook_field_attach_presave/7 can "beat" us. Anyway submit handlers can deal with node titles before, so to be sure we probably need to add a submit handler (as first one) to the node form to and update $node->title also there.

I suggest we should have an API function performing the replacement, something like title_node_sync($node), we can call in both places.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+    $langcode = (strlen($entity->translations->original))? $entity->translations->original: $entity->language;

!empty($entity->translations->original) should be faster. Moreover there must be a white space vefore ? and :.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+    // TODO Hide or remove?

$form['title']['#access'] = FALSE; should be the proper way.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+function title_translation_enabled($bundle) {

title_field_enabled()

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+  return variable_get('translation_title_enabled', FALSE) && module_invoke('translation', 'supported_type', $bundle);

Why can't we just have variable_get("title_field_enabled_$bundle", FALSE)?

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+/**
+* Implements hook_form_FORM_ID_alter().
+*
+* Adds the title settings to the content translation configuration
+*/

Since title field has a more generic scope than just translation we need a configuration in the content type settings form.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+ * Remove default title field and remove settings link from title_field

Isn't there a way to tell the Field UI we don't need a settings link? I don't really like this kind of form manipulation, but if it is the only way let's go with it.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+      $form['fields']['title']

I think we can use http://api.drupal.org/api/function/hook_field_extra_fields_alter/7 to remove node title form field configuration.

+++ title.module	1 Oct 2010 19:56:46 -0000
@@ -1,108 +1,457 @@
+/**
+* Implements hook_form_FORM_ID_alter().
+*/
+function title_form_translation_edit_form_alter(&$form, &$form_state, $form_id) {
+  $form['#submit'][] = 'title_form_translation_edit_form_submit';
+  // TODO Why do we have to define it here? Could we change module translate?
+  if (isset($form['submit']['#submit'])) {
+    $form['submit']['#submit'][] = 'title_form_translation_edit_form_submit';
+  }
+}
+
+/**
+* Function to trigger hook_title_translate().
+*/
+function title_form_translation_edit_form_submit($form, &$form_state) {
+  // Clone the entity to prevent unintentional changes...
+  $entity = clone $form['#entity'];
+
+  // TODO Is this a good idea?
+  $entity->language = $form['#language'];
+  $entity->title = $entity->title_field[$form['#language']][0]['value'];
+
+  module_invoke_all(
+    'title_translate',
+    $form['#entity_type'],
+    $entity,
+    $entity->title_field[$form['#language']][0]['value'],
+    $form['#language']
+  );
+}

I don't get what this code is supposed to do. Would you please explain to me? I ain't sure understand it well, but two things:
1) Translation will depend on this, so if changes are needed over there to reach a better integration, we'll do them.
2) We don't need to care about node language in the translation form, since it can be changed only in the node edit form.

Powered by Dreditor.

Sorry for being vacant, but I have been busy with killing the language system and core translation queues (there are 3-4 issues over there that would benefit from a passionate eye ;). I'll try to give this another look in a couple of days.

First of all: thanks for your work on this! I didn't test it yet, I'd like to have a "commitable" patch first, but here is my (hopefully) last code review:

+++ title.install	12 Oct 2010 20:18:51 -0000
@@ -6,3 +6,30 @@
+  db_delete('{variable}')->condition('name', 'title_field_enabled_%', 'LIKE')->execute();

No need for curly brackets in db_delete.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+/**
+ * Implements hook_hook_info().
+ */
+function title_hook_info() {
+  $hooks['title_translate'] = array(
+    'group' => 'title',
+  );
+  return $hooks;
+}

Can we leave Trigger integration for a later patch?

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  // This fetches the settings from the translation module

Trailing dots are missing from many PHP docs/inline comments.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Add a submit handle to node forms

"handler", missing trailing dot

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  $target_form = '_node_form';
+  if (substr($form_id, strlen($target_form) * -1) == $target_form) {

We can implement title_form_node_form_alter() and remove this check.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+    $bundle = str_replace($target_form, '', $form_id);
+    if (title_field_enabled($bundle)) {

We can use $form['#node']->type here.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Callback for node forms

Should be "Submit handler" instead of "Callback", missing trailing dot.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  if (title_field_enabled($form_state['node']->type)) {

For consistency we could use $form['#node']->type also here.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  if (title_field_enabled($form_state['node']->type)) {
+    // Choose the appropriate language - on insert the original language in
+    // translation is not set!
+    $langcode = (!empty($form_state['node']->translations->original)) ? $form_state['node']->translations->original : $form_state['node']->language;
+
+    // If the original language is changed, change the entity title value too
+    if (isset($form_state['values']['title_field'][$langcode][0]['value'])) {
+      $form_state['values']['title'] = $form_state['values']['title_field'][$langcode][0]['value'];
+    }
+  }

As I was saying, we can make an API function out of this code, I'd say title_field_sync($node, $display = TRUE). We should have a parameter specifiying if we have to use the node language or the current display language (see http://api.drupal.org/api/function/field_language/7). So we don't need that check on $node->translations.

This way in the submit handler we can call title_field_sync((object) $form_state['values'], FALSE).

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * TODO Do we have to synces on $entity->title back to title field too?

No, for now I don't think we need to sync the title back.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  if (title_field_enabled($entity->type)) {
+    // Choose the appropriate language - on insert the original language in
+    // translation is not set!
+    $langcode = (!empty($entity->translations->original)) ? $entity->translations->original: $entity->language;
+
+    // If the original language is changed, change the entity title value too
+    if (isset($entity->title_field[$langcode][0]['value'])) {
+      $entity->title = $entity->title_field[$langcode][0]['value'];
+    }
+  }

Here we can call title_field_sync($entity, FALSE).

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Implements hook_field_attach_form().

I'd move this code into title_form_node_form_alter() so it is not called for each entity form.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Checks if all requirements are meet to enable title translation
+ * @param string $bundle
+ * @return boolean

PHPdocs messed up: for consistency "Checks" should be "Check". We are missing an empty line between the first line and the parameter descriptions, and we are missing also those :)

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Implements hook_field_attach_create_bundle().

Missing empty line.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+function title_form_field_ui_field_overview_form_alter(&$form, &$form_state, $form_id) {

There is no $form_id param here.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  // TODO Why do we have to define it here? Could we change module translate?

Sure, but I don't fully grok the title_translate hook yet, I'll have to test it after we finish the code review.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * TODO Better idea needed - anyone?

I really don't get why we need this.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * TODO Better idea needed - anyone?

We'll change translation to depend on title.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Callback to add / remove title_field instance to a bundle

"Submit handler", missing trailing dot.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * Iterates over all bundles an makes sure the title_field is set correctly

Where do we need this?
Missing trailing dot.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+  // Make sure theres such a field to create a instance of

"there is", missing trailing dot

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+      // TODO There must be a smarter way to do this

node_field_extra_fields() defaults to -5. Perhaps we want to do the same to maintain consistent behavior.

+++ title.module	12 Oct 2010 20:18:52 -0000
@@ -6,3 +6,448 @@
+ * @ TODO Review desperately needed - this is some strange solution :)
+ *
+ * @link http://drupal.org/project/entity_api (perhaps we should be using this)

As I told you before I ain't sure this is the right approach: altering entity info is subject to the same order than implementing hook_field_attach_load() or hook_field_load() (better): other modules could overwrite our entity controller. IMO we should implement hook_field_load() and rely on a low module weight (say -0xFFFFFFFF) to act before any other one. The risk of actually not being the first exists anyway, but we'll have a far simpler code.

Sidenote: I took into consideration Entity API while coding the initial Translation patch, but basically it provides a CRUD API which we don't need atm. I'll keep an eye on it, however.

Powered by Dreditor.

I tested the patch for the first time and it seems we are almost ready to go!

[...] what's about the titles of other entity types? Is there a more general way instead using title_form_node_form_alter()?

My goal for the title project is reaching a stable status ASAP with a basic set of features including strictly the ones needed to make Translation and the "node title as a field" behavior work. Afterwards I'd like to work on a general API allowing to replace any pseudo-field with a regular field for any entity. This would allow us to replace Taxonomy term names, for instance, or comment subjects or bodies.

Hopfully these are my last code-related remarks:

+++ title.info	20 Oct 2010 09:54:54 -0000
@@ -4,5 +4,8 @@
 package = Multilingual

Let's remove this line, I don't know which package we should be using, but Multilingual is misleading.

+++ title.info	20 Oct 2010 09:54:54 -0000
@@ -4,5 +4,8 @@
 dependencies[] = locale
+dependencies[] = translation

Please remove these dependencies, they are unneeded.

+++ title.info	20 Oct 2010 09:54:54 -0000
@@ -4,5 +4,8 @@
+files[] = title.title.inc
+files[] = title.migrate.inc

These files are not present atm.

+++ title.install	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,37 @@
+  db_query("UPDATE {system} SET weight = -0xFFFFFFF WHERE name = 'title'");

Sorry for making a wrong suggestion, but to have a 32 bit representation this should be -0x7FFFFFFF.

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+function title_field_info() {

Probably we are missing some information, see the attached screenshot.

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+ * Add a submit handler to node forms.

" and hide the standard title field."

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+/**
+ * Implements hook_form_FORM_ID_alter().
+ *
+ * Remove default title field and remove settings link from title_field.
+ */
+function title_form_field_ui_field_overview_form_alter(&$form, &$form_state, $form_id) {
+  if (isset($form['fields']['title_field'])) {
+    $form['fields']['title_field']['type']['#markup'] = $form['fields']['title_field']['type']['#title'];
+    $form['fields']['title_field']['type']['#cell_attributes']['colspan'] = 2;
+
+    unset(
+      $form['fields']['title_field']['type']['#type'],
+      $form['fields']['title_field']['type']['#title'],
+      $form['fields']['title_field']['type']['#href'],
+      $form['fields']['title_field']['type']['#options'],
+      $form['fields']['title_field']['widget_type']
+    );
+  }
+}

After testing the patch I don't think we need this: as I was saying before this module will allow to have a regular field replacing node title; this means we will be able to choose the widget to use and set the text processing type (plain/filtered). Instead we want to implement http://api.drupal.org/api/function/hook_field_widget_info_alter/7 to tell the Field API which widget we support (for now just textfield).

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+  if (property_exists($entity, 'title') && title_field_enabled($entity->type)) {

Why property_exists() and not isset(), which should be faster?

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+    // Choose the appropriate language

Missing trailing dot.

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+  // Checkbox to enabled / disabled title field.

"enable/disable". Please remove the whitespaces around the slash.

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+    '#description' => t('If enabled the title is stored as a common instead an extra field.'),

I'd rephrase this: "If enabled node title is stored and behaves as a regular field."

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+/**
+ * Implements hook_field_attach_load().
+ *
+ * TODO Doesn't work for me - seems not called on each load
+ */
+function title_field_attach_load($entity_type, $entities, $age, $options) {
+  foreach ($entities as &$entity) {
+    title_field_sync($entity_type, $entity);
+  }
+}
+
+/**
+ * Implements hook_field_load().
+ *
+ * TODO Doesn't work for me - seems not called on each load
+ */
+function title_field_load($entity_type, $entities, $field, $instances, $langcode, &$items, $age) {
+  foreach ($entities as &$entity) {
+    title_field_sync($entity_type, $entity);
+  }
+}
+

You are right, I did not take into account field cache. We can keep title_field_load(), since it will act before any hook_field_attach_load() implementation when field cache is empty. I think performing synchronization two times in this case should not be a great problem.

+++ title.module	20 Oct 2010 09:54:54 -0000
@@ -6,3 +6,242 @@
+ * TODO The only hook, I know, which works for me as
+ * replacement of the EntityController wrapper

Fine. Let's keep this as the primary way to perform synchronization. We need a comment here explaining what is the intended workflow, I'd say: "Since the result of field_attach_load() is cached, we perform title synchronization also here to ensure that we always have the correct value in $entity->title".

Powered by Dreditor.

I still get errors on node creation and view. I'm using the latest 7.x-1.x-dev and a plain installation with only Title enabled (no Locale, no Translation):

Notice: Undefined index: text_processing in _text_sanitize() (line 325 of E:\www\test\modules\field\modules\text\text.module).

Notice: Undefined index: text_processing in text_field_widget_form() (line 553 of E:\www\test\modules\field\modules\text\text.module).

Moreover we still have some minor string/coding standard issues:

+++ title.info	27 Oct 2010 06:21:31 -0000
@@ -1,8 +1,6 @@
+description = Replaces the node title by a normal field.

I'd say "Replaces with" is more correct.

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+      	'text_processing' => '0',
+  			'max_length' => '255',

Leading tabs instead of spaces.

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+ * @param string $entity_type
+ *  The name of the entity type.
+ * @param object $entity
+ *  The entity to work with.
+ * @param boolean $display
+ *  Specifies if the display- or the node-language is used.

There should be an indentation of 2 spaces between @param and the following line.

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+  // Checkbox to enabled/disabled title field.

"enable/disable"

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+ * Submit handler to add / remove title_field instance to a bundle.

Whitespaces around the slash.

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+ * Enables / disables the title_field on a bundle.

As above.

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+  foreach ($entities as &$entity) {
+    title_field_sync($entity_type, $entity);
+  }
...
+function title_entity_load($entities, $type) {

Let's just call title_entity_load() in title_field_load() .

+++ title.module	27 Oct 2010 06:21:31 -0000
@@ -6,3 +6,223 @@
+  foreach ($entities as &$entity) {
+    title_field_sync($type, $entity);
+  }

Please add a check on the entity type so we avoid the iteration on non-node entity lists.

Powered by Dreditor.

Great work!

Let's give sun the chance to have a final look to this before committing it.

@sun:

As bojanz is pointing out entity_label() won't work for core, we surely can add a label callback to support it, but this should be an additional measure not an alternative to synchronization.

I ain't sure we can fully generalize label handling and extending it to any entity, but if we go this way IMO we should have a basic API to replace any "custom" field with a "regular" field. Title should build on top of this API to handle the particular needs of node titles, which are fairly different from comment subjects, or term or user names, at least in core.

However, the last patch seems to work well, just a couple of issues: the title field should be hidden in the display settings by default, moreover title does not show up in node preview (full version). I found a few coding standard issues left:

+++ title.install	12 Nov 2010 19:04:27 -0000
@@ -6,3 +6,44 @@
+  // Make sure the title is properly handled before any other module
+  // access it.

Comment does not wrap at column 80.

+++ title.module	12 Nov 2010 19:32:59 -0000
@@ -3,6 +3,228 @@
+        'field_name' => 'title_field',
+        'type' => 'title',
+        'cardinality' => 1,
+        'translatable' => TRUE,
+        'locked' => TRUE,

Wrong indentation.

+++ title.module	12 Nov 2010 19:32:59 -0000
@@ -3,6 +3,228 @@
+ * synchronization also here to ensure that we always have the correct
+ * value in $entity->title.

Comment does not wrap at column 80.

Powered by Dreditor.

Working on Field UI/entity_label() integration to see what we can get.

@klonos:

About 1) see http://drupal.org/node/924968#comment-3516774.

We might have hit a core bug here(?).

I guess we had. It would be nice if you could investigate a little more about this and possibly open a core issue (please link it here if you do).

I haven't found the time for this yet, but I will in a few days. Don't lose hope ;)

I didn't write any line of code yet, if you want to try to work on this be sure to post an interdiff between your patch and #27.

Here is a partially working patch extending the Field UI to support any entity. As per #31 the patch introduces a field replacement API that can be used on any legacy pseudo-field (there is a docblock describing it in some more detail). entity_label() support is still TODO.

The main change wrt the previous patch is that the replacement field is provided through an hook for each legacy pseudo-field and can be managed through the Field UI as any other: when a lpf is replaced with a regular field, it disappears from the field overview form and gets back when the replacing field instance is removed.

If the direction is good I'll provide a complete patch implementing syncing and form massaging for any entity.

Please don't make a code style review, the patch is a huge mess from that POV and actually is needs work, just evaulte the direction taken.

Here is the full patch implementing form massaging and synchronization for any entity. Comments and documentation should be ok too.

Please let me know what you think about this, because I'd really like to have a testable dev snapshot in a few days.

entity_label() support is still TODO because IMO we have bug in the API: the label callback function is called without specifying the entity type (just the entity), which makes impossible to achieve a generalized label handling. Probably we need to file a core issue to fix this.

There were some trailing whitespaces all around.

Thanks to git people wishing to review/test some up-to-date code can have a look to the initial_work-924968 issue branch.

At the moment I'm working on some simple tests for the code recently added (mainly integration with the Entity API and support for the 'label callback' entity key).

I'm hoping to post a patch here soon for a final review.

Ok, here is what I came up with after talking with sun, fago and rfay in Chicago.

The approach is not that much different from the one posted in #41:

• the current patch introduces a dependecy from the Entity API module, mainly to generalize the entity language handling;
• sun expressed some concerns about the fragility of the synchronization approach, I tried to address them by reversing part of the synchronization workflow: on load/view/submit field values are put into the legacy fields, instead on (pre)save field values are pulled from the legacy fields and synchronized back into fields; since title is supposed to act as the very first module on hook invocation, we cannot be sure that other presave hook implementations acting on the legacy fields do not get field values out of sync: for this reason field values are checked again after legacy field values are stored and get stored again if needed;
• as previously discussed with fago, synchronization is now static cached as it can be performed on hook_field_attach_load, hook_entity_load, hook_entitycache_load (see #1089130: Allow modules to act on any entity type) and hook_entity_prepare_view (see #1089174: Prepare view hooks do not receive the language parameter);
• we now have entity_label() integration for any entity replacing its label with a field; this is currently disabled due to #1096446: entity_label() is not passing along the $entity_type parameter.

If there is any other pending concern please let me know soon because I'd wish to release a development snapshot in a week, so more people can start testing this and we can start opening individual issues to polish things.

I forgot: we have tests now!

@sun:

Somehow related issue: #1099162: Is commit tracking for unofficial branches/tags intended?.

Let's try again.

Probably we need to commit an initial patch first. The attached one ships some small improvement on comments/phpdocs.

Committed the attached patch to HEAD!

A development snapshot will be available in 12 hours.