No3x
Forum Replies Created
-
Forum: Reviews
In reply to: [WP Mail Logging] Exactly what I needed!Hi @kenesloan,
Thanks for your kind feedback!
Please consider making a donation if you like the plugin.Forum: Plugins
In reply to: [WP Mail Logging] Timestamps of older mail all the sameWhat do you mean with PHP levels?
The host column was introduced in 1.7.0. Any previous logged mails are empty therefore. This should be easy to confirm by looking at the plugin_version field in the database.Actually that are a lot of information.. but no obvious reason.
Forum: Plugins
In reply to: [WP Mail Logging] Timestamps of older mail all the sameThe plugin itself does not change any of the values of a mail after it is stored in the database. So it must be triggered from anything else (like migration, restoring) imho.
Forum: Plugins
In reply to: [WP Mail Logging] Timestamps of older mail all the sameI just checked: ON UPDATE CURRENT_TIMESTAMP is default for field of type TIMESTAMP..
I thought I had removed something from this field in a previous plugin version but I have looked at several older versions and could not find any change.Nevertheless this seems not related to the problem. Because it is set on websites without any influence. But only if site 3 and 4 were not moved or restored from a backup.
Forum: Plugins
In reply to: [WP Mail Logging] Timestamps of older mail all the sameHi @marvel32,
thanks for your response. What you say supports my thesis about the “on update CURRENT_TIMESTAMP”. Basically this means: use the current timestamp if something in the database entry changes.
This is bad an was removed in 1.5.2 or so (but for new installs, not for old sites that used updates) because:
The first time I experienced the same was when moving a site with DB Migrate Pro. It took me a day to find the cause of this was “on update CURRENT_TIMESTAMP”.
Also the timestamp of the database is used. That may be differ to the WordPress time settings.You can check if “on update CURRENT_TIMESTAMP” is present easily with phpmyadmin by editing the timestamp field. There is a dropdown in the attributes column (see https://i.stack.imgur.com/LwCi7.png) either there is “on update CURRENT_TIMESTAMP” selected or nothing.
Please report on which sites this attribute is set.
Forum: Plugins
In reply to: [WP Mail Logging] Timestamps of older mail all the sameHi @marvel32,
interesting.. I can see this behaviour on my own site. I have never looked at mails older than a month. It is not an display issue – the timestamps are wrong on the database already.
Can use please check for me if the timestamp field in the wpml_mails table is set to “on update CURRENT_TIMESTAMP”? This could be related to the issue. This might be set if you use the plugin since a while (I have removed this update trigger a while ago for new installs – but It is not removed if you did plugin updates only)
At the first glance I have no glue why this happens..I just use this method https://codex.wordpress.org/Function_Reference/current_time to get the time and store it to the database..
Forum: Plugins
In reply to: [WP Mail Logging] PHP 7 CompatibilityHi! I run the plugin on multiple sites with php7.0. Don’t worry about this.
Forum: Plugins
In reply to: [WP Mail Logging] Compatibility with WP Mail SMTPHi @groovelanddesigns, thanks for your feedback. I recommend WP Mail SMTP (see Installation tab on the plugin site)
You may want to put this into a review:
https://wordpress.org/support/plugin/wp-mail-logging/reviews/Forum: Plugins
In reply to: [WP Mail Logging] Some emails are not being registeredOh sorry, it’s under “Installation” which seems to be the perfect place to me.
https://wordpress.org/plugins/wp-mail-logging/#installationForum: Plugins
In reply to: [WP Mail Logging] Some emails are not being registeredHi @felipe152,
Each mail send trough wp_mail should be logged. This contract may be broken by smtp mailer plugins that do not call the wp_mail filter. Default does of course and the recommended smtp plugins in the FAQ.
Forum: Plugins
In reply to: [WP Mail Logging] Suspicious CodePlease send me a hash of the file to verify integrity. Maybe someone really put malicious code in there.
But I don’t think that’s the reason: Please refer to a similar topic https://wordpress.org/support/topic/security-risk-vaultpress/
Forum: Plugins
In reply to: [WP Mail Logging] Suspicious CodeThis is ridiculous. It’s an established pattern for service based OOP and dependency injection.
Please refer to http://pimple.sensiolabs.org/Forum: Plugins
In reply to: [WP Mail Logging] function set_errorHi @alissonpierre,
I don’t understand under what condition the failed mail could not be found in the database. But I will add a check to prevent this error.
This can lead to logging failed mails without the actual error message.Forum: Plugins
In reply to: [WP Mail Logging] WordPress database error Duplicate column name ‘error’Closing due lack of feedback.
Forum: Plugins
In reply to: [WP Mail Logging] 500 Fatal error on updating user-edit.phpClosing due lack of feedback.
