reggieofarrell

@prometheus-fire If you’re curious, this is that code rolled into a simple plugin…

https://gist.github.com/reggieofarrell/3151943d93c739550873f371c9f176c9

@prometheus-fire I went digging in the codebase and figured out what is going on with this…

Certain plugins (the one I’m currently struggling with is Event Tickets) send a full HTML document for their HTML emails. However, this plugin (Email Templates) also creates a full HTML document and then just intercepts whatever is being sent through the wp_mail function and wraps it in their template.

That’s all well and good, but you don’t want to send an email that has an HTML document wrapped in another HTML document inside it. So they run the email content through the wp_kses_post function which strips certain html tags including <style> tags. That is what is causing the styles to print in plain text.

It plays well with WooCommerce but doesn’t seem to play well with most other things that send out HTML emails that would have <style> tags in them.

I did figure out a hacky solution where I’m grabbing the email content before they filter it (using their own mailtpl/email_content hook). I’m grabbing the email content and storing it to a txt file on the server and then re-injecting it from that file after all of their filtering runs. I do some similar filtering to theirs, but leave the <style> tags untouched. It’s hacky but it works.

@prometheus-fire Oh, that’s a bummer. I’ve been using this plugin for a while on various sites and have just recently run into this problem. Thanks for the update.

What did you switch to?

@prometheus-fire What was the resolution to this? I’m having this problem as well.

@hamza1010 If you are closing an issue you should post the solution as well.

Thanks @rockfire! That looks like what I’m looking for.

Thanks @rockfire. There is only one endpoint in this group currently and it fetches the downloads in a particular taxonomy by the term slug and transforms the data for each download before returning the results. So for example if the endpoint is…

vc/v1/downloads/get-by-content-group/{term-slug}

I need a function that can be called from anywhere that can clear the cache for that particular endpoint whenever a download is created or updated that is in a particular content-group. I know how to hook into post creation and update and do some logic there to determine the taxonomy and term. Is there a function I can call from my own code to clear the cache for a specific endpoint though? If not, is there one I can call from anywhere to clear everything under vc/v1/downloads/get-by-content-group/ or even just everything under vc/v1/downloads/?

Perfect. Thanks!

Hi @donncha. I tried the dev version as well as the newly available 1.6.8 version. Unfortunately the problem still persists. I put in a support ticket with Dreamhost again and they assured me again that all permissions are set as they should be. I’m not sure where to go from here.

I am also having this problem, but the globals are actually set in my wp-config.php. I had DreamHost check the file permissions and everything looks good there.

Warning! WP Super Cache caching was broken but has been fixed! The script advanced-cache.php could not load wp-cache-phase1.php.

The file /home/dh_32cx77/rachelhansbro.com/wp-content/advanced-cache.php has been recreated and WPCACHEHOME fixed in your wp-config.php. Reload to hide this message.

define('WP_CACHE', true);
define( 'WPCACHEHOME', '/home/dh_32cx77/rachelhansbro.com/wp-content/plugins/wp-super-cache/' );

Tried deleting the plugin and re-installing as well.

Host is WP Engine. Since my previous comment I realized that clearing the WP Engine cache and then coming back to the page does solve this issue. Thanks for the reply.

I ended up taking care of this by changing a CSS rule. Still doesn’t really make sense to me what was different. The rules wasn’t being overridden by something being out of order or anything like that. Anyhow, thanks for your help!

Thanks Frank. That helped me out a bit. I was able to add our custom.css file to the comma separated list of ignore file in the advanced options. It looks like it’s still being processed, but I guess maybe it’s just being minified now? For some reason, this fixes the problem in Chrome, but not Firefox. The issue is only affecting the header for logged in users, but this is a subscription site so most of our visitors are logged in. Any idea why this would be happening in Firefox and not Chrome? So strange!

I deleted all of the MOBIAPLUSHASH garbage and that seems to have fixed my problem. Thanks for pointing out the .htaccess file! I never would have checked that.

the .htaccess file in my root directory reads this…

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

###[==MOBIAPLUSHASH_<%DOMAIN_HASH%>=]###

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:X-WAP-PROFILE} !^$ [OR]
RewriteCond %{HTTP:PROFILE} !^$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*(Alcatel|Asus|Android|BlackBerry|Ericsson|Fly|Huawei|i-mate|iPAQ|iPhone|iPod|LG-|LGE-|MDS_|MOT-|Nokia|Palm|Panasonic|Pantech|Philips|Sagem|Samsung|Sharp|SIE-|Symbian|Vodafone|Voxtel|WebOS|Windows\s+CE|ZTE-|Zune).*$ [NC,OR]
RewriteCond %{HTTP_ACCEPT} application/vnd.wap.xhtml\+xml [NC,OR]
RewriteCond %{HTTP_ACCEPT} text/vnd.wap.wml [NC]
RewriteCond %{SERVER_PORT} !^443$
RewriteCond %{SERVER_NAME} ^www\.(.*)$
RewriteRule ^(.*) https://m.%1/ [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:X-WAP-PROFILE} !^$ [OR]
RewriteCond %{HTTP:PROFILE} !^$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*(Alcatel|Asus|Android|BlackBerry|Ericsson|Fly|Huawei|i-mate|iPAQ|iPhone|iPod|LG-|LGE-|MDS_|MOT-|Nokia|Palm|Panasonic|Pantech|Philips|Sagem|Samsung|Sharp|SIE-|Symbian|Vodafone|Voxtel|WebOS|Windows\s+CE|ZTE-|Zune).*$ [NC,OR]
RewriteCond %{HTTP_ACCEPT} application/vnd.wap.xhtml\+xml [NC,OR]
RewriteCond %{HTTP_ACCEPT} text/vnd.wap.wml [NC]
RewriteRule ^(.*) https://m.%{HTTP_HOST}/ [L]

###[=MOBIAPLUSHASH_<%DOMAIN_HASH%>==]###

Everything after the END WordPress tag in this looks very suspicious. It looks like it was added by my hosting company since they are called Aplus. Maybe I should just delete everything after the END WordPress tag?

I tried deactivating all of the plugins. It still re-directs my mobile browser to m.thewombrecording.com