502 Error

We are having the same issue.

If I disable the plugin there is no more problem with the login, but otherwise I get a 502 bad gateway error instead of the login screen.

There are no hard errors, but I did find this clue:

Warning: Cannot modify header information – headers already sent by (output started
at /wp-content/plugins/contact-form-7/includes/functions.php:374)
in /wp-content/plugins/handl-utm-grabber/handl-utm-grabber.php on line 46

as a follow up, I just added the following to the top of handl-utm-grabber.php above this line:

add_filter('widget_text', 'do_shortcode');

to ensure the code isn’t executed on the login screen:

if ( $_SERVER['REQUEST_URI'] == "/wp-admin/" || strpos($_SERVER['REQUEST_URI'], "/wp-login.php?redirect_to")  !== false  ) {
	return true;
}

There is probably a better way to do this, but it will get us by until the plugin is fixed.

• This reply was modified 5 years, 5 months ago by e dev.
• This reply was modified 5 years, 5 months ago by e dev.
• This reply was modified 5 years, 5 months ago by e dev.

Thanks for the report, I’ll release a fix soon for this…

Thank you. Do you have an approximate time when this will be released? We are really struggeling with that unfortunately.

Thanks in advance.

Planning to release new version in a month…

I thought your fixed worked? Why are you struggling with the problem?

Hi, so for me the fix did not work. When I add the code from “efishinsea” the whole plugin does not work anymore. We are struggeling because we need the utm-parameters and we also need to be able to login to wordpress at the same time.

Regards

Hello I also have this 502 error, but only on logout, otherwise the plugin is working awesome! Any idea when the fix for the 502 error is coming? Thanks for your work adding this plugin!

Hi @severintravel and @devoncrowell,

If still having problem related to this, please create separate support ticket. Thanks!

HI. Did you ever come up with a permanent solution for this? I had to re-add my fix to the latest versions of your plugin because the 502 Gateway issue is still happening.

Thanks!