SwissMountainLeader

I’ve done that, I’ll wait for a reply

I have this : https://imgur.com/a/2PCtRAy

Thanks, that was exactly what I had read on the website, and it’s not in advanced setting on my installation.

me too ??

I can add a little more local detail. It only occurs on pages withe Automatic Event block plugin actually used. Other pages are fine. In the console the APi paths look odd but I’d need to look properly to qualify that, certainly there’s a bunch of 404 errors caused.

it’s not uncommon for a site to be so broken that the wpadmin doesn’t work. In that case you’ll need command line or FTP access. Do you have those?

I’m not using MU but I have fixed our issue, I’ve removed and reinstalled JetPack along with a few general bits of housekeeping where the installation had got messy over time.

@pelletta that’s the same error I get with Nginx and PHP 7

You don’t need to disable Jetpack, just remove the following files/directories:

wp-content/plugins/jetpack/modules/simple-payments/
wp-content/plugins/jetpack/modules/widgets/simple-payments/
wp-content/plugins/jetpack/modules/widgets/simple-payments.php

That’s the error I’ve had on both versions today. I just removed the module and widget to fix that error both times.

I’m getting the same errors with 6.3.2 using PHP 7.2.7

removing the simple payments module & widget is the simplest and quickest fix.

2018/07/04 15:32:01 [error] 923#923: *3201 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: Class ‘Jetpack_Simple_Payments’ not found in /xxxxxxxxxxxxxxxx/wp-content/plugins/jetpack/modules/widgets/simple-payments.php:479

I see ?? it’s supercached vs wp-cached. But, my settings are the same on several sites and it’s apparently doing different things. Something odd about my config I assume!

thanks for the update!

it would be perfect to not update passwords, we’d be able to automate this and run via cron as well which would be great.

Thanks!

That doesn’t entirely answer my question and I had read the documentation.

To recap, I’ve a CSV file with usernames, email addresses and some profile information. When I import that the first time, all accounts are created and passwords are created.

If I import that file a second time, then it seems from testing and the documentation that the passwords are reset. I want to import that a second time and more because some data may change, some records may be added and so on. But, while I do want to update the user, I don’t want to reset the password.

If I add a password column to the CSV with a value then when I do the second import it would reset the user password to the initial value even if they’ve changed it. That’s not really what I want.

If I set the password column in the CSV to blank, then what? the initial import or the later one with new records creates accounts without passwords? That’s what the documentation seems to say. That’s also not really what I would want.

The options on the first tab are confusing as there’s no clear precedence, ie

Update existing users?
Update roles for existing users?

If we say “no” to updating existing users, does that mean roles for existing users are not updated or does that boolean take precedence over the first?

And, if those two options acknowledge the design point that users can be updated in part, ie profile information updated but not the role if we answer YES then NO to those questions, then a third option “Update passwords for existing users?” would logically fit as well.

The CSV I have contains membership information for an association, members have different levels which can change so I do want to repeatedly import the same users. Most of the time, I want to update users rather then add them.

I hope I’ve explained that properly!

I don’t use W3TC personally but I do cache using fastcgi_cache and the same issue comes up with identifying user agents.

I found the wptouch blog post talking about this with nginx :

https://www.wptouch.com/wptouch/optimizing-nginx-cache-wptouch-pro-3/

I thought the list of user agents there could be tweaked a bit, here’s my list :

https://www.alpine.link/wordpress-page-caching-mobile-users/

I did see that, but as adding markers like utm_source would be the same for every post then it would suggest it’s an option best selected at a global level.