Crawler AJAX/escaped fragment support?

cpwalker07 · 2014-01-14T15:32:22.000Z

I support getting this feature on the development roadmap.

Volotskoy · 2014-01-22T11:55:06.000Z

+1

gerwert · 2014-01-23T10:34:06.000Z

+1
With the resize of front-end frameworks, like Angular and Backbone, this is a really essential feature of modern crawlers.

Please make it a priority, Twitter!

johngboutros · 2014-01-29T12:28:35.000Z

Is there any known workaround for twittercards to work with the #! ?

tecteun · 2014-01-30T15:07:42.000Z

+1
Please Twitter, give this priority! Or at least a workaround:

Implementing this shouldn't be too hard ;)

sampsakuronen · 2014-01-31T11:11:55.000Z

Hello!

Any update on this?

DenisTRUFFAUT · 2014-01-31T16:31:00.000Z

@tecteun It is best for Twitter to follow the full spec (handle #! fragments or detect a ), but indeed, a cheap “twitter:crawl_url” parameter should complete the job for free.

jbulava · 2014-02-26T22:00:25.000Z

As of today, the Twitterbot will support hashbangs by converting to “escaped_fragment.”

nabbyps · 2014-02-26T23:46:00.000Z

#THANKYOU#THANKYOU#THANKYOU#THANKYOU#THANKYOU#THANKYOU#THANKYOU

Coquevas · 2014-02-28T08:15:43.000Z

Still getting “Invalid card time” from the card validator for my #! URLs, and looking at my server logs the bot is still hitting the wrong URLs, without the #! (obviously, local dynamic part) but without the escaped_fragment param too

odra_ti · 2014-03-05T16:33:42.000Z

Sorry the invalid card still continuing

zealous_co · 2014-03-12T17:13:42.000Z

We tried testing this link on the card validator http://www.zealous.co/#!project;id=5701808034938880 it doesn’t hit the escaped fragment version of the site. It should look something like this give you this result when shared http://www.zealous.co/?escaped_fragment=project;id=5701808034938880.

Could you confirm this hasn’t been done yet, or if it has that it’s a current bug on Twitter?

We’re very excited to start using cards properly!

Cheers,

Guy

jbulava · 2014-04-22T12:20:11.000Z

Could you provide a couple example URLs for us to investigate?

jbulava · 2014-04-22T12:20:21.000Z

Could you provide a couple example URLs for us to investigate?

jbulava · 2014-04-22T12:23:54.000Z

Ah, just noticed the following URL on a related thread, but if you have any others to share, feel free. http://www.laurareyero.com/retrato/?escaped_fragment=LR_081209_01

Coquevas · 2014-04-23T15:44:16.000Z

Now it’s working, It accepted the URLs and I could request the approval, but I got instant rejection mail. Now I re-requested it and waiting for approval. Thanks!

jbulava · 2014-04-25T04:47:52.000Z

Ok great!

jbulava · 2014-05-05T18:18:58.000Z

Hi Zealous Co,

Over the weekend, we rolled out a change to fix issues with escaped fragments. I now see the appropriate gallery cards when I tweet http://www.zealous.co/#!project;id=5701808034938880 and http://www.zealous.co/#!project;id=6327994469580800. Please let me know if you are experiencing any further issues.

theeluwin · 2014-07-24T21:34:59.000Z

I think my case is not usual as other people but can I give a question? I’m just wondering that whether the Twitterbot is considering hash on url (not hashbang, hash!). My case is http://blincle.com/#!/#detail-53d091366803fae3a9529e90 and I need them to be like http://blincle.com/?escaped_fragment=/%23detail-53d091366803fae3a9529e90 or just escaped_fragment instead of _escaped_fragment (my server detects both), but I’m not sure if the # coming after #! is well converted to %23. The twitter card validator shows http://blincle.com/#!/#detail-53d091366803fae3a9529e90 is “server error”, while http://blincle.com/#!/%23detail-53d091366803fae3a9529e90 just works fine (of course, for the latter one, my server receives /?escaped_fragment=/%23detail- blah blah).

theeluwin · 2014-07-24T21:38:25.000Z

hmm. Two underscores surrounding some word somehow got stripped. escaped_fragment