Scott Reilly

This plugin records which user actually published a post, which in a multi-author environment may not always be the original post author. This helps to maintain accountability for who was ultimately responsible for a post appearing live on a site.
The admin listing of posts is amended with a new “Published By” column that shows the name of the person who published the post (for those posts that have actually been published). A dropdown above admin post listings allows for the listing to be filtered by a particular publishing user (but only includes posts with a known publishing user).
For posts that were published prior to the use of this plugin (and thus the plugin could not directly record who published those posts), the plugin makes a best guess attempt to ascertain who published the post. After failing to find the publisher of the post as recorded by the plugin, it checks for who last edited the post, then who is responsible for the latest revision of the post, and finally failing those, it assumes it was the post author. In cases where it had to go through this process, the name of the person it deduced as the likely publisher appears italicized and with a question mark at the end. If you’d rather the plugin not make an attempt to guess the publisher, you can disable the checks by including this snippet in your theme’s functions.php (or, ideally, a site-specific mu-plugin):
<pre><code><?php add_filter( 'c2c_published_by_skip_guessing', '__return_true' ); ?>
</code></pre>
Links: <a href="http://coffee2code.com/wp-plugins/published-by/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/published-by/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/published-by/" rel="nofollow ugc">GitHub</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a>

Published By

Track which user actually published a post, separate from who created the post. Display that info as a column in admin post listings.

Ryunosuke

Allows Asset Store publishers to accept online customer support requests with automatic invoice validating beforehand.
Unity provides the api located at http://api.assetstore.unity3d.com/ to be used to validate invoices by requiring a publisher identifier and an invoice number(s). Once it receives both of these it will return an array containing the following information: 1. Purchase date 2. Was the transaction reversed / refunded 3. The invoice number you supplied 4. The package/product name
Invalid invoices are not returned so this kit checks the number of returned invoices against the number sent to Unity as well as the refund status of the invoices. If all invoices return as validated, the contact form will be sent to the configured address.
In terms of the data collected to be sent to Unity, the publisher’s identification is achieved via the private API key the publisher gets on the Unity Publisher’s Administration page. This info is entered in the Dashboard and fetched before contacting the Unity API. This field is never revealed to anyone other than Unity and people with the authority to manage site options. The invoice numbers to be validated is provided by the person completing the form.
So in summary: In the dashboard, provide the email address you want the contact form to be sent to and your private key to access the Unity API. From the customer, collect their invoice number(s) These two fields are sent to Unity who then returns anonymous info regarding the transaction including only purchases / refund status and purchase date.

Asset Store Customer Support Form

Allows Asset Store publishers to accept online customer support requests with automatic invoice validating beforehand

Published By vs Asset Store Customer Support Form