Title: slewisma's Replies | WordPress.org --- # slewisma [ ](https://wordpress.org/support/users/slewisma/) * [Profile](https://wordpress.org/support/users/slewisma/) * [Topics Started](https://wordpress.org/support/users/slewisma/topics/) * [Replies Created](https://wordpress.org/support/users/slewisma/replies/) * [Reviews Written](https://wordpress.org/support/users/slewisma/reviews/) * [Topics Replied To](https://wordpress.org/support/users/slewisma/replied-to/) * [Engagements](https://wordpress.org/support/users/slewisma/engagements/) * [Favorites](https://wordpress.org/support/users/slewisma/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 34 total) 1 [2](https://wordpress.org/support/users/slewisma/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/slewisma/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/slewisma/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Font Awesome] Can’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is active](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [7 months, 1 week ago](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/#post-18666162) * Yes, 5.1.3 still works correctly in my test site here. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[List category posts] Vulnerability posted by Wordfence](https://wordpress.org/support/topic/vulnerability-posted-by-wordfence/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [7 months, 1 week ago](https://wordpress.org/support/topic/vulnerability-posted-by-wordfence/page/2/#post-18666098) * In case it is helpful, here are some tips from Wordfence for securing local file inclusion when it is needed: [https://www.wordfence.com/blog/2025/10/how-to-find-local-file-inclusion-lfi-vulnerabilities-in-wordpress-plugins-and-themes/#how-to-prevent-lfi-vulnerabilities](https://www.wordfence.com/blog/2025/10/how-to-find-local-file-inclusion-lfi-vulnerabilities-in-wordpress-plugins-and-themes/#how-to-prevent-lfi-vulnerabilities) Not sure if these are practical in the List Category Posts code or not but thought I’d post them here in case they’re helpful for addressing the security risk while not breaking an important part of how the plugin works. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Font Awesome] Can’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is active](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [7 months, 2 weeks ago](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/#post-18657047) * That 5.1.2-1 experimental release does fix the problem on the sites where I use Toolset and Font Awesome. I tested on a copy on localhost. * I opened a ticket with Toolset today referencing this support post as they seemed to want proof it was a Toolset issue before doing more work on their side of things in older, now closed, tickets. Your post from yesterday seems to explain it pretty well. Not sure if they’ll act on that or not. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Font Awesome] Can’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is active](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [7 months, 2 weeks ago](https://wordpress.org/support/topic/cant-edit-post_content-in-classic-editor-if-plugin-v5-0-1-or-v5-0-2-is-active/#post-18656939) * Having the same issue on a bunch of client sites where I use Toolset. My workaround is to not use the Font Awesome plugin and load Font Awesome by script instead. Since I don’t need access to font awesome in classic or block editor, this works for me but I’d still prefer if Toolset and Font Awesome can work this out and fix it in either or both plugins. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[List category posts] SECURITY RISK](https://wordpress.org/support/topic/security-risk-32/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [8 months, 3 weeks ago](https://wordpress.org/support/topic/security-risk-32/page/2/#post-18611276) * Wordfence and ManageWP still show it as vulnerable too which gives clients anxiety. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Min Max Step Quantity Limits Manager for WooCommerce] Memory exhausted error(s) with WooCommerce 10.1.0](https://wordpress.org/support/topic/memory-exhausted-errors-with-woocommerce-10-1-0/) * Thread Starter [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [8 months, 4 weeks ago](https://wordpress.org/support/topic/memory-exhausted-errors-with-woocommerce-10-1-0/#post-18601571) * This update appears to have fixed the issue. Thank you. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Ultimate Before After Image Slider & Gallery - BEAF] Load text domains using the init hook (error since WP 6.8)](https://wordpress.org/support/topic/load-text-domains-using-the-init-hook-error-since-wp-6-8-2/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [9 months ago](https://wordpress.org/support/topic/load-text-domains-using-the-init-hook-error-since-wp-6-8-2/#post-18597725) * Any progress on this issue? Most other plugins fixed this last year when it first started happening with a WordPress update. It is filling the error logs on servers. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[List category posts] SECURITY RISK](https://wordpress.org/support/topic/security-risk-32/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [11 months ago](https://wordpress.org/support/topic/security-risk-32/#post-18505657) * Fernando, does your comment about 0.91.0 having just went out mean that you will be addressing the vulnerability, just not immediately since you just did a release? Clients get nervous when they see the warning from Wordfence, Jetpack, etc. I understand the risk is low due to the needed access levels and that Wordfence’s WAF may provide protection anyway. It’d be good to be able to tell the clients that the risk is minimal and that a future update will address it rather than not knowing if it will be addressed or not. Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Asgaros Forum] Vulnerability reported](https://wordpress.org/support/topic/vulnerability-reported-3/) * Thread Starter [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year ago](https://wordpress.org/support/topic/vulnerability-reported-3/#post-18426457) * Thanks for the quick resolution! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] PHP warning: Function called incorrectly](https://wordpress.org/support/topic/php-warning-function-called-incorrectly/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year ago](https://wordpress.org/support/topic/php-warning-function-called-incorrectly/#post-18418437) * Every other plugin maker of plugins I use on client sites that had this issue fixed it months ago. It’d be really nice to have it officially fixed in the repository version Responsive Lightbox soon. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[StellarPay - Stripe Payment Gateway for WooCommerce] How to connect to existing Stripe Account?](https://wordpress.org/support/topic/how-to-connect-to-existing-stripe-account/) * Thread Starter [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year, 1 month ago](https://wordpress.org/support/topic/how-to-connect-to-existing-stripe-account/#post-18410820) * I think I found the root cause. The customer’s Stripe account is “managed by” another business/app. That was apparently okay with the legacy checkout method but you cannot connect WooCommerce to that kind of Stripe account with the newer checkout method. Unfortunately it looks like the only solution is going to be for the customer to setup a new Stripe account directly with Stripe. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[StellarPay - Stripe Payment Gateway for WooCommerce] How to connect to existing Stripe Account?](https://wordpress.org/support/topic/how-to-connect-to-existing-stripe-account/) * Thread Starter [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year, 1 month ago](https://wordpress.org/support/topic/how-to-connect-to-existing-stripe-account/#post-18408531) * Hi Devin, it’s been a while. Nice to see you here. My issue is that when I get to the list of businesses, it says the one I want to choose is ineligible as it is connected to another app. I am thinking I might be able to get it to work if I revoke access to the previous WooCommerce connection but, if it doesn’t work, that makes the process of reverting to the old site that much more complex which equals more downtime and late night work.It seems like I should be able to connect WC Stripe and StellarPay since I routinely connect WC Stripe and Gravity Forms Stripe or GiveWP Stripe from the same site but it doesn’t let me. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[StellarPay - Stripe Payment Gateway for WooCommerce] Why is there a pay button on the after checkout screen?](https://wordpress.org/support/topic/why-is-there-a-pay-button-on-the-after-checkout-screen/) * Thread Starter [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year, 2 months ago](https://wordpress.org/support/topic/why-is-there-a-pay-button-on-the-after-checkout-screen/#post-18333283) * Hi Devin, good to hear from you. * Hi Ramon, Does that code return without unsetting the buttons if there is no subscription involved? I’m seeing these buttons on regular products, not subscriptions, on the site where I discovered the issue. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shipping Live Rates and Access Points for UPS for WooCommerce] 250002 Error Persists](https://wordpress.org/support/topic/250002-error-persists/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year, 5 months ago](https://wordpress.org/support/topic/250002-error-persists/#post-18190179) * My two clients are still connected. I’ll keep checking through the week as the connection usually lasts for a week or more before dropping. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shipping Live Rates and Access Points for UPS for WooCommerce] 250002 Error Persists](https://wordpress.org/support/topic/250002-error-persists/) * [slewisma](https://wordpress.org/support/users/slewisma/) * (@slewisma) * [1 year, 5 months ago](https://wordpress.org/support/topic/250002-error-persists/#post-18183657) * Yes, each time this happens I have to revoke access and then authorize again. The ability to use an API Key doens’t seem to work on its own without the OAuth login also being in place. Viewing 15 replies - 1 through 15 (of 34 total) 1 [2](https://wordpress.org/support/users/slewisma/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/slewisma/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/slewisma/replies/page/2/?output_format=md)