acidstout

Hi @vkprog . Yes, you need to contact them to have those enabled. These cannot be enabled in the plugin itself, because the settings in the plugin are just flags which are sent to the SumUp servers, and then the SumUp servers check if you are allowed to use them. So, just contact SumUp to get your account verified and they’ll be glad to enable restricted scopes for you.

Well, yes and no. In the default configuration of PHP (that’s the language WordPress’ code is written in) it is not allowed to send multiple headers after the first header response has been sent. So, if a plugin, theme or whatever sends a header and then another plugin or theme or whatever also tries to send headers this warning occurs. In PHP a warning does not abort the execution of a script. That being said, the warning should have no effect on the plugin’s functionality. But there might be a custom error-handler which overrides this behavior. As I said before, it is safe to temporarily comment those lines out, but I think the issue should be tracked down and fixed properly in order to maintain a stable and reliable WordPress instance. Also, you should review your server’s PHP configuration. Maybe there is something messed up or configured in a non-optimal way.

The quoted header() instructions basically send information to the browser on how to process. For example the “X-Frame-Options” parameter set to “SAMEORIGIN” tells the browser that the website sending this header is not allowed to be run embedded in an iframe of another website.

So, basically it is safe to temporary comment these lines out by putting double-slashes “//” at their beginning. However, that does not solve the issue on the long run, and all three files are core files of WordPress and should not be modified. At least following the next update they will get overwritten anyway.

I really suggest you to contact your web hoster and tell him to modify the php.ini file for you as stated in my previous post. Again, this is just a suggestion. I cannot know if this really fixes the issue, since I basically don’t know anything about the setup of the web server etc.

Regarding the missing card option I have absolutely no clue what’s wrong. Maybe it is some payment setting in WooCommerce itself or in the SumUp plugin. I can’t remember how I configured it (it was long before I wrote this setup guide).

Hi! The warning message “Cannot modify header information …” is very likely caused by another plugin and/or your web server’s configuration. As a first approach I would try to disable all other plugins, and then try to set up the SumUp plugin. Once set up, re-enable all previously disabled plugins. If that doesn’t work, you may try to switch to the default WordPress theme in case you use a custom theme. If nothing helps, you need to modify your web server’s configuration (likely its php.ini file). Your web hoster should allow you to do this in one or another way. The setting in the php.ini you want to change is called “output_buffering”. Its default value is 4096, and you want to set it to “On”. That should prevent the warning message in nearly all cases, and allow you to save the settings in the SumUp plugin.

Thanks for your offer, but I don’t need any money. If you really want to pay tribute, you are free to donate some BTC to this address: 0x160443c73f5fb9cdeace14ec5cb431fd51f68ed5 on BNB Smart Chain (BEP20). All donations will be used to support Ukrainian refugees.

Thanks for your reply. I already came up with a working solution in the meantime.

$uri = wp_get_referer();
if (empty($uri)) {
	$uri = isset( $_SERVER['REQUEST_URI'] ) ? esc_url_raw( wp_unslash( $_SERVER['REQUEST_URI'] ) ) : '';
	$uri = preg_replace( '|^.*/wp-admin/|i', '', $uri );

	if ( ! $uri ) {
		$uri = '';
	}

	$uri = remove_query_arg( array( '_wpnonce', '_action', '_cache' ), admin_url( $uri ) );
}
		
wp_safe_redirect( $uri );

What do you think? Would that work for you?

@thegulshankumar There are no ads or popups in this plugin. Also there’s no code which fetches external sources in any way to show ads or popups. I know because I analyzed several versions of this plugin and I use the plugin on my own website as well as on many of my customers websites. Never had any issues with it.

I think @mohsinist just made a mistake and wrote a review for the wrong plugin, or maybe he installed some other plugins and/or themes which show ads. It’s impossible to analyzed without access to the system in question. Therefore nobody should be judged or blamed.

The installation procedure is still the same, but in order to have an up-to-date geo-database MaxMind requires you to create a free account and generate a free license key. So, it’s MaxMind to blame for and not Pascal.

Also if you need automatic updates of the geo-database (Pascal removed this feature several versions ago due to legal complains) you might want to check-out the Lite version of the plugin at https://github.com/acidstout/iq-block-country-lite

It is actively maintained and based on Pascal’s version. The only differences are, that I removed the optional tracking feature and the Webence API, did some cleanup and added an option to enter your MaxMind license key in order to enable automatic updates of the geo-database.

Thanks for clarification.

First of all, this is not how this plug-in is meant to work. Let’s say your site is hosted in France and you wish to block access to your site from Italy. This is entirely possible. But, if a user from Italy googles for your site, it will still show up in Google’s search results, because Google servers are located all over the world. You could still try to find out the ip-addresses of the Italian Google servers and block them in that case, but it still would just block access from Italian Google servers; not from Google servers somewhere else. Also if a user does not use Google, but lets say Bing oder DuckDuckGo or whatever, your site will show up in the search results. Also you could just tell all search engines to not index your site at all, or you could completely block any search engines from accessing your site, but that’s likely not what you want.