justdave

Just pulled version 3.0.3 and can confirm that fixed the above error, but it replaced it with a new one:

PHP Warning:  Attempt to read property "ID" on null in wp-content/plugins/elex-woo-flexible-pricing/includes/elex-wfp-product-flexible-price.php on line 655

Thanks. I did check through those troubleshooting steps before posting here, since it was mentioned on the troubleshooting FAQ. ??

I have filed a support ticket.

I managed to work around this by changing three occurrences of “AF_TD” to the string “‘daily-attendance'” to match the other uses of esc_html__() in the plugin.

Thanks! The in-product documentation showing the list of available tags in the middle of the Design page doesn’t mention it. It is indeed there in the docs on your website though.

Got it working so I’m all set.

• This reply was modified 1 year, 2 months ago by justdave.

Your screenshots are showing items that have actual prices and not “name your price”

Just to help people find it better, it says in other threads that the developers are aware of it and working on a fix, and the workaround is to roll back to version 3.4.4 until they have the fix ready.

If you have shell access and have the wp command line tools installed, you can do this by cding into the root of your wordpress then running:

wp plugin install --force --version=3.4.4 google-apps-login

You didn’t have to roll back because it was fixed in 2.1.10 and you have a newer version than that.

You probably have a Role field on your profile forms.
See https://www.ads-software.com/support/topic/after-2-1-update-roles-dropdown-returns-error-500-on-profile-form/

The only thing off your list there that I can probably help you debug is getting rid of that role. What happens when you try to get rid of it? Does it cause an error? Does it just go through the motions like it’s getting rid of it but then it’s still there?

Except they’re not really different? (I’m not a developer for this plugin, just a user, but I’ve written my own plugins, and this is just my own opinions) WordPress has a lot of built-in support for things like roles, users, and handling logins to the site already, so why re-invent the wheel? The internals are there already, it just needs good UI to help you build on top of it, and some extension of features, which is what UM provides. The only difference you need to have between an admin and a front-end user is the roles and capabilities they have.

As a developer I would think it would make logging into the site complicated if you had to handle it differently depending if you were a “normal” user or a front-end user. There’s so many security considerations in handling the login process, that NOT using WordPress’s built-in login mechanisms means you have a ton of stuff to re-implement to make it secure. WordPress itself is far more likely to get security bugs found and fixed than some random plugin, too. That’s the last thing a plugin author would want to do is accidentally create a way for someone to hack your site in their custom login screen. I’m guessing this is why UM just makes pretty login forms and wraps them around WordPress’s built-in internals for handling it on the back end (with hooks to do extra stuff, too).

Sorry for rambling so much. ??

@nsinelnikov That form points me back here when I’m not a paid user.

I did file https://github.com/ultimatemember/ultimatemember/issues/670 yesterday, if that helps.

debug.log was the first place I looked trying to figure out what was going on before tracking it down. There was nothing in it. I could tail the log, submit a form, get the error on the web page, and nothing new would show up in the log.

First choice: restore a backup (you make them, right?) Preferably restore just wp-content/plugins/ultimate-member and not your entire WordPress install.

Second choice: You can download it from here: https://github.com/ultimatemember/ultimatemember/releases/tag/2.1.8 link is: “Source code (.zip)”

Note that it unpacks to a different directory name, so if you use the “upload a zip file” option from Add New Plugin, it will install a second copy instead of overwriting the existing one. Activating both at once will confuse the heck out of WordPress and may break things. After uploading it do NOT activate it. Instead, log into the shell or use an FTP client to delete the one named “ultimate-member” from wp-content/plugins/, then rename “ultimatemember-2.1.8” to “ultimate-member”. It should automatically activate because the one originally under that name was never deactivated. Note that your site will probably be broken after you delete the original until you rename the new one to replace it.

Does your registration form have a Role field on it? If so, see https://www.ads-software.com/support/topic/after-2-1-update-roles-dropdown-returns-error-500-on-profile-form/

Yeah, just confirmed, rolling back to 2.1.8 fixes this.