scirceo

Hello @andrewshu

I have added the code you provided to our production site, updated to UM version 2.8.8, and it works fine, no anomalies noted. If I see something that does not look as expected, I’ll post it here.

Thank you for your assistance.

• This reply was modified 1 month, 3 weeks ago by scirceo.

Hello @andrewshu

I added that code to my functions.php file and it worked to fix the problem on the Member List page on my staging site with the latest version of UM, which is now version 2.8.8. (Please note that I tried this version earlier today without the code you posted above, and the Member List page was not fixed.)

I have not yet checked whether other problems have arisen because of it, but I can confirm that the Member List issue I originally posted about appears to be fixed with the added code. Thank you.

I just rolled back to version 2.8.6 and it works as expected.

I’ll keep it at 2.8.6 until y’all release a fix.

• This reply was modified 1 month, 3 weeks ago by scirceo.

I copied my current site to the staging site. I deactivated all plugins except UM. I switched to the Twenty Twenty-Three theme.

Here is what I see:

0 ) { #>

user.account_status_name

<a href="user.profile_url" title="user.display_name”> user.avatar

<a href="user.profile_url" title="user.display_name”> user.display_name_html

user.hook_just_after_name user.hook_after_user_name

0 ) { #>



We are sorry. We cannot find any users who match your search criteria.

data.pagination.header_single 1 ) { #> data.pagination.header0 ) { #>

<span class="pagi pagi-arrow disabled” data-page=”first” aria-label=”First page”> <span class="pagi pagi-arrow disabled” data-page=”prev” aria-label=”Previous page”> <span class="pagi current” data-page=”page”>page <span class="pagi pagi-arrow disabled” data-page=”next” aria-label=”Next page”> <span class="pagi pagi-arrow disabled” data-page=”last” aria-label=”Last page”>
0 ) { #>

user.account_status_name

<a href="user.profile_url" title="user.display_name”> user.avatar

<a href="user.profile_url" title="user.display_name”> user.display_name_html

user.hook_just_after_name user.hook_after_user_name

0 ) { #>



We are sorry. We cannot find any users who match your search criteria.

data.pagination.header_single 1 ) { #> data.pagination.header0 ) { #>

<span class="pagi pagi-arrow disabled” data-page=”first” aria-label=”First page”> <span class="pagi pagi-arrow disabled” data-page=”prev” aria-label=”Previous page”> <span class="pagi current” data-page=”page”>page <span class="pagi pagi-arrow disabled” data-page=”next” aria-label=”Next page”> <span class="pagi pagi-arrow disabled” data-page=”last” aria-label=”Last page”>

NOTE: As before, when I removed the shortcode to restrict viewing to logged in members only –[um_loggedin show_locked=”yes”] — it functions perfectly.

NOTE: I also tried um_loggedin without the show_locked parameter, and still got the bad result.

And this is the Console set of messages:

Uncaught Error: Template not found: #tmpl-um-member-list-302c0
    at wp-util.min.js?ver=6.6.2:2:371
    at um_build_template (um-members.min.js?ver=2.8.7:1:5841)
    at Object.success (um-members.min.js?ver=2.8.7:1:4917)
    at c (jquery.min.js?ver=3.7.1:2:25304)
    at Object.fireWith [as resolveWith] (jquery.min.js?ver=3.7.1:2:26053)
    at Object.<anonymous> (wp-util.min.js?ver=6.6.2:2:1230)
    at c (jquery.min.js?ver=3.7.1:2:25304)
    at Object.fireWith [as resolveWith] (jquery.min.js?ver=3.7.1:2:26053)
    at l (jquery.min.js?ver=3.7.1:2:77782)
    at XMLHttpRequest.<anonymous> (jquery.min.js?ver=3.7.1:2:80265)Understand this error

• This reply was modified 1 month, 3 weeks ago by scirceo.

Thank you for your response.

This is what I see in Console:

Uncaught Error: Template not found: #tmpl-um-member-list-302c0
at wp-util.min.js?ver=6.6.2:2:371
at um_build_template (um-members.min.js?ver=2.8.7:1:5841)
at Object.success (um-members.min.js?ver=2.8.7:1:4917)
at c (jquery.min.js?ver=3.7.1:2:25304)
at Object.fireWith as resolveWith
at Object. (wp-util.min.js?ver=6.6.2:2:1230)
at c (jquery.min.js?ver=3.7.1:2:25304)
at Object.fireWith as resolveWith
at l (jquery.min.js?ver=3.7.1:2:77782)
at XMLHttpRequest. (jquery.min.js?ver=3.7.1:2:80265)

Thanks, George, I’ll check it out.

Btw, when I clicked the link at the top of the settings in my WP Dashboard — the advertisement banner — it takes me to https://1.envato.market/ai-images-for-wp

The link in the text portion of the settings goes to the right place.

@susantau Cool, I did not even know that existed. I don’t know whether it’ll work for this particular use case, but I know it’ll work for others, and I’ma try it out right now. Thanks!

I’d like this capability, too, like adding an optional shortcode parameter that contains the expand/contract text. A reasonably priced PRO version would be cool, because this plugin is an excellent one, and I’d like to count on it for the foreseeable future.

I came here looking for an answer to this issue, too. We are hosted at GoDaddy Managed WP. We had the plugin working in the test site area, and did not detect this issue, but once we pushed the site to prod, the plugin turns off on its own. For example, I turned it on 4 hours ago, checked now and it’s off. Version 1.3.6 with WP 5.7.2.

EDIT TO ADD: I just verified that when I made an Update to the parent page, Protect the Children toggled off on the parent page, and the children were not protected. When I toggled it back on and updated the parent, the children were again protected.

EDIT TO ADD: I played around with the parent page for a little time. Made an edit. Updated. Watched protect all children toggle itself off. I toggled it back on and updated. It stayed on. I made another change and updated. It toggled off. That is to say, it seems to toggle off after every other update.

• This reply was modified 3 years, 5 months ago by scirceo.
• This reply was modified 3 years, 5 months ago by scirceo. Reason: Add more information
• This reply was modified 3 years, 5 months ago by scirceo. Reason: Add more information

Thanks for the tip, davemgraham. I was having the same issue, i.e. whenever I would update a published page I’d get that same error. When I deactivated Google Sitemap by BestWebSoft, the problem went away. Please note, bestwebsoft, that I did not have the problem with posts, only with pages. Unfortunately, the site is all pages. (I updated a test post as an experiment.)

• This reply was modified 7 years, 11 months ago by scirceo.

We have a Godaddy user who is also experiencing this. I suspect that Godaddy’s proprietary “Limit Login Attempts” plugin is conflicting with Wordfence Security, so we’ll need to figure out what to do about it.

Did you figure this out, Circe Link? I want to do the same.

Glad this explanation and fix are here. That was a shocker to see this problem.

Okay, good to know about the red display. I did not know what was going on there.

will do. thanks!