Ipstenu (Mika Epstein)
Forum Replies Created
-
Forum: Alpha/Beta/RC
In reply to: $wpdb->use_mysql was removed without being deprecatedYour post has been marked resolved.
Once the alpha version of WordPress is released, or more than a month has gone by without response, we “resolve” posts as a bit of a sanity check. It lets mods and volunteers know we don’t have to jump in and find an issue.
If you’re still having this issue with the newly released/current version of WordPress, please make a new post in https://ww.wp.xz.cn/support/forum/how-to-and-troubleshooting/
Forum: Plugins
In reply to: [Ban Hammer] Ban Hammer is Retired@idearius The code still works, and it’s still available. I would consider it safe to use (technically I still use the code personally, just not as a plugin to support).
@tharg3 Then I have a clarifying question.
The option is enabled by default. The issue that occurred caused the email to be sent instantly, even if the site was not fully authenticated within Google Analytics.
Plugin Guidelines stipulate tracking users must be opt in.
Is this email sent from the user’s site to themselves? If so, all good! If not (as in, it’s sent via your systems in any shape or form)? You have to change that to be opt in.
@caroh This is really a question about the add-on not the theme.
Since you already made https://ww.wp.xz.cn/support/topic/compatibility-issue-with-ocean-extra-and-beaver-builder-plugins-2/ I’m closing this, and you can continue there.
Forum: Plugins
In reply to: [Proxy Cache Purge] Add custom page to delete from varnishHi, you should add a set of custom pages to purge from varnish every time a article or post is created.
There are default pages, but I’m assuming you mean there should be a way for YOU to add custom pages. And if so, you can!
https://github.com/Ipstenu/varnish-http-purge/wiki/Custom-Filters#add-urls-to-be-purged
There’s no UX for it simply because I haven’t the time to sit and bash that out, but it’s something I’d like to do one day.
Forum: Plugins
In reply to: [Jetpack Social] Connecting to Facebook doesn’t show one page@ihenetudan Yep, it’s working finally!
Oh stupid Facebook.
Forum: Plugins
In reply to: [Proxy Cache Purge] PageSpeed in FAQPageSpeed, for reasons unknown to anyone sane, will modify your Cache-Control by default, telling browsers that the data is not cached, which in turn tells any proxy based cache system (nginx, varnish, etc) that the data is new.
By doing so, the proxy cache will regenerate your cache and effectively never work.
https://www.modpagespeed.com/doc/configuration#ModifyCachingHeaders
Please note I am not saying to DISABLE modPageSpeed, just to tell it stop screwing with your cache control and let cache be cached.
Forum: Plugins
In reply to: [Jetpack Social] Connecting to Facebook doesn’t show one page@bruceallen It was not working. Which is why I did the disconnect/reconnect.
Read the post you linked and someone pointed out this:
Adding business_management to the login scope made it work again.
Guess what MY site is?
Is that something you can check to make sure it’s allowed in the scope for your connector?
Forum: Plugins
In reply to: [Jetpack Social] Connecting to Facebook doesn’t show one pageFWIW if I try to adjust settings, it PROPERLY shows both pages when it asks what access I want to give it. I tried removing and adding back but the issue persists.
Forum: Reviews
In reply to: [Proxy Cache Purge] Age Header MissingIt’s a little unfair to post about this as a support question and a bad review in the next day, @bandsaw12
https://ww.wp.xz.cn/support/topic/age-header-missing/
And the error is correct. Nginx dropping support for age headers is something that happened, but it’s still an HTTP standard. The fact that Nginx is being weird doesn’t invalidate the check.
That said, the plugin will still work. The checker doesn’t work correctly for your site, but the cache-flush is not reliant on that.
Forum: Plugins
In reply to: [Proxy Cache Purge] Age Header MissingThis is true, Nginx does not have that out of the box. But that does mean that the check will never work because it cannot tell if the file has, in fact, been cached. Basically your server isn’t telling it if it was cached.
You can, however, MAKE an age header.
Edit: Actually that error means your Nginx box isn’t returning a proper X-Varnish header either. The checker was built to look for that and, if it’s valid, return true on all age checks. Make sure
'X-Varnish'is returningHIT- This reply was modified 2 years, 9 months ago by Ipstenu (Mika Epstein).
Forum: Plugins
In reply to: [Proxy Cache Purge] Clear cache not working on bedrock sites@lucasaffonso0 Before I implement that … how is a “bedrock” site different from any other WordPress site? I’d expect everyone to have this problem if it was universal, and thus far I have not.
To clarify here, you have an mistake in your code that is causing a “Try it” button to show on all plugins listed in the Plugin Search section.
Looking at your code:
add_action('in_admin_footer', [&$this, 'tryItOutScript']);That call lacks any checks to ensure it’s only running on YOUR plugins, so it shows up for every single one. You want to make that specific to your plugins only, otherwise you’re hurting all the other devs.
Forum: Plugins
In reply to: [Proxy Cache Purge] compatibility with php 8.2It’s tested up to 8.2 now 🙂 All safe!