I’ve confirmed this is an issue on a fresh install of both 1.6.4 and 1.6.6. Data sent in either the mt_text_more or mt_excerpt fields via the MetaWeblog api is not saved to the database, nor is it returned when downloading posts if those fields are manually updated in the web admin.

Data sent in the description field, however, is saved and displayed, so I’m fairly sure this is not a problem with my configuration.

I can confirm that I have also been having this issue.

( I have not yet checked out the latest build to see whether the API was returning the correct Permalinks, but I was very happy to see that this was addressed in the latest build because I have had to apply a work-around in the past. )

What application are you using to set the custom field(s) (or fail to set as the case may be).  I’m trying to replicate, but not terribly up on the editors.

Aha- I tested a bit with ecto.  On that one- make sure when you set things up, you choose ‘MoveableType’ as the system/api.  MoveableType and Metaweblog are both the metaweblog module, but on some clients (all clients?) if you set to MT the client send/recieve the information for the custom fields as per the Metaweblog module settings.

I believe this boils down to the client settings.  Does this look to be the case?

Robin is correct, if the editor offers MT, select it instead of Metaweblog, as the standard Metaweblog implementation does not have the extra fields that the MT extended version of the Metaweblog implementation has.

Thread is suspending due to lack of feedback.  To reopen the issue for consideration, please use the button at the top or bottom of the thread to create a new related topic.