510 Not Extended during Analytics module setup about site-kit-wp HOT 5 OPEN

Hi @Philipp91 thanks for opening this issue. We do not provide support via GitHub so could I ask you to please open a new support topic with us and we will be happy to look into this further with you.

Thanks!

from site-kit-wp.

I don't need support (I'll go figure out that ModSecurity issue myself). I filed a bug about how the plugin behaves wrt. error reporting towards the user (with users in mind who couldn't debug this with DevTools like I did myself). I'm basically asking for those pre-existing bugs to be reopened, as they weren't really fixed, as my experience above proves.

from site-kit-wp.

@Philipp91 Understood, I will reopen this for review by the team. Thanks for flagging.

from site-kit-wp.

Indeed I got it to work by temporarily disabling that ModSecurity rule. And in fact, a simple link for doing so was already included in the error message.

Btw the same kind of error also happens in the background now that I've got everything set up, when I open the Analytics settings in the sitekit plugin again, change a setting and click on "Apply changes". Except that here, no error message is shown, it simply doesn't go on to save and doesn't close the form. So here, that issue is even harder to debug.

I strongly suggest that, for your (presumably thousands of) users' sake, you parse apart that error message, output a more useful error to the user and include the link for ModSecurity deactivation (the https://{mydomain}/ /modsec/?domain=[{mydomain}](http://{mydomain}/)&ip={myip}&path=/home/ch309093/web/[{mydomain}/public_html](http://{mydomain}/public_html) part of the error I sent above) directly into the output. So tell your users something like: "Your webserver rejected the plugin's attempt to access/update its settings. This is likely due to ModSecurity blocking this access. You can try disabling ModSecurity entirely for a short amount of time, or visit the following link to disable specifically the one rule that blocked your access: https://{mydomain}/ /modsec/?domain=[{mydomain}](http://{mydomain}/)&ip={myip}&path=/home/ch309093/web/[{mydomain}/public_html](http://{mydomain}/public_html). Note that sometimes after updating ModSecurity you need to wait a couple of minutes before the change takes effect. Then retry this action."

from site-kit-wp.

Thanks for these details, @Philipp91! We'll dig into this further and consider a future enhancement for Site Kit. Feel free to continue to follow this issue for updates.

from site-kit-wp.