inceweb

Me too. Issue is incorrectly marked as resolved, OP actually extended their CSS to workaround.
The issue first appears in version 1.57 which is why foomep’s site (and ours) works ok with v1.56
There are a lot of changes between these versions, and unfortunatley the changelog.txt disappears at v1.57
However, I have diff-ed a number of files and I think that the problem arises in functions.php at line 89. If I revert:
wp_enqueue_style( ‘hemingway_style’, get_template_directory_uri() . ‘/style.css’ );
back to:
wp_enqueue_style( ‘hemingway_style’, get_stylesheet_uri() );
the child theme CSS is correctly loaded.
I’m not saying that this is necessarily the solution, but the problem definitely relates to the child style.css not being correctly enqueued.

bookchiq is correct – this is still a bug in 2.2.2
The problem arises when the user clicks “Add custom field” before a page has been saved using the “Save and continue editing” or “Save” buttons or the autosave.
As described by HopkinsProg above, a post is created instead of a page, and the page content including custom fields is lost.
I suspect that the fix would be to force the save action when the “Add custom field” button is clicked, somewhere in admin-functions.php
The workaround, as described above, is to save the page before trying to add custom fields.