Thank you for your suggestion. I have submitted a message to the plugin developers to investigate further your suggestion/request.
Kind regards
Thank you. I will look into it.
Hi @erikmolenaar.
As I understand from your message, you want an option in the plugin, which, when checked, checks if domain name of the website it’s running on matches the list you specify. If it matches, then it can send email, and if not – it isn’t sending it.
Am I correct? If not, could you please provide some additional details.
Thanks.
Hi @alexanderfoxc,
Correct. But I think a single input field would be sufficient compared to a list.
In a single input field you’ll just enter your live domain name (e.g. mywebsite.com). A list would be not needed as you just want to make sure it only emails out from the live domain (and NOT from others like staging.mywebsite.com or localhost).
Thanks!
Thank you for your clarifications, @erikmolenaar.
This functionality is coming in next version, which should be released short 😉
Thanks great news. Thanks for listening to my feedback 🙂
One more thing I notice now when working with the new domain check field.
The domain value tends to be replaced during building a staging/development version of a website. E.g.: by using WP Engine’s ‘copy to staging’ functionality, deploying with Duplicator or when working with popular ‘search & replace URL’ plugins such as Velvet Blues.
Is it possible to encode this field in the database it so it would be affected by ‘URL search & replace’ scripts?
Hi Erik. You want it to BE affected or NOT to be affected? As I understand from your use case, you want the value to be preserved rather than replaced during copy to staging.
Hi Alexander
Thanks for your reply.
I would say it should NOT be replaced and thus preserved during a migration (which usually includes a URL search and replace script).
This way the only case where email is send out to the ‘real world’ in from the live domain only.
Yep, that’s what I thought too 🙂 Thank you for your reply.
It would be implemented in next version.
so it would be affected by ‘URL search & replace’ scripts?
Sorry that was a typo on my end 🙂
Looking forward to your plugin update and thanks again for listening!
Hi @alexanderfoxc,
I just updated to 1.2.9, which was released 3 days ago but the domain name value is still being renamed by WP Engine’s staging functionality.
Or am I a bit too soon with 1.2.9 and will the fields be encoded in the next version of your plugin? 🙂
Looking forward to your reply and plugin update. Thanks!
Kind regards
Hey @erikmolenaar, this is coming in next version, which should be released within couple of days 😉
Hi @alexanderfoxc
Just wanted to now it works beautifully with version 3.1.0.
Just one more question: how did you do this; preventing this field NOT to be renamed during search&replace procedures? WP Engine even told me it was not possible, as their system renames EVERY domain reference during building a staging/development version.
Looking forward to your reply. Thanks!
Hey Erik @erikmolenaar , the version is 1.3.0, but doesn’t matter 😉
What I did is applied base64_encode on the domains list value. This way following line
domain1.com, domain2.com
turns into
ZG9tYWluMS5jb20sIGRvbWFpbjIuY29t
and migration scripts can’t see anything familiar, thus not replacing any values 😉
-
This reply was modified 8 years, 7 months ago by
Alexander C..
