Matt

We’re also getting the same error. Please let us know if there’s any update.

Hi, just to add to the others requesting this functionality. (Required 2FA for other user roles than just administrator.) Is there any update, reasoning behind it, or is there a proposed-feature page we can upvote? +1

PS – seeing as the message is only a ‘Deprecated’ message and not a fatal error, WP_DEBUG being set to false (or similar) might prevent it from showing.

I am also getting this error and have narrowed it down to the Sermon Manager plugin.

It says that you’re using the ‘contextual_help’ hook which has been deprecated, so I checked and you use it on line 554 of sermons.php. The error disappears when I comment out that action (lines 553-564), so it’s definitely that causing it. They suggest using get_current_screen()->remove_help_tab() instead.

Deprecated: contextual_help is deprecated since version 3.3.0! Use get_current_screen()->add_help_tab(), get_current_screen()->remove_help_tab() instead.

Amazing, thanks!

That works straight out of the box, so long as I remember to use the ‘Regenerate/Refresh’ tool in ‘Custom URIs’ mode after saving the product.

I know I’m being picky on an otherwise BRILLIANT plugin, but could it automatically regenerate/refresh the permalink (for that product only) on save? (Only if the category or primary category has changed)

Thanks for the prompt fix tough; very helpful indeed!

• This reply was modified 6 years, 1 month ago by Matt. Reason: Mark issue as resolved

Hi jordankcm, did you fix this in the end? The timers on our site sometimes don’t show, but it only happens on mobiles and when you resize the browser window on desktops. Was this the case with yours? (Don’t worry, I’ll start a new thread if it’s different)
Many thanks, Matt

Sorry yes of course, it’s the natters section of Independent Hostels UK.

Here’s an example of one that missed didn’t get ‘publicized’.

Can your users edit their name? Are you sure they’re not making the change?

It’s highly unlikely, as they are the ones that complain about it if their names get changed. Also, when it happens it’s a consistent change like it’s being parsed by some code, rather than the variety of changes you would expect if multiple unrelated users are changing their names.

So we don’t know what triggers it, but when it does take place, two things happen:

1. The first_name & last_name values change from uppercase to title case.
2. Any first_name values more than one word long (in other words ones that contain a space) get shortened to the first word and the remaining words get prepended to the last_name value.

The other possibility is that Buddypress or another plugin is making the changes.

If that’s the case I’ll see if I can find something in the buddypress forums, and meanwhile set the remote dev server going to check if it occurs without theme & plugins.

As for finding a trigger for the change, I thought the following actions could be close enough to trigger the bug, but none do:

• Update userdata (Core)
• Import userdata from Book (Custom)
• Export userdata to Book (Custom)
• Export userdata to Mailchimp (Mailchimp for WP)

Are there any other actions that might trigger such a change in userdata, particularly in core?
(I’ll check in the buddypress forums in case it’s buddypress related)

PS – many thanks for the blazing-fast responses btw!

Ahah good point. But the display itself doesn’t seem to be the issue, as the data is changed in the database table, before it reaches any display code.

@jacob I’m viewing this data directly in phpmyadmin, so I wouldn’t say it’s an issue with display.
But in answer to your question, we use <?php bp_displayed_user_fullname(); ?> on the user’s profile pages seeing as we want it all displayed, but for the book export we need to display the seactions differently, so take them separately from the respective table fields with a MYSQL query:

SELECT meta_value FROM wp_usermeta WHERE user_id = $id AND meta_key LIKE 'first_name'

SELECT meta_value FROM wp_usermeta WHERE user_id = $id AND meta_key LIKE 'last_name'

The important thing is that when we look up the first_name and last_name fields in phpmyadmin, the values in them change inexplicably, and that’s what we’re trying to stop, or at least find out what’s causing the change.

@esmi We’ve tried that with a dev site, but it’s a hard problem to replicate as it happens intermittently and without us doing anything. (Hence we thought it might be some wp_cron script.) I guess I should really try setting up a remote dev and leaving it running for a few weeks.

Is there a part of WordPress’ code that periodically sanitises user details, such as maybe forcing the firstname to be one word and pushing the rest into the lastname field? If there is, could someone could point me towards that?

It would make sense if such a script was running, because at the same time as the name reshuffle, the name also gets altered to Title Case.

e.g. “AVON TYRRELL” “ACTIVITY CENTRE” becomes “Avon” “Tyrrell Activity Centre”

[Firstname] [Lastname], so ‘Avon Tyrrell Activity Centre’, which is what usually displays on the site frontend.

The main place the firstname & lastname fields are used separately is when exporting to the book that they publish (The Independent Hostel Guide) and in user material such as forums and communications.

I had to disable all caching. Database & object wasn’t enough, all of them had to be disabled. Do we know if this error will be fixed with an update some point soon, so we can start making use of caching again?

Hi, is there any news on this issue?