Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve information displayed on the Post Meta Box #231

Closed
kristineds opened this issue Feb 12, 2016 · 7 comments
Closed

Improve information displayed on the Post Meta Box #231

kristineds opened this issue Feb 12, 2016 · 7 comments
Assignees
Milestone

Comments

@kristineds
Copy link
Contributor

It would be nice to improve the information displayed on the Post Meta Box to include the subscription time. Also, have the subscriber’s name displayed instead of their email address.

Before:

screen shot 2016-02-12 at 6 18 51 pm

After:

screen shot 2016-02-12 at 2 03 31 pm

@raamdev
Copy link
Contributor

raamdev commented Feb 12, 2016

👍

@raamdev
Copy link
Contributor

raamdev commented Feb 12, 2016

Some more thoughts on this:

  • Linking the email address to the subscription itself is very counterintuitive. When I see the link around the email address, I immediately assume that clicking that link is the same as clicking any other email address: i.e., it's going to try and open my default email client to send that person an email. So, whatever we do here, we need to NOT use the email address as a link to the subscription; that just doesn't make sense.
  • Now that this Post Meta box is of the wider variation (instead of the sidebar variation), we can make use of that extra space to show a bit more information. I like that idea. It makes that box look a bit more like a log of recent subscriptions.
  • The "6 days ago", "20 hours ago" feature that Kristine suggested looks nice and I would follow the same format that we use in the Subscriptions list, e.g., "Feb 11, 2016 3:20pm (20 hours ago)".
  • The link at the very top that says the total number of subscriptions has a few issues, namely that it doesn't look like a button or a link. I suggest moving that to the bottom of the list (which makes sense... you view the list of most recent subscriptions, then if you want to view all of them you click the button to view all at the bottom).

Here's how I suggest we improve this Post Meta Box:

2016-02-12_10-52-35

@raamdev raamdev added this to the Future Release milestone Feb 12, 2016
@jaswrks
Copy link

jaswrks commented Feb 12, 2016

This looks great!

2016-02-12_10-52-35

@kristineds
Copy link
Contributor Author

Nice! I love this. 👍

2016-02-12_10-52-35

@raamdev
Copy link
Contributor

raamdev commented Apr 15, 2016

Next Release Changelog:

  • Enhancement: Improved the Subscriptions meta box that appears on the Post Edit screen. For each subscription, the meta box now lists the full name and email address, the date the subscription was created, and a view link that allows you to view/edit the subscription. Props @kristineds. See Issue #231.

@raamdev raamdev closed this as completed Apr 15, 2016
@jaswrks
Copy link

jaswrks commented Apr 16, 2016

Woohoo! :-)

raamdev added a commit that referenced this issue Jun 18, 2016
- **Restructured Codebase**: The codebase has been completely restructured to improve performance, enhance flexibility, and make it easier to build in new features! Props @jaswsinc. See [Issue #150](#150).
- **Comment Mail Pro Upgrade Notice: Incompatible Advanced Templates.** This version of Comment Mail includes a rewritten and improved codebase. This rewrite, however, came with the unfortunate side effect of breaking backwards compatibility with Advanced Templates that were customized in a previous version of Comment Mail Pro.

     If you are currently using Comment Mail Pro and you've customized your Advanced Templates, all of your customized Advanced Templates will be backed up and the templates will then be reset to their new defaults. You will find the backup of your old customized template appended to the bottom of the new template, separated with a  <code>Legacy Template Backup</code> PHP comment. See [example screenshots](#238 (comment)).

     Note: This change has no effect on Simple templates—only Advanced Templates are affected. Advanced Templates are a Pro-only feature, so this notice only applies to Comment Mail Pro. See [Issue #238](#238).
- **Bug Fix**: Fixed a bug where `esc_html()` was being used where `esc_sql()` should've been used. Props @jaswsinc @kristineds. See [Issue #268](#268).
- **Bug Fix**: Fixed a bug that in some scenarios resulted in a "DB table creation failure" error when activating the plugin. Props @thienhaxanh2405, @PanNovak, @kristineds, and @jaswsinc. See [Issue #260](#260).
- **Bug Fix**: Fixed a bug where "New reply" notification emails were not being parsed properly by some Hotmail accounts and were showing up as blank. Props @kristineds. See [Issue #259](#259).
- **Bug Fix**: Fixed a bug that allowed spam comments to create subscriptions in Comment Mail when using Akismet. Props @IvanRF. See [Issue #250](#250).
- **Bug Fix** (Pro): When Chrome or Firefox Autofill Username/Password was enabled, the Comment Mail Pro Updater fields would incorrectly be autofilled by the browser with invalid credentials. This has been fixed. Props @renzms. [Issue #274](#274).
- **Bug Fix**: Fixed a bug where the cron job for the Queue Processor could get deleted and never recreated, which would result in notifications getting stuck in the Mail Queue and not being sent out. If you ever installed Comment Mail and then deleted it (without first disabling Data Safeguards), and then installed Comment Mail again, you were probably affected by this issue. This release fixes the issue and makes the cron setup more robust. Props @kristineds, @renzms, @jaswsinc, and @IvanRF for help testing. See [Issue #194](#194) and [Issue #173](#173).
- **Bug Fix:** Fixed a bug where a subscriber who selected Hourly Digest and who had never been notified before could, in some scenarios, have their subscription treated instead as a Weekly Digest. This bug was found and fixed during the codebase restructuring. Props @jaswsinc. See [Issue #150](#150) and additional discussion in [Issue #173](#173 (comment)).
- **Bug Fix:** Fixed a bug where in some scenarios Mail Queue entries for Digest Notifications that should have been held for sending later were not being held and were also not being sent. They also would not have shown up in the Mail Queue Event Log. This bug was found and fixed during the codebase restructuring. Props @jaswsinc. See [Issue #150](#150) and additional discussion in [Issue #173](#173 (comment)).
- **Enhancement**: Minor improvements to the Options Page menu links and positioning of the Pro Preview link. Props @renzms. See [Issue #227](#227).
- **Enhancement**: It's now possible to use the following shortcodes in the Email Footer Tag for Email Footer Templates: `[home_url]`, `[blog_name_clip]`, and `[current_host_path]`. Props @kristineds and @IvanRF. See [Issue #246](#246).
- **Enhancement**: Improved the Subscriptions meta box that appears on the Post Edit screen. For each subscription, the meta box now lists the full name and email address, the date the subscription was created, and a view link that allows you to view/edit the subscription. Props @kristineds. See [Issue #231](#231).
- **UX Enhancement (Pro)**: Improved the Dashboard notice that appears when you try to enable the Pro version of Comment Mail when the Lite version is currently enabled. Props @kristineds @jaswsinc. See [Issue #230](#230).
- **UX Enhancement**: When Subscribing Without Commenting, the Add New Subscription form now pre-populates the Name and Email address fields whenever possible. Props @kristineds. See [Issue #204](#204).
- **UI Enhancement**: Dashboard notices generated by Comment Mail now use the WordPress-style dismiss button to keep things consistent. Props @kristineds. See [Issue #193](#193).
@raamdev
Copy link
Contributor

raamdev commented Jun 19, 2016

Comment Mail v160618 has been released and includes changes from this GitHub Issue. See the v160618 announcement for further details.


This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#231).

@wpsharks wpsharks locked and limited conversation to collaborators Jun 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants