Wordletz

What are the chances of a pull request on github adding this feature getting merged?

Something like this:
A setting in Settings->Twitter Tools->Accounts->User
Below the “Create blog posts from tweets”
A setting for “Use embedded format for tweets”

which basically does an if statement in create_blog_post for $post_content to equal $this->status_url() if the setting is enabled.

I’d also like something to eliminate the title altogether, it just duplicates the content, so in most themes it’s unnecessary. Something like a checkbox under ‘use embedded format’ that says ‘Don’t pull title from tweet’ but without disabling the title prefix so you can still say something like ‘From Twitter’ if you wanted.

If the odds are good I can throw something up over the weekend.

I made a provision script to automatically create a user with their information from CAS (just the username and email), and then I have a cron job that removes them after a certain period of time.

Looks like it might be related to my https everywhere plugin I have installed. Or perhaps another one. I tried opening it in an incognito window and I didn’t get an error.

When I opened the page normally (when I get the error) I used the javascript console to catch this debug info (replaced my website url with <mywebsite>):
Blocked a frame with origin “https://<mywebsite&gt;.com” from accessing a frame with origin “https://widgets.wp.com&#8221;. The frame requesting access has a protocol of “http”, the frame being accessed has a protocol of “https”. Protocols must match.
onloadwff.js:463
Blocked a frame with origin “https://widgets.wp.com&#8221; from accessing a frame with origin “https://public-api.wordpress.com&#8221;. Protocols, domains, and ports must match. onloadwff.js:463

So it looks like the use of the iframes violates some best practices guidelines that whatever plugin I have enforces for additional security.

I’m experiencing the same error. Although this is my first time installing so it’s never worked.

This can be fixed by going into the ‘functions’ file of the plugin and changing all instances of current_time(‘timestamp’) to time()

However fixing that bug alone is now pointless because the plugin does not work with twitter’s new v1.1 api which became required a couple of days ago.