Jeff Sterup
Forum Replies Created
-
Forum: Plugins
In reply to: [Honeypot Toolkit] Plugin Causing Fatal ErrorWhat is the error?
You’ll need to turn those back on to use it.
Without pretty permalinks like product-category or product plugin organizer will not work. It uses the URL structure to find the plugins you need enabled/disabled.
Forum: Plugins
In reply to: [Plugin Organizer] Issues with update to v10.2@demironmanx PO is built to work with custom post types. But you do need to check that the post type is enabled on the settings page to enable/disable plugins on their edit screen. If you are using a plugin filter that setting doesn’t matter because when plugin organizer makes the decision to enable/disable plugins on a page or custom post type those objects don’t exist yet. So everything is based on URL. Something else is stopping the plugins from being enabled/disabled like you are expecting. Try using the debug messages to see what is being found in the database and applied to your custom post type. The debug messages are in your browser console after you turn them on.
Forum: Plugins
In reply to: [Plugin Organizer] Issues with update to v10.2@oxfordmetadata no. You can only use the * character once. And only to replace one piece of the URL structure in between the / characters. So if you want a plugin filter to match these:
/category/cat1/postname/
/category/cat1/cat2/postname/
/category/cat1/cat2/cat3/postname/You could add a plugin filter with /category/cat1/ and select “also affect children”. But that would only work if you didn’t have a plugin filter with a longer permalink that matched the pages URL structure. Plugin filters start at the full URL looking for a match. So in the case of /category/cat1/cat2/cat3/postname/ it would look for these URLs one at a time in this order.
/category/cat1/cat2/cat3/postname/
/category/cat1/cat2/cat3/*/
/category/cat1/cat2/*/postname/
/category/cat1/*/cat3/postname/
/category/*/cat2/cat3/postname/
/*/cat1/cat2/cat3/postname/
/category/cat1/cat2/cat3/
/category/cat1/cat2/*/
/category/cat1/*/cat3/
/category/*/cat2/cat3/
/*/cat1/cat2/cat3/
/category/cat1/cat2/
/category/cat1/*/
/category/*/cat2/
/*/cat1/cat2/
/category/cat1/
/category/*/
/*/cat1/
/category/
/*/
/If it finds a match along the way it will stop looking. So if it found a plugin filter with /category/cat1/cat2/cat3/*/ set as the permalink that had “also affect children” set on it then it would stop looking and apply the rules set up on that plugin filter.
I added the help text you suggested with a few verbiage changes in version 4.5.2 along with a few other help text changes.
Forum: Plugins
In reply to: [Plugin Organizer] Plugin organizer not working on alias subdomainYou would need to create plugin filters for everything. Plugin organizer relies on the permalink.
Forum: Plugins
In reply to: [Plugin Organizer] Loosing Plugin Order after UpdateI think I may have fixed it. WordPress automatically reset the load order when plugins are activated/deactivated. I’m wondering if that was happening during the update. I added code to reset the order back to what you have saved if that happens. It might happen again since you will have the old code in place when you update this time. Unless you manually update it by placing the new version in your plugins directory with FTP. Version 10.2.2 has the fix. Hopefully that works.
Forum: Plugins
In reply to: [Plugin Organizer] Issues with update to v10.2If you have the plugins globally disabled and only enabled on those pages you more than likely need to add the ajax endpoints. For a plugin like Woocommerce you need to have it enabled on your homepage because that is where its ajax calls end up going. For others it is the REST API. So the URL is something like this https://www.sterup.com/wp-json/wp/v2/….. You might have to load the page and look for javascript errors or 404 errors generated by javascript to determine what is missing and where you need to enable the plugins.
The trailing slash can either be added automatically or not. That is an option on the options page “Auto Trailing Slash”.
Wildcards are limited. You can only use the * character and it can only cover one part of the URL. You have to enable Fuzzy URL Matching on the settings page for this to work. So for a URL structure like this:
https://www.sterup.com/category/cat1/postname
https://www.sterup.com/category/cat2/postname
https://www.sterup.com/category/cat3/postname2
https://www.sterup.com/category/cat1/postname34A filter with this as the permalink https://www.sterup.com/category/cat1/* would match https://www.sterup.com/category/cat1/postname and https://www.sterup.com/category/cat1/postname34.
A filter with this as the permalink https://www.sterup.com/category/*/postname would match https://www.sterup.com/category/cat1/postname and https://www.sterup.com/category/cat2/postname
There are also options to ignore the URL protocol so that http and https are treated the same.
There is also an option to ignore URL arguments so that https://www.sterup.com/category/cat1/postname and https://www.sterup.com/category/cat1/postname?foo=foo&foo2=foo are treated the same.
Forum: Plugins
In reply to: [Plugin Organizer] Issues with update to v10.2That CSS file somehow disappeared. I put it back in the css folder where it belongs. So that should be fixed with version 10.2.1.
Yes. You need to regenerate the permalinks. There is a tab on the settings page for Plugin Organizer to do that for you.
FYI I just purchased my new domain and I’m still setting the site up. It will hopefully be more useful in the future.
Forum: Plugins
In reply to: [Plugin Organizer] PHP 8.3 warnings/deprecationsVersion 10.2.1 should fix this issue.
Forum: Plugins
In reply to: [Honeypot Toolkit] Breaks wp-cliI have 127.0.0.1 whitelisted. That might be why it’s working for me. Can you add 127.0.0.1 to your whitelist and try it again?
Forum: Plugins
In reply to: [Honeypot Toolkit] Breaks wp-cliI can run WP-CLI with no issues while having Honeypot Toolkit active. Can you give me any logs showing what the issue is?
Forum: Plugins
In reply to: [Plugin Organizer] PHP 8.3 warnings/deprecationsCan you give me more information? Like the line number from the logs? I’m running PHP 8.3.12 and don’t get those warnings.
Forum: Plugins
In reply to: [Plugin Organizer] Filters stop working if browser closedIf you close your browser you’re logged out of WordPress. So you would no longer have a role. That’s why the role filter isn’t getting applied.