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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Process Queue Manually #282

Closed
jaswrks opened this issue Jun 16, 2016 · 8 comments
Closed

Feature Request: Process Queue Manually #282

jaswrks opened this issue Jun 16, 2016 · 8 comments
Assignees
@jaswrks
Labels
enhancement
Milestone
v161213

Comments

@jaswrks
Copy link

jaswrks commented Jun 16, 2016

It would be very helpful if there was a button in the Dashboard that would allow a site owner to force a queue runner to process any lingering emails still in the queue. This might help others troubleshoot issues related to what could actually be an underlying problem with the CRON job.

Referencing: https://github.com/websharks/comment-mail-pro/blob/edea333166cc96cb9a7b6b8d6f8e09a346263fc0/src/includes/classes/Plugin.php#L2729

↑ Need to a way to trigger this method from the Dashboard through a non-blocking HTTP connection. Or, we simply need a way to trigger the CRON job that already exists from the Dashboard using something other than WP Crontrol, because that plugin doesn't seem to work in all cases for some reason.
@raamdev raamdev added this to the Future Release milestone Jun 16, 2016
@raamdev raamdev modified the milestones: Next Release, Future Release Jul 12, 2016
@IvanRF
Copy link

IvanRF commented Oct 3, 2016 •
edited
Loading

This feature will be helpful. I currently have 1,292 items stuck on the Mail Queue (since 2 weeks ago).

@raamdev raamdev modified the milestones: Next Release, Future Release Oct 11, 2016
@jaswrks
Copy link
Author

jaswrks commented Nov 19, 2016

Work in this issue may also help to resolve and/or diagnose problems reported in #317

@jaswrks jaswrks mentioned this issue Nov 21, 2016
Open
jaswrks pushed a commit to wpsharks/comment-mail-pro that referenced this issue Dec 2, 2016
- **New Feature:** It is now possible to manually process the outgoin…
6bcd03d 
…g mail queue. See: **WP Dashboard → Comment Mail → Mail Queue**. See also [Issue #282](wpsharks/comment-mail#282).
@jaswrks jaswrks mentioned this issue Dec 2, 2016
Merged
@jaswrks
Copy link
Author

jaswrks commented Dec 2, 2016

2016-12-02_03-00-51

2016-12-02_03-01-22

@jaswrks
Copy link
Author

jaswrks commented Dec 2, 2016

Next Release Changelog:

  • New Feature: It is now possible to manually process the outgoing mail queue. See: WP Dashboard → Comment Mail → Mail Queue. See also Issue #282.

@jaswrks
Copy link
Author

jaswrks commented Dec 2, 2016

Noting that the above details (i.e., 30 seconds and 100 queued emails) as seen in the screenshot, can be changed in your Comment Mail options. If you change them, the wording in that notice will change accordingly, and so will the time allowed and the number of entries you're able to process.

See: Config Options → Queue Processor Adjustments

jaswrks pushed a commit to wpsharks/comment-mail-pro that referenced this issue Dec 2, 2016
Typo: is you, should be if you. See: wpsharks/comment-mail#282
53d0ae0
@renzms renzms mentioned this issue Dec 10, 2016
Closed
@renzms
Copy link
Contributor

renzms commented Dec 13, 2016

@jaswsinc @raamdev

Settings seem to be working fine, but how can I get Notifications to queue so that they can be manually processed? The automatic process is doing its job very well 😆

Default:
screen shot 2016-12-13 at 3 29 36 pm

Changing settings in Queue Processor Panel

screen shot 2016-12-13 at 3 32 03 pm

With Max allowable values:
screen shot 2016-12-13 at 3 39 21 pm

@jaswrks
Copy link
Author

jaswrks commented Dec 13, 2016

In that same panel change Real-Time Queue Processing from 5 to 0 (disable).

raamdev added a commit that referenced this issue Dec 13, 2016
@raamdev
Phing release of v161213 with the following changes:
6573c2d 
- **Bug Fix:** Prevent browser autocomplete in Comment Mail options. See [Issue #319](#319).
- **Bug Fix:** Searching by email address alone should always narrow to the search to that specific email address and not result in any fuzzy or fulltext matching. See [Issue #226](#226).
- **Bug Fix:** The conflict check for 'Subscribe to Comments Reloaded' was not working in the previous release; i.e., if you attempt to activate both Comment Mail and the 'Subscribe to Comments Reloaded' plugin at the same, this should result in a Dashboard warning. Fixed in this release. See [Issue #315](#315).
- **Bug Fix:** Notify 'Subscribe to Comments Reloaded' users about the comment form template being disabled under certain scenarios. See [Issue #314](#314).
- **Bug Fix:** Do not attempt to import 'Subscribe to Comments Reloaded' (StCR) settings if StCR is no longer installed, even if old StCR options exist in the database. See [Issue #294](#294).
- **Bug Fix** (Pro): Do not show SparkPost partner image when Mandrill is selected as the RVE handler. See [Issue #318](#318).
- **Bug Fix** (Pro): Conflict checks between lite and pro corrected. This was not working properly in the previous release; i.e., installing Comment Mail Pro when Comment Mail Lite is already running should result in Comment Mail Lite being deactivated automatically. See [Issue #270](#270).
- **New Feature:** It is now possible to manually process the outgoing mail queue. See: **WP Dashboard → Comment Mail → Mail Queue**. See also [Issue #282](#282).
- **New Feature** (Pro): In Comment Mail Pro it is now possible to enable/disable comment content clipping entirely; e.g., if you prefer that email notifications include the full original comment content in raw HTML instead of being clipped and displayed in the email as plain text. See: **WP Dashboard → Comment Mail → Config. Options → Email Notification Clips**. See also: [Issue #281](#281).
- **Accessibility:** This release improves screen reader accessibility by adding `aria-hidden="true"` to all FontAwesome icons. See [Issue #304](#304).
- **Accessibility:** This release improves screen reader accessibility by offering a new setting that allows a site owner to enable or disable select menu option enhancement via jQuery. Disabling select menu option enhancement has the benefit of improving accessibility for screen readers whenever accessibility is of more concern than presentation. See: **Dashboard → Comment Mail → Config Options → Misc. UI-Related Settings**. See also [Issue #304](#304).
@raamdev
Copy link
Contributor

raamdev commented Dec 13, 2016

Comment Mail v161213 has been released and includes changes from this GitHub Issue. See the v161213 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 (#282).

@raamdev raamdev closed this as completed Dec 13, 2016
@wpsharks wpsharks locked and limited conversation to collaborators Dec 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jaswrks jaswrks

Labels
enhancement
Projects
None yet
Milestone
v161213
Development

No branches or pull requests
4 participants
@raamdev @jaswrks @IvanRF @renzms