Changes cannot be made at fsmpt_email_logs with Better Search Replace

Hello @markussss,

Thank you for getting in touch with the FluentSMTP support team.

I understand that you’re experiencing issues when using Better Search Replace to update email addresses in the fsmpt_email_logs table.

Could you please provide more details about what you’re trying to achieve with Search and Replace? This will help me understand your situation better and provide more tailored assistance.

Can we turn it around? I actually explained it all – what’s your question about it to better understand the situation?

Hello @markussss

In the part where you are changing the emails, It’s important to clarify whether you’re trying to modify the “FROM” or “TO” email address. Please confirm this information.

Additionally, the purpose of modifying the email logs should be considered. Once an email has been logged, changing the logs doesn’t affect the actual sending of the email.

The database lock status is the same as the other tables and not locked by default.

Not sure if there is perhaps a misunderstanding.

I am just replacing the strings e.g. from [email protected]?to?[email protected]

There is no FROM or TO address. There is no intention to re-send any emails.

I know about the purpose and I am aware of it. In general if I am running and target a string replacement, I am the one of course who is responsible for the outcome. But when I run a string replacement, I expect it to be changed in the database – and it does exactly that, except for the mentioned table, where Better Search Replace tells me it has done it successfully, until I learn it did not actually happen

All if it is only about a clean process. Yes, you can question why someone would change a string in log entries of the past, but that is less of a concern than why it is not doing it. No matter the reason, I think it should be able to do it like it can do for every other table in WordPress

Hey there,

as I have an open support case with Better Search Replace about this, I checked the status in here and saw it’s marked as ‘resolved’ which actually isn’t quite true.

As mentioned in my previous message, no matter the reasoning behind it, a string replacement via DB should replace everything including log tables from Fluent SMTP. No idea why it is not possible to do that.

In real life it doesn’t matter much anymore to me for the particular project where I tried to apply the search/replace command. But it did cost me some time to troubleshoot until I narrowed it down to understand that the search/replace did solely not work with the Fluent SMTP table.

You could probably test and try yourself, I think you’ll be able to replicate it.

best regards
Markus

I got some insights now from Better Search and Replace – they’ll try to work around here, but it sounds like it’s related to the fact that you are using reserved words as table columns. I hope you can make use of this information

They can confirm that this is a bug,?
since ‘fsmpt_email_logs‘ table is using the words “to” and “from” are used as column names.
This causes an error, as they are to be considered as reserved words:?
https://dev.mysql.com/doc/refman/8.4/en/keywords.html#keywords-in-current-series
?
Our code does not put the column names in backticks, so column names that match reserved words will cause a failure.
Our dev team have now raised a ticket to try and fix this issue.

Better Search Replace support