pictoru
Forum Replies Created
-
Forum: Plugins
In reply to: [Two-Factor] Design email templateWell, this is nice. Thanks.
I also added the filter
wp_mail_content_type
separately to send the email as HTML because in the below line (from Two Factor plugin) headers cannot be altered.return wp_mail( $user->user_email, $subject, $message );
Is there something already set to allow me to send as HTML or my approach is OK?
Thanks,
Ciprian
Forum: Plugins
In reply to: [Blackhole for Bad Bots] Falsly treatment for AIOSEO Rest API requestsI will try to replicate the steps on Monday on a brand new install, note all the steps and let you know after.
Thank you,
Ciprian
Forum: Plugins
In reply to: [Blackhole for Bad Bots] Falsly treatment for AIOSEO Rest API requestsHi Jeff,
Thank you for making time for my issue.
Firstly, some more generic information. All my client’s websites (20+) are located in Azure and have Nginx as web server with caching module enabled. All these websites have almost the same plugins and use Avada theme. I cannot give here, publicly, the URLs because of my contract. However, only one website, the most visited one, has this issue or incompatibility, don’t know how to better name it. This is the strangest thing. Although, in private, I could give you access to the staging environment, which behaves the same.
The issue didn’t appear from the beginning. The website has at least one year since has been completely changed, and we made a couple of times update to WP core, theme and plugins ever since. So, I can’t give you the exact steps to reproduce because I don’t remember the exact moment it appeared. The plugins I use: AIOSEO with couple of addons, ACF Pro, Complianz, Custom Post Type UI, Disable Guttemberg, BBQ Firewall, Everest Timeline, FileBird, Font Awesome, Interactive GEO Maps, Post Types Order, Themehigh Job Manager, Two Factor, User Role Editor, Visual Term Description Editor, WP Mail SMTP.
Ciprian
I also have the same issue. With VTDE plugin installed qTranslateX is disabled on category description in LSB mode. It is working thought if using Raw Editor mode of qTranslateX, with shortcodes, like:
[:en]English text [:fr] texte fran?ais [:ro] text ?n roman?
… so, I think only the behaviour of the text editor is affected not the entire qTranslateX plugin.