Ben Keith
Ben Keith
More about GitHub's community guidelines features: https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization Adding guidelines to the repo would provide clear guidance on who can propose edits and make pull requests, removing the need for questions...
Compare https://vip.wordpress.com/plugins/co-authors-plus/ to https://wordpress.org/plugins/co-authors-plus/, and observe that the .org plugin listing has some very outdated screenshots. - [ ] replace screenshot-1.png, screenshot-2.png, screenshot-3.png in this repo with newer screenshots
How about the long form of [Llanfairpwllgwyngyll](https://en.wikipedia.org/wiki/Llanfairpwllgwyngyll): Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch Alternately, https://en.wikipedia.org/wiki/Taumatawhakatangihangakoauauotamateaturipukakapikimaungahoronukupokaiwhenuakitanatahu
We have this example in readme.txt: ``` [pym src="child.html" pymoptions=" xdomain: '\\*\.npr\.org' "] ``` Which is supposed to output: (with supporting code) ```js pym.Parent('pym_0', 'child.html', { xdomain: '*\.npr\.org' }); ```...
- [ ] `fab wp.tests_setup:pym` - [x] review code for things that will need to be tested especially - [x] create list of high-priority tests and low-priority tests - assume...
We didn't do this in the initial implementation of Gutenberg blocks in #34 because, at the time, it appeared as if there was no way to use Gutenberg's `anchor` property...
From #34: - [ ] create a https://wordpress.org/gutenberg/handbook/block-api/#transforms-optional transform method that converts the Pym block into a generic embed block
From #34: - [ ] Add support for converting the shortcode block containing a Pym iframe into a Pym Block, once https://github.com/WordPress/gutenberg/issues/8569 has been resolved
This issue is waiting on answers to the questions in https://github.com/WordPress/gutenberg/issues/9517 . Once we have an answer, - [ ] re-add the text domain removed in the commit f73f965 -...
https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/ says regarding declaring a text domain: > After WordPress 4.6 came out, the Text Domain header is no longer required if it’s the same as the plugin slug. It’s...