I have had issues before where shortcodes on the same line as a paragraph would cause erroneous tags. Seems that it would also be better as it wouldn’t interfere with any 3rd party shortcodes!
So for every shortcode you create, you have a class on the outer wrap of “autop”?
Might need to take a little look at re-working the way we do it 
- Ed
I’m not sure if the reviewers would have anything against it, but does it work well for you?
- Ed
PhantasiaAeterna said
yes, it is not perfect But if you have a better solution, I will be glad to hear it:)
I suggest you get this changed asap, as that really isn’t a solution in any way. You need to get users to sort out their own credentials (provide a tutorial?).
- Ed
phpdude said
I was skeptical too, I thought the display requirements were only meant for the more high class sites and for TV, but according to this discussion with a Twitter employee, they say it’s for everything. https://dev.twitter.com/discussions/15327Yes, the display requirements apply to all scenarios in which Tweets and Twitter content are shown

- Ed
chrisakelley said
http://wordpress.org/extend/plugins/oauth-twitter-feed-for-developers/
YES! Thanks for posting that Chris, works an absolute treat.
- Ed
JustinScheetz said
I have an announcement to make soon about Leafping, stay tuned on the site to find out what it is.
Excited!! 
- Ed
EDIT: Seems I didn’t actually read the thread post! :doh:
- Ed
We also had this response in our latest submission. I remember the toolkit being introduced a while back, but it was never brought up as being an issue for not including it before this week.
From our last few releases it does seem that requirements are sometimes introduced without sufficient notice to authors.
- Ed
Congratulations – best of luck at the new job! 
- Ed
Congrats guys – great work! Should be joining you in a few months 
- Ed
