partynoparty
Forum Replies Created
-
Forum: Plugins
In reply to: [Redirection for Contact Form 7] Redirect settings not showingthanks
Forum: Plugins
In reply to: [WooCommerce] No link to create an account on checkout pageThanks for the reply. I was aware of that option. I intentionally did not choose that setting because I do not want the account creation process to be tied to the checkout process. This is related to our tax exempt process that I mentioned in my post. What I am looking for is a checkout process that would prompt the user to create an account PRIOR to the actual checkout, which would give our customers a chance to enter their tax exempt status prior to paying.
Forum: Plugins
In reply to: [Contact Form 7] Google Ads – Tracking Clicks – Adding code to Submit buttonI’m trying to do the same thing. I’m not positive that this will work, but this is what I just implemented on my site.
document.addEventListener( ‘wpcf7mailsent’, function( event ) {
return gtag_report_conversion(‘/#wpcf7-f171-o1’);
}, false );In my case, I pulled the url from the action value of the contact form. I don’t know if this is the correct way to do, and I won’t know for a few days if this is actually working or not. I also noticed that the page reloads when this event is triggered, which isn’t ideal. I’d be curious if there were a better way to do this.
This didn’t seem to fix it for me. I’m seeing the following errors in the dev console:
wp-color-picker-alpha.min.js?ver=5.5:8
Uncaught ReferenceError: wpColorPickerL10n is not definedwp-auth-check.min.js?ver=5.5:2
Uncaught TypeError: Cannot read property ‘hasClass’ of undefinedForum: Plugins
In reply to: [W3 Total Cache] Blog page not updating after new postIt also does not seem to be consistent. I just published a test post, and the blog page updated for me. The issue was reported to me by another admin that published a post earlier today and did not see the blog page updated on her end.
Forum: Plugins
In reply to: [W3 Total Cache] Blog page not updating after new postThe blog home page is specified as Posts Page, so it seems like it should be updating after a new post is published.
Forum: Plugins
In reply to: [W3 Total Cache] Blog page not updating after new postSpecify the pages and feeds to purge when posts are created, edited, or comments posted.
Posts page
Post page
Blog feedSpecify the feed types to purge:
rss2 (default)Purge limit:
10Forum: Fixing WordPress
In reply to: Automatic redirects when changing blog URLsthanks @dominic_ks. I’ll look into that plugin.
Forum: Fixing WordPress
In reply to: Automatic redirects when changing blog URLsThanks @dominic_ks. We’re using the SEOPress plugin, but you’re probably right that the warning is coming from the plugin, and not WP. I suspected as much, but just wanted a few more opinions on the matter.
I’m still curious about whether or not the blog redirects are created automatically by WP, or if that is something I will have to set up in htaccess.
I reached out to W3 Total Cache and got this response:
I’ve spoken with the team and apparently there is a conflict between W3 Total Cache Page Caching and AO cache.
As I’ve stated above Stylesheets should have a MIME type of text/CSS. Your server is serving up a MIME type (‘text/html’) so the problem is with the CSS file.
Thank you!Not entirely clear what caused the conflict, though.
Thank you for the response. I am curious, the lines that I removed from the htaccess file, would they have been written into the file by W3 Total Cache, or would they have to have been manually added to the htaccess file a web developer? I’m afraid I only recently took over management of this web page, so I don’t know the full history and what the previous developers may have done.
I haven’t yet, but I will follow up with them about it.
Just to follow up, I was able to resolve this issue. Turns out the problem was related to our htaccess file. The following lines were causing an issue and had to be removed:
# RewriteCond “%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}” -f
# RewriteRule .* “/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}” [L]That makes sense. We did recently change hosts. I’ll check the host caching policy, and also try out the 404 fallback option. Thanks!
Thanks. I was able to locate the email. It had gone to my spam folder.