Martin Mattel

Hello @yberges
the processor checks if the domain entered is most likely capable to recieve eMails. There is no checking for a particular domain or if the mailbox exists. But you can take the code and adopt it to your needs. The quick and dirty (=hardcoded) version would be to add the relevant code in file: cf-email-check.php in function EDCCF_email_domain_has_no_mx( $value ). You can of course extend the coding for an additional user input field to be more flexible.
Hope this helps.

Sorry for posting the Feature Request here, created a FR on your support page.

Anyway, just updated my live site from a duplicator backup – works like a charm !

Yep, two things come to my mind.

My database is:
Version 10.4.13
Comments mariadb.org binary distribution
Charset utf8mb4
Collation utf8mb4_unicode_ci

This charset is also defined in my wp-config.php
When creating a package and restoring it, duplicator always wants to set utf8 instead of utf8mb4. It does not respect the setting of the source database, I have to manually overwrite it each and every time.

I would like to have a switch/setting where I can define the size checks limit notice – to shut it off and make it green.

Hello @mostafas1990

many thanks for the quick answer.

I am hosting my own site. For me, it would be great to reuse my MariaDB engine, not a new one. Means, having the option to define the db connection (tcp:port or socket), db name, credentials would be great. I would, based on recommendations, pre-setup the database so you would only need to enter the access parameters. The code change would be to virtualize $wpdb by either using the original $wpdb or $mydb, where “$mydb = new wpdb(‘username’,’password’,’database’,’host’);” Know that sounds easy and I would help coding, but atm my knowledge about handling options in plugins is limited.

Hoping that this would not make to much effort and a soon implementation.

Best Regards,
Martin

• This reply was modified 4 years, 10 months ago by Martin Mattel.

Thanks John for replying.

Regarding regex, no this cant be used as the regex to be applied needs to know the source url somehow. Which would mean that you need to know/identfy the post-slugs. This is exactly to be avoided. As far I have seen, you can′t target regex to post categories.

Your statement “not if the posts are at the root URL” is imho also not true, because if you look on the code example in my comment above, it checks if the post to be shown has a category matching an element of the array list which is not dependent on the url location.

My favorite whish/approach would be, that this behaviour (in the UI, select post categories from the list and apply a post redirect to a internal url in case of a match) becomes part of the redirect plugin.

Martin