Daniel Bachhuber
Forum Replies Created
-
Forum: Plugins
In reply to: [WP SAML Auth] x509 Cerificate PathHey @iconicmatt:
Do I simply add the certificate to a www.ads-software.com directory somewhere? How and where do I add it so that it is findable by the plugin?
You’ll need to put the x509 certificate somewhere on your web host’s filesystem that is:
1. Accessible by the WP SAML Auth plugin.
2. Not accessible from the web.Where the file should be located will vary from host to host. For example, on Pantheon you can put your files in a
private
directory in the root of your Git repository, or inwp-content/uploads/private
if you’d like the file stored outside of version control (documentation).Forum: Plugins
In reply to: [WP SAML Auth] Logout URL redirect to homepageYep. Because WP SAML Auth redirects to Watchguard to log the user out of the IdP, Watchguard will need to be configured to redirect back to the homepage.
Forum: Plugins
In reply to: [WP SAML Auth] Logout URL redirect to homepageThanks for the question. They are redirected to that URL so they get logged out of the IdP. In order to have the user end up on the homepage, you’ll need to configure that redirect behavior in your IdP.
Who configured WP SAML Auth and your IdP originally?
Forum: Plugins
In reply to: [WordPress Native PHP Sessions] Sessions with user id 0You’re welcome!
Forum: Plugins
In reply to: [WordPress Native PHP Sessions] Sessions with user id 0Hey @ittalentmx,
Yep! When the
user_id
value is 0, it’s a session for a logged-out user. You’re seeing lots of different IP addresses because there are lots of different logged-out users.Hope this helps clarify.
Sorry about that! I guess I messed something up with
composer.json
when I was changing the supported PHP version.I’ve just tagged v2.0.1 with a fix.
Forum: Plugins
In reply to: [Solr Search for WordPress] We have 2022 and it still depends on Solr 3.6???Hey @fhwebcs,
You’re welcome!
But is there any chance that this plugin will be updated to work with latest Solr 8.11.1 (or newer ;))?
At this point, it’s unlikely. I haven’t heard of any plans to update Solr on Pantheon’s infrastructure, which is what this plugin is tied to.
Security-wise, a warning note should be placed directly above the description details (imho).
Want to submit a pull request for that?
Forum: Plugins
In reply to: [WP Redis] PHP fatal error: wp_cache_add() cannot be redefinedGreat!
Forum: Plugins
In reply to: [WP Redis] PHP fatal error: wp_cache_add() cannot be redefinedHey @sdvservices,
I think there’s something funky in your site setup. It looks like WP Redis’
object-cache.php
is getting loaded first, and then WordPress core’scache.php
is loaded afterwords.The standard behavior is to load
wp-content/object-cache.php
if there is one, otherwise loadwp-includes/cache.php
. Here’s the corresponding logic: https://github.com/WordPress/wordpress-develop/blob/b161cfc1ff2566c7be7425339b695aa404bf8dce/src/wp-includes/load.php#L655-L738It’s hard to say what the problem is without access to your codebase. However, it’s a problem unique to your codebase/configuration, not a problem with WP Redis.
Hope this helps point you in the right direction!
Forum: Plugins
In reply to: [WP Redis] Sudden cache collisions (newly added site)It was an oversight by me, though the salt being a constant while the other redis connection config residing in
$_SERVER
contributed a bit to this accidental mix up.Makes sense — no worries.
Does a Redis server emit a notice/warning when a database index higher than the set up max database index number is used by the client? If this is the case, WP Redis could show a warning message in backend.
I’d be open to a pull request if this is something you want to explore!
Is there a particular reason why the key salt is expected to be in a constant in contrast to being in
$_SERVER
as the other redis connection configuration? Because it isn’t a connection setting that doesn’t concert the Redis server?
On the other hand, this has been the case for a very long time now, so it shouldn’t be changed, maybe extended to other locations the salt can be expected to be in ($_SERVER
).WP_CACHE_KEY_SALT
is a constant out of WordPress core, while$_SERVER
is from the original implementation of WP Redis. Different origin stories, essentially.Can a default salt be used, e.g. the site name or maybe a GUIID?
This would require an additional database lookup on every request, so probably an over-optimization at this point.
Can WP Redis detect a cache collision on its own and show a warning in backend? Like storing something unique and site-specific under some key and when it finds an existing value that mismatches, it is probably a cache collision with another site/setup?
Potentially, yes, although this seems like another over-optimization. Is there something we could make more obvious in the installation instructions? https://cln.sh/x5j9YS
Forum: Plugins
In reply to: [WP Redis] Sudden cache collisions (newly added site)Sorry for the troubles, @strarsis !
Need anything else on our end?
Forum: Plugins
In reply to: [WP Redis] Setting for username & password with Redis 6?Oops, was signed in to the wrong account with that last comment ??
Forum: Plugins
In reply to: [WP SAML Auth] Remove login button from the wp-login pageHey @helen35,
Glad you’ve found the plugin helpful ??
I was wondering if there is a way to remove the sign in button from the wp-login page. I just want my google workspace users to login with the SAML app in their Google Dashboard.
Just to confirm, you’d like to remove this part? Or are you hoping to replace the whole thing?
Forum: Plugins
In reply to: [WP Redis] Does this plugin work with WooCommerceWP Redis should work just fine with WooCommerce. It serves as a drop-in replacement for WordPress’ internal object cache. As long as WooCommerce is interfacing with the object cache, WP Redis will handle the requests just fine.
Forum: Plugins
In reply to: [WP Redis] Multisite compatibilityHey @mattrin,
Yes, WP Redis does work with multisite. It is an implementation of WordPress core’s internal object cache, and uses the same mechanism for generating cache keys.
If you run into any issues, feel free to weigh in with more detail on this thread.