@adamdunnage The editor role has access to Analytics and Search Console. This is in the first screenshot I shared in my post above, unless I’m misunderstanding comething.
I tried disabling W3 Total Cache, but Site Kit did not appear in the admin bar for editors.
Just to be clear, it isn’t an issue that the URL is being rewritten by the server and thus can’t be accessed, the issue is the URL is incorrect in the minified CSS directly (you can see this if you go to the site in question and search for ‘woff’ in the minified CSS).
Thanks @vmarko, I have verified the .htaccess rules are correct. But I don’t think this issue would be related to .htaccess as it isn’t a problem accessing the files, the problem is that the URL for the files in the minified CSS is clearly incorrect (starts with content instead of /wp-content).
Thanks, here’s a screenshot. I’ve reduced it to a single stylesheet for testing purposes. I’ve tried with both the absolute URL and with the relative URL. But to be clear, the stylesheet itself is being found and minified, it is the urls within the stylesheet that are incorrect after being minified (they are missing /wp- from the start of them).
I have to agree with @leo1976 here. It’s great that a solution is being worked on, but this update took my sites down entirely. I agree that it would be best to roll back with an update so that no one else experiences this issue, even if a fix is near. It’s obviously affecting a significant number of sites based on the number of comments here.
Anything to try for this issue? I’ve tried enabling only Caldera Forms in Troubleshooting mode, so it’s the only plugin active — and I still can’t save the form. This happens on both sites in a multisite setup. I’ve tried removing the plugin entirely, plus its database tables and then reinstalling.
Seems this definitely breaks other things. Looks like removing those lines causes the form submission to fail if no option is selected, i.e. if [“”] is sent. And with an array, you can’t compare to parameter values.
Looks like the array is being converted to a list here. Removing lines 52-54 fixes the issue, but I’m not sure if it might break something else. Not sure why this was there in the first place.
@vmarko I found the source of the problem. I thought I had everything disabled, but it turns out there were selections in the user experience area. It was disable jquery-migrate, which was checked and was causing issues. Sorry to bother you with this!
