IniLerm
Forum Replies Created
-
Forum: Plugins
In reply to: [Advanced IP Blocker] A couple of items I foundHi @spectraemail,
Thank you so much for this excellent and very detailed report! This is incredibly helpful feedback. The behavior you’re describing—locations showing correctly in the Security Log but appearing as “Not available” for the map link in IP Management—almost always points to an issue with the configured Geolocation Provider.
Here’s what is likely happening:
- When a block occurs, the location data is fetched and saved directly into the Security Log. This is why the log entry is correct.
- The IP Management table, however, pulls fresh location data from a separate cache to display the “View Map” button. If the Geolocation API fails to provide coordinates (latitude/longitude) when this cache is being built, the map button won’t appear, even if the city/country name is known.
This usually happens if the currently selected Geolocation Provider has reached its free query limit or is experiencing a temporary service disruption.
How to Fix This (Recommended Solution):
We strongly recommend switching to the ip-api.com provider, which is the new default for the plugin. It’s free, reliable, does not require an API key for standard use, and supports all plugin features including ASN lookups.
Here are the steps to fix it:
- In your WordPress admin panel, go to Security > Settings > General.
- Scroll down to the “External API Settings” card.
- In the “Geolocation Provider” dropdown, select ip-api.com.
- Scroll to the bottom of the page and click “Save Changes”.
- Finally, go back to the “External API Settings” card and click the “Clear Location Cache” button. This will force the plugin to refetch the location data for your blocked IPs using the new, reliable provider.
After clearing the cache, please check the IP Management tab again. The “View Map” button should now reappear for all entries as their location data is repopulated.
If the problem persists after following these steps, it might indicate a specific issue with your server’s ability to connect to the API or a limitation of the API provider selected in their Free plans.
Thank you again for helping us improve the plugin! Let me know if that solves the issue for you.
Best regards.
Forum: Plugins
In reply to: [Advanced IP Blocker] A couple of items I foundHi spectraemail,
Thank you so much for this excellent and detailed bug report! You are absolutely right, and your suspicion about the object cache is spot-on. This is a fantastic catch and helps us make the plugin better for everyone.
Let me explain exactly what’s happening, as you’ve correctly identified the cause:
- Dual Record System: When an IP is blocked, the plugin creates two records: a permanent entry in the database list (which you see in the “Blocked IPs” table) and a temporary active flag (a “transient” in WordPress) that tells the plugin to actively block traffic from that IP.
- The Object Cache Effect: The “Status” column in the table checks for the existence of that temporary active flag. In hosting environments with an aggressive, persistent object cache (like Redis, Memcached, or high-performance server-level caching), a synchronization issue can occur. The temporary flag isn’t immediately read from the fresh cache, so when the table loads, it doesn’t see the “active” flag and incorrectly assumes the block has expired, even though the permanent entry is still there.
The most important thing to know is that the IP block itself is almost certainly still active for real visitors. The issue is primarily a visual glitch in the status column in the admin area.
As an immediate workaround, purging your site’s object cache should resolve the visual discrepancy. You can usually find this option in your hosting control panel or in the settings of your caching plugin (e.g., “Redis Object Cache”, “LiteSpeed Cache”, etc.).
We are about to release version 8.4.4 which includes several other important stability fixes. Thanks to your report, we have already developed a permanent solution for this caching issue, and it is scheduled to be included in the maintenance release that will follow shortly after, version 8.4.5. The fix makes the status check much more robust so it won’t be fooled by a stale cache.
Thank you again for your valuable contribution to improving the plugin. We really appreciate it!
Best regards.
Forum: Plugins
In reply to: [Advanced IP Blocker] A couple of items I foundYou were absolutely right! (Your suggestion is in the latest version)
Hi @spectraemail,
Wow, thank you for following up! First of all, I’m glad we were able to catch and fix that CSS bug before it caused you any more trouble. Your timing was perfect.
Secondly, regarding your pseudo-code for the block duration… you’re a natural! You’ve described the logic perfectly, and I’m thrilled to tell you that your suggestion was so good that we implemented it immediately.
If you update to the latest version (8.4.4.3), you will find that the plugin now behaves exactly as you described. Setting the duration to 0 for any block type in the settings will now correctly make it permanent, and the UI (in the “Blocked IPs” and “Security Log” tables) will display the status as “Permanent”.
You were absolutely right – forcing users to create a separate manual block was clumsy. Your idea makes the system much more intuitive and flexible. It was a fantastic suggestion and the plugin is better because of it.
Thank you once again for your incredible feedback and for helping to improve the project. Your contributions are genuinely invaluable.
Best regards!
Forum: Plugins
In reply to: [Advanced IP Blocker] A couple of items I foundHi @spectraemail,
Thank you so much for the incredibly valuable feedback and for digging into the plugin’s functionality. These are exactly the kind of questions that help make the plugin better for everyone. Let me address both of your items.
1. Block Duration and Expiration
You’ve likely encountered a limitation in how WordPress transients work. While our plugin lets you enter a large number of minutes for the block duration, WordPress stores this expiration time in its database in a way that can be affected by how it manages its internal cache and scheduled events (WP-Cron). For very long durations (many days or months), some hosting environments or object cache configurations might cause the transient to be cleared earlier than expected.
While we investigate a more robust method for extremely long-term blocks in a future version, the most reliable way to ensure a block is effectively permanent is to set the duration to 0.
For block types like Manual ASN and Manual IP Block, setting the duration to 0 in the settings (or simply not having a specific duration for a manual block) makes them permanent. They will never be automatically cleared by the expiration system. For other temporary block types, we recommend using durations up to a few weeks for maximum reliability. Thank you for bringing this to our attention!
2. Unblocking vs. Whitelisting an IP
You are 100% correct. If you’re on a dynamic IP (like with a VPN), you absolutely do not want to whitelist a temporary IP address. You just want to remove the current block.
The good news is that the plugin is designed for exactly this scenario. The “Whitelist” button in the Security Log is a shortcut for convenience, but the primary tool for managing blocks is the IP Management > Blocked IPs tab.
Here’s the recommended workflow for your situation:
- Find the Blocked IP: Go to the Security Log and identify the IP address that was blocked.
- Go to the Blocked IPs Tab: Navigate to IP Management > Blocked IPs.
- Search and Unblock: Paste the IP address into the search bar on that page to quickly find the entry. Then, simply click the “Unblock” button for that row.
This action will remove that specific IP from all blocklists and clear its temporary block, without adding it to the permanent whitelist. It’s the perfect solution for unblocking a dynamic VPN IP.
For advanced users like yourself, you can also do this instantly via WP-CLI:
- To find the IP: wp advaipbl blocked
- To unblock it: wp advaipbl unblock <the_ip_address>
Thank you again for your excellent questions and for being such an engaged user. This is the kind of feedback that is invaluable to the project’s development.
Best regards.
Forum: Reviews
In reply to: [Advanced IP Blocker] I’ve Been Waiting For This! Well Done!Thank you so much for the detailed review!
Hi @spectraemail,
Thank you for taking the time to leave such a thoughtful and positive 5-star review! It’s fantastic to hear that you’re finding the plugin stable and that the core features like the WAF, Geoblocking, and ASN blocking are working well for you.
We put a lot of effort into making the blocking duration flexible, so I’m really glad you find that feature handy.
I’m also very intrigued by your ideas! There are no “dumb” suggestions when it comes to improving security and usability. Please feel free to share them in the support forum or via our website’s contact form whenever you’re ready. User feedback is what drives this project forward.
Thanks again for your support and good luck to you too!
Forum: Reviews
In reply to: [Advanced IP Blocker] I’ve Been Waiting For This! Well Done!Thank you so much for your kind words and for taking the time to leave this wonderful feedback! I’m thrilled to hear that you’re finding the plugin well-arranged and easy to set up. My main goal was to create a comprehensive yet user-friendly security tool, so your comment means a lot. I look forward to any further feedback you might have after you’ve had more time to evaluate it. Thanks again!
Yo también comenté la linea 72 en el init.php y en apariencia todo funcionaba bien pero al hacer esto se deshabilita la comprobación de la versión del framework del plugin y puede afectar a su correcto funcionamiento.
entonces ante la duda he preferido volver a la versión anterior del plugin 4.15.0 hasta que los desarrolladores actualicen y solucionen el problema.
Pude descargar la versión anterior desde https://downloads.wordpress.org/plugin/yith-woocommerce-product-add-ons.4.15.0.zip
Todas las versiones anteriores se pueden descargar desde https://wordpress.org/plugins/yith-woocommerce-product-add-ons/advanced/
Forum: Plugins
In reply to: [YITH WooCommerce Product Add-Ons] Version 4.16 critical errorThanks @scollonp
I have commented line 72 in init.php and the latest version 4.16.0 works perfectly
//*yit_maybe_plugin_fw_loader( YITH_WAPO_DIR );
Forum: Plugins
In reply to: [YITH WooCommerce Product Add-Ons] Version 4.16 critical errorThe only solution for the moment is to go back to the previous version 4.15
- This reply was modified 1 year, 9 months ago by IniLerm.
The only solution for the moment is to go back to the previous version 4.15
- This reply was modified 1 year, 9 months ago by IniLerm.
Forum: Plugins
In reply to: [YITH WooCommerce Product Add-Ons] Version 4.16 critical errorThe same problem
Current plugin: YITH WooCommerce Product Add-ons & Extra Options (version 4.16.0)
PHP version 8.2.26
Error Details
=============
An error of type E_ERROR was caused in line 72 of the file /wp-content/plugins/yith-woocommerce-product-add-ons/init.php. Error message: Uncaught Error: Call to undefined function yit_maybe_plugin_fw_loader() in /wp-content/plugins/yith-woocommerce-product-add-ons/init.php:72
Stack trace:
#0 /wp-settings.php(526): include_once()
#1 /wp-config.php(114): require_once(‘/homepages/2/d6…’)
#2 /wp-load.php(50): require_once(‘/homepages/2/d6…’)
#3 /wp-admin/admin.php(34): require_once(‘/homepages/2/d6…’)
#4 /wp-admin/plugins.php(10): require_once(‘/homepages/2/d6…’)
#5 {main}
thrown