nathanagin
Forum Replies Created
-
Thanks, will follow up with iThemes!
Thanks, Tyler! I logged into the hosting and even though the cache settings are set to 0 or N/A, I tested by clearing them and trying the links.
I also rolled back iThemes to 8.1.4 and I believe ALL 6 links are currently redirecting properly.
Could you test that on your end too? If that’s the case, I’ll reach out to iThemes about their recent update. Thank you!
Thanks for the helpful ideas, Tyler! I tested the redirects with the Enforce SSL turned off and there was no change (3 correct redirects, 3 incorrect redirects, as listed originally). When I disabled the entire iThemes plugin, the 3 previously correct were fine and only this one additional redirect then behaved correctly (but only in Firefox – all 3 were still incorrect in Chrome):
rethinkhomeinteriors.com/eval
The two versions with “https://www…” still redirected to /wp-admin, so something else appears to be going on with these Pretty Links redirects. Even using your redirect header instructions, what’s odd is that the redirect still appears to show as “iThemes Security” but the .htaccess has no code referencing iThemes, so I’m unclear how iThemes is controlling the redirects even when the plugin is deactivated.
I did come across this post referencing the same issue and someone mentions an updated function (wp_safe_redirect()) in a recent update to iThemes, but it’s not definitive and again, even with the plugin turned off, the redirects are behaving improperly.
Thanks, Tyler! We do have “Enfore SSL” selected in iThemes and I would agree with the assessment, except https://rethinkhomeinteriors.com/eval is redirecting correctly.
More info on that iThemes feature here.
So why would https:// work, but https://www won’t?
Also, how are we able to check the headers for a Pretty link redirect? Once the page redirects to the final destination, I’m unable to check the headers for the /eval link – I can only check for /wp-admin or the target page.
- This reply was modified 1 year, 7 months ago by nathanagin.
Forum: Plugins
In reply to: [WPFront Notification Bar] Not showing on front-end (have added JS exclusion)Here’s what I currently have in “Exclude scripts from Autoptimize”:
seal.js, js/jquery/jquery.js,wpfront-notification-bar.js,jquery.c.js
I had only added “wpfront-notification-bar.js,jquery.c.js” when I had this issue; the previous exclusions had already been there.
Forum: Plugins
In reply to: [WPFront Notification Bar] Not showing on front-end (have added JS exclusion)We discovered this site was also running Autoptimize, and when we added the same .js files to exclude there, the notification bar appeared. All set!
Forum: Plugins
In reply to: [WP Fastest Cache] Conflict with recognizing membersPerfect, thank you!
Forum: Plugins
In reply to: [WP Fastest Cache] Conflict with recognizing membersThank you!
I have not removed the wp-login.php, but have members using the following page (and only here, not on every page):
/membership-login/
So I’ve added the rule to exclude ‘If REQUEST_URI Contains “membership-login”‘
That should be sufficient, correct?
Ok, I’ve resumed the email thread we already had going, please look for subject: business pro theme – conflict with Tabs
thanks!
Hi there-
Thanks for looking into this. As I mentioned in the original post:
I’ve tested this on a fresh install of WordPress with *only* this plugin installed and replicated the same behavior with this theme.
So it doesn’t appear other plugins would be creating an issue.
Sure – I had actually emailed both the parent and child theme to the wpshopmart email address on 9/4. I was directed to your support forum, but it’s not clear how I sign up for that without an invitation. I will re-send the parent theme today to that same email address. Thanks.
thanks – emailed that over today.
This is the theme:
https://my.studiopress.com/themes/business/
As it’s a premium theme, I don’t believe there’s a secure way to share a link, correct?
Thanks!
Sure, just let me know how to send you the ZIP. Thanks!
I’ve discovered this is only happening in Chrome and Brave, but not Safari or Firefox. Still unsure what could be the cause.