Re: Re: customMetaData not saving

Hello Scott,

Thanks for your reply.

Then it seems that it's a bug. Since, it has been reported a long time ago, 
I'm assuming that it's a known issue and that it will be fixed at some 
point in the future. Could somebody from Google confirm that?

In case someone is interested, I too worked around it by saving the 
metadata json as a data-url encoded url in a meta tag in the body. E.g.,

<meta name="metaData" 
content="data:application/json;charset=utf-8,%7B+foo%3A+%22test+string%22+%7D">

This is of course a suboptimal solution since you always need to download 
the whole body in order to read a post's metadata.

Giannis

On Thursday, April 9, 2015 at 10:23:09 AM UTC+9, Scott Arthur wrote:
>
> Hi Giannis
>
> I don't think we did ever get the meta-data issue solved, I think I ended 
> up working around it instead.
>
> Scott
>
> On 3 April 2015 at 18:52, Giannis Georgalis <[email protected] 
> <javascript:>> wrote:
>
>> Hello Scott,
>>
>> Did you find what was wrong with customMetaData not persisting?
>>
>> It doesn't work for me neither via the .NET API nor the web-based Google 
>> API Explorer.
>>
>> Thank you,
>> Giannis
>>
>>
>> On Friday, April 11, 2014 at 12:12:56 PM UTC+9, Scott Arthur wrote:
>>>
>>> Brett, should the customMetaData for posts be working?
>>>
>>> I can't seem to get it work at all now through the rubygem or through 
>>> the API explorer.
>>>
>>> I have tried both escaping the string myself and leaving it to be 
>>> escaped by the gem/explorer and nothing seems to work now, I just cannot 
>>> get it to persist despite a 200 response.
>>>
>>> Is there any particular attribute of the post resource that must be 
>>> present for this to work?
>>>
>>> On Tuesday, 18 March 2014 12:53:40 UTC+11, Scott Arthur wrote:
>>>>
>>>> I'm trying to add customMetaData to posts via the API and it is not 
>>>> saving.
>>>>
>>>> Weirdly, it did work for me when I first tried it and now it doesn't 
>>>> seem to work at all.
>>>>
>>>> I have tried via both the API Ruby gem and via the API explorer.
>>>>
>>>> This is the request and response that I got via my latest test in the 
>>>> API explorer:
>>>>
>>>> PUT https://www.googleapis.com/blogger/v3/blogs/XXXXXX/posts/XXXXXX?key={YOUR_API_KEY}
>>>>
>>>> Content-Type:  application/json
>>>> Authorization:  Bearer XXXXXXXX
>>>> X-JavaScript-User-Agent:  Google APIs Explorer
>>>>
>>>> {
>>>>  "kind": "blogger#post",
>>>>  "id": "XXXXXX",
>>>>  "blog": {
>>>>   "id": "XXXXXX"
>>>>  },
>>>>  "published": "2014-03-17T16:35:00-07:00",
>>>>  "updated": "2014-03-17T18:43:15-07:00",
>>>>  "url": "X <http://monash-science-blog-dev.blogspot.com/2014/03/up-in-sky-its-nuclear-explosion.html>XXXXXX",
>>>>  "selfLink": "X <https://content.googleapis.com/blogger/v3/blogs/948315869216243850/posts/7366190412128718208>XXXXXX",
>>>>  "title": "Post Title",
>>>>  "content": "X",
>>>>  "author": {
>>>>   "id": "XXXXXXX",
>>>>   "displayName": "Scott Arthur",
>>>>   "url": "http://www.blogger.com/profile/10485462634315144000",
>>>>   "image": {
>>>>    "url": "http://img2.blogblog.com/img/b16-rounded.gif"
>>>>   }
>>>>  },
>>>>  "replies": {
>>>>   "totalItems": "0",
>>>>   "selfLink": "XXXXXXX"
>>>>  },
>>>>  "labels": [
>>>>   "Physics"
>>>>  ],
>>>>  "status": "LIVE",
>>>>  "customMetaData": "{\"key\": \"value\"}"
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>> {
>>>> "kind": "blogger#post",
>>>> "id": "XXXXXX",
>>>> "blog": {
>>>> "id": "XXXXXX"
>>>> },
>>>> "published": "2014-03-17T16:35:00-07:00",
>>>> "updated": "2014-03-17T18:44:50-07:00",
>>>> "url": "XXXXXX",
>>>> "selfLink": "XXXXXX",
>>>> "title": "Post Title",
>>>> "content": "X",
>>>> "author": {
>>>> "id": "XXXXXX",
>>>> "displayName": "Scott Arthur",
>>>> "url": "XXXXXX",
>>>> "image": {
>>>> "url": "http://img2.blogblog.com/img/b16-rounded.gif"
>>>> }
>>>> },
>>>> "replies": {
>>>> "totalItems": "0",
>>>> "selfLink": "XXXXXX"
>>>> },
>>>> "labels": [
>>>> "Physics"
>>>> ],
>>>> "status": "LIVE"
>>>> }
>>>>
>>>> I also double checked that the customMetaData is not an ADMIN only 
>>>> detail via the posts.get ADMIN view and it is just not there.
>>>>
>>>> Is this a bug or am I missing something?
>>>>
>>>> Scott
>>>>
>>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Blogger Developer Group" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/bloggerdev/up3zqBUdFj4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/bloggerdev.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Scottatron | AU Mobile +61428911882 | NZ DDI +6498892394 | skype scottatron
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/d/optout.