fbf3

Dev console errors further down. Note: I had trouble upgrading from IP Geo Block 3.0.17 to the latest 3.0.17.4 some time back, so stayed at 3.0.17 until now. I did successfully migrate another site at 3.0.17.4 to IP Location Block prior to the above attempt. I have two sites at with the older 3.0.17, the rest are at 3.0.17.4.

Dev Console details after clicking “Migrate from IP Geo Block” (IP Geo Block is deactivated).

***
wp-content/plugins/ip-location-block/admin/js/admin.min.js.formatted

Uncaught Reference Error: IP_LOCATION_BLOCK_AUTH is not defined at admin.min.js:

!function(e, t, n, i) {
var a = !1
, o = []
, r = e(t).width()
, l = IP_LOCATION_BLOCK
, c = IP_LOCATION_BLOCK_AUTH;
function s(e, t) {
var n = {
“.”: “.ip-location-block-“,
“#”: “#ip-location-block-“,
“@”: “#ip_location_block_settings_”,
$: “ip-location-block-“,
“%”: “ip_location_block_”,
“!”: “ip_location_block_settings_”
};
return t !== i ? n[e] + t : n.$ + e
}

and at:

e(“ul.wp-submenu>li.wp-first-item”).removeClass(“current”).next().addClass(“current”)
}
})
}(jQuery, window, document);

***
wp-admin/options-general.php?page=ip-locaiton-block:

Uncaught TypeError: Cannot read property ‘1’ of null at window.onerror(options-general.php?

// If there was no matching functions, do not try to downgrade.
if ( typeof erroredFunction !== ‘object’ || typeof erroredFunction[1] === “undefined” || -1 === jQueryFunctions.indexOf( erroredFunction[1] ) ) {
return true;
}`

Thanks. Some of us have private (but no login) sites, e.g., family, where we want to cache the site’s pages. Members get access by knowing the page URL.

Some caching plugins, e.g., w3tc, use the sitemap as a guide in the caching process.

Even though we may tell search engines to not index a site, individuals or malicious entities may use the sitemap to find private pages.

The two things that AISEO has recently done that makes this more difficult are:
1) hide the ability to rename the sitemap to something not obvious.
2) publish the sitemap path/name in the robots.txt file.

The filters are appreciated, but it would be nicer and more helpful to have left in place easy ways to change the sitemap name and omit the sitemap from the robots.txt file. Another option would be to add a module to your Feature Manager that offers those two options. That way they would be out of sight for most users but available for advanced users.