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

Fatal Error replying to comments in Comment Mail Lite #297

Closed
raamdev opened this issue Aug 24, 2016 · 2 comments
Closed

Fatal Error replying to comments in Comment Mail Lite #297

raamdev opened this issue Aug 24, 2016 · 2 comments

Comments

@raamdev
Copy link
Contributor

@raamdev raamdev commented Aug 24, 2016

This bug was originally reported on the WordPress Support Forum here and here and here and here.


The following appears when replying to comments on the site as a logged-in admin using Comment Mail Lite v160818:

2016-08-23_23-37-02

Fatal error: Uncaught exception 'Exception' with message 'Undefined overload property: `utils_rve`.' in /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/AbsBase.php:111
Stack trace:
#0 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/Plugin.php(866): WebSharks\CommentMail\AbsBase->__get('utils_rve')
#1 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/UtilsPhp.php(87) : eval()'d code(109): WebSharks\CommentMail\Plugin->__get('utils_rve')
#2 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/UtilsPhp.php(87): eval()
#3 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/Template.php(149): WebSharks\CommentMail\UtilsPhp->evaluate('<?php\nnamespace...', Array)
#4 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/QueueProcessor.php(898): WebSharks\CommentMail\Template->parse(Array)
#5 /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/QueuePr in /vagrant/src/app/src/wp/wp-content/plugins/comment-mail/src/includes/classes/AbsBase.php on line 111

This appears to be related to something that is expecting the RVE code to be present, likely the result of the work done in #285 for the last release.


Additionally, when replying to comments from the WordPress Dashboard, the following shows up under the comment box. The comment reply goes through, but the JavaScript that refreshes the form fails and makes it look like the reply did not go through:

2016-08-23_23-39-11


Temporary Workaround

At this time the only workaround is rolling back to the previous version of Comment Mail Lite, v160618.

@raamdev raamdev added this to the Next Release milestone Aug 24, 2016
raamdev added a commit to wpsharks/comment-mail-pro that referenced this issue Aug 24, 2016
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Aug 24, 2016

Next Release Changelog:

  • Bug Fix: Fixed a bug that was generating a fatal error when replying to comments. This bug only affected the Lite version of Comment Mail and was introduced by the previous release (v160818) where work was done to strip out unused Pro-only code from the Lite codebase. A few references to Pro-only functions were missed and that resulted in fatal errors for the Lite version in some scenarios. See Issue #297.
@raamdev raamdev closed this Aug 24, 2016
@raamdev raamdev modified the milestones: Next Release, v160824 Aug 24, 2016
raamdev added a commit to wpsharks/comment-mail-pro that referenced this issue Aug 24, 2016
raamdev added a commit that referenced this issue Aug 24, 2016
- **Bug Fix**: Fixed a bug that was generating a fatal error when replying to comments. This bug only affected the Lite version of Comment Mail and was introduced by the previous release (v160818) where [work](#285) was done to strip out unused Pro-only code from the Lite codebase. A few references to Pro-only functions were missed and that resulted in fatal errors for the Lite version in some scenarios. See [Issue #297](#297).
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Aug 24, 2016

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

@wpsharks wpsharks locked and limited conversation to collaborators Aug 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.