I am currently experimenting with some Rental Car Reservation Email Schema and also Go-To Action Email Markup. About a year ago, I played around with the code and used Apps Script Quickstart Guide to test the markup. The tests worked as expected and I was getting all sort of great results in email. Specifically, I was seeing action buttons and, when in Google Inbox, all sorts of cool treatments of the reservations. I also saw my tests come through on "my car rental" queries in Google.
Today, I went ahead and redid my test, and some of the results were not the same. First off, I am unable to replicate the action buttons. My theory is that perhaps these were discontinued with the new version of Gmail. As for Google Inbox, those are still coming through. However, with Google Inbox slated to be discontinued in March 2019, this matters very little to us now. Lastly, my "my car rental" queries are not pulling in any results.
Is anyone able to confirm that email markup is still relevant? Google's documentation hasn't been updated since 2017, so it would be great to know before going through the effort of implementing the markup.
Thanks!
Related
As of yesterday, it appears that the Onenote /pages endpoint is not working properly for my account. The data returned for the first two pages is recent, however all other pages and their respective HTML content links are last updated as of Feb 28th 2020. Additionally, some of the pages showing up as "last edited" on Feb 28th 2020 are pages that I know for a fact have not been edited for months (place holders, old projects, etc.)
I have described a similar problem before: here and here. Such a problem was also described by another recently. Upon resolution of those issues, Manjusha stated that it was because of a "bad machine cluster causing jobs to get stuck" and therefore delaying updates. While this suffices to explain the delay, the inaccurate edit dates on page does not seem to be accounted for.
Any updates on the issue or insight into what is happening would be greatly appreciated.
UPDATE Mar. 5th 2020: Using the graph explorer, I can see that the pages endpoint is returning the same out-date response again and again. Basically, it is frozen in that state from what I can see.
I'm sorry to say this, especially at such a stressful time. However, the reliability of the pages endpoint has been up in the air for months. Working sometimes, not working at others. Personally, this has forced me to rebuild my personal programs so they do not rely on OneNote and reconsider using OneNote in professional settings where new pages are being made regularly. The sum total of this has been to cease development and usage of the OneNote API. Just a bit of feedback. I know your team works hard and these issues are complex - I hope this clears up for you soon.
Can you send the request-id header from the response and your request timestamp? Thanks!
I've found some interesting pieces of code on Google Schemas and I know that the only way to test it without being whitelisted is sending mails to yourself, but my problem is that even that doesn't really work for me.
I've tried countless examples in both formats, but only the Flight Reservation and the Go-To Action are working at all... Even though I let everything run through Google's markup validator before testing and it turned out to be valid.
So... does anyone know if this is an error that lies with Google (missing functionality, wrong examples, faulty markup tester, ...) or am I in fact missing something which is the reason why it doesn't work?
(I'm sending/receiving the emails through the normal Gmail inbox in Firefox version 33.0. In case it's important, I'm using a Laptop with Ubuntu 14.04.1 LTS)
The functionality is still missing from Gmail. In other words, no one at Google working at Gmail has coded any functionality to pick up, for example cooking recipies.
I am new to crashlytics. I entered my email and clicked on Try crashlytics. It redirected to another page showing You're on The list etc.Under General Info i entered my Name and my Company and clicked on "Put me on top".Then what are the steps should i follow to use crashlytics in my ios application. I am not getting what are the further steps should i follow?
When I registered for their service i was facing the same question, without an imminent answer on hand.
So I wrote them on Twitter and got a response in about an hour, which stated that they will process my request imidiately.
And they did. They created a batch just for me (the whole process from registration till the end implementation on my side was done in less than one day).
thumbs up for their customer service! I have never seen better :)
with monday being a holiday you might have an extra day to wait. have a little bit of patience, it is totally worth the wait. I migrated from BugSense to HockeyApp to Crashlytics. The fact that they're free is insane. I've got a couple feature requests in to them and they quickly got back to me and said that they have them on the roadmap. They're a cool group of people and were just scooped up by Twitter.
Enjoy it.
I have an iOS app that has been fetching the user's Facebook status updates and location checkins using "/me/posts" for several months. After today's "breaking changes" update, "/me/posts" only returns recent "Like"s. It looks like "/me/statuses" and "/me/checkins" are the new proper places to check for these things. I guess that makes sense, but I saw no documentation anywhere describing these changes or saying that they would happen today. The original documentation about what is specifically returned from the graph API also seems pretty slim.
So my questions are: is this an official change to the API? Where was it specified? Where should I look so I can stay on top of these things and not have my app break for hundreds of users?
Perhaps more importantly: are "/me/statuses" and "/me/checkins" the new proper ways to get this information? Or is there something else?
Always good to keep a (sharp) eye on the Developer Roadmap. These types of changes happen often, but FB usually does a good job of calling them out ahead of time. You've answered your own question as far as whether or not it's an "official" change - you're seeing it in the wild - insofar as how Facebook works, it's official.
Try using the Graph API Explorer. It could be an access token issue.
FYI: I see a similar issue with my application, and I am able retrieve the posts only when I use the Graph API Explorer and the token I get from there.
Update: I found where some of the problems lived. In the app profile in Facebook, pick "Edit Settings" and then go to "Advanced" where you'll see a section called "Migrations". This is mostly switches to show compatibility for various "breaking changes" updates, but it also includes an option for "Include Checkins with Statuses".
Now I know where to look, things are making a bit more sense.
Is anyone else experiencing problems with the Bing helper in Microsoft.Web.Helpers?
The Bing.AdvancedSearchBox helper method tried to load the following javascript file but throws a 404 error. The script is http://www.bing.com/bootstrap.js
Has anyone else experience the same problem? So far there has not been any updates to the microsoft-web-helpers package in Nuget. Any information is greatly appreciated.
Thanks,
Diego.
UPDATE 5/1/2011
I found the following official statement...
I wonder when Micorsoft will release an update to Microsoft.Web.Helper to remove the deprecated functionality.
Note: Bing team at Microsoft announced that they will be shutting down siteowner service on April 4th. This will prevent you to use the AdvancedSearchBox feature of Bing on your website/blog or web applications. Here is the quote from Bing's official blog:
As of April 4th, 2011 we will discontinue support for the bing.com/siteowner functionality. If you continue to leverage the feature after this date (April 4th, 2011), users who attempt to query in the search box will be redirected to a 404 page. This means that you will need to move to the Bing API in order to continue to receive web or site search results from us. We have decided to take this step for two reasons.
First, the tool has not been getting a lot of use and while we have some very loyal customers on it, we believe we can provide you better alternatives in the future as we free up resources.
Second, the functionality available through bing.com/siteowner can be replicated with the Bing search API and so it feels a bit redundant.
As has become customary, we will give you a window to migrate off and ask us any questions you may have about this change. We will also provide reminders as we get closer to April 4th. Thank you so much for your support.
It looks like something has changed on the bing servers and this script no longer exists.