Fishback

Thanks @shonleestudios

Having WP Engine support via live chat add “action=rp” to the dashboard caching > exceptions worked immediately for the invalid password reset message.

It has to be set for all sites using WPS Hide Login.

WPE recommend WPS Hide Login. Seems like they would want to globally fix this, not requiring site-by-site tickets.

I’m starting to have concerns about JetPack being a collection of plugins. If something goes wrong with one (as it has with subscriptions), I have to roll back all. Is putting all of the JetPack eggs in one plugin-basket a sound strategy? (Rolled back to 1.7 and fine for now.)

I had no problems with email subscriptions until 1.8.2. No emails are going out on any post by any author. So whatever 1.8.2 was trying to fix, it broke for me. https://GraphicJoke.com

Moderator: This is a duplicate. I did not realize I posted the issue prior. Can this be deleted?

[ Moderator Note: Please post code or markup snippets between backticks or use the code button. ]

Just upgraded to Hey Cookie 1.2.9 and the ie.css problem is still there. In functions.php because the if statement is commented out, in all cases the /ie.css is registered. This is creating conflicts in look with non-IE browsers as well as conflicts with the user custom CSS field since /ie.css is pulled in after the custom css is displayed in the header.

/*if( isset( $hey_cookie_responsive ) && $hey_cookie_responsive == 1 ) {
		wp_register_style( 'hcmedia', get_template_directory_uri() . '/media.css' );
		wp_enqueue_style( 'hcmedia' );
	}
else {*/
		wp_register_style( 'hcmediaie', get_template_directory_uri() . '/ie.css' );
		wp_enqueue_style( 'hcmediaie' );
	//}

PS.
The PayPal button at the bottom of theme options didn’t go anywhere for me.

<form action=”https://www.paypal.com/cgi-bin/webscr&#8221; method=”post”>

Will go PayPal the manual route!

I gather you are preparing for a responsive option in theme options (not showing yet) and for now are, in effect, defaulting to style inside ie.css. Well at least I know where to customize (since this all happens after the Custom CSS field statements.) I’m good for now!

Looks like functions.php. There is an “if” statement commented out and then by default ie.css is being brought in, even with no-ie browsers. So ie is overriding default style.css with non-ie browsers as well as overrides my own theme options css since those come in prior to this call.

/*if( isset( $hey_cookie_responsive ) && $hey_cookie_responsive == 1 ) {
wp_register_style( ‘hcmedia’, get_template_directory_uri() . ‘/media.css’ );
wp_enqueue_style( ‘hcmedia’ );
}
else {*/
wp_register_style( ‘hcmediaie’, get_template_directory_uri() . ‘/ie.css’ );
wp_enqueue_style( ‘hcmediaie’ );
//}

I dug a little further. It seems to be that the conflicting ie style call is being brought in at the end of the header by:

<?php wp_head(); ?>

Will dig further. Congrats on new job! I’m experimenting with Hey Cookie over here… GraphicJoke.com

To clarify, I am using Caorline’s own demo site to point out what seems to be an error in ie.css handling.

https://heycookie-demo.calobeedoodles.com/

A second call is being made to ie.css that is not suppressed in other browsers, and because it comes in last minute, it overrides default style.css in those other browsers.

This Firefox snapshot shows how the header h1.title has a 28px attribute which is *only* an ie.css attribute.

https://skitch.com/fishback/82rbn/hey-cookie-ie-css-example

I think you talked yourself down.