tomo55555

Hi Konrad,

Apologies for the delay getting back to you, and thanks for your continued support. As part of testing my user form I created a new user in the wordpress user admin. I then tried to load the user in the form to change their first name etc. It failed. I loaded the form in an incognito browser page so that no existing users were logged in,

In the form I then inputed the correct username and password as set in the admin section, updated the other acf fields and submitted the form. The user details in the user admin were not updated, nor were the fields loaded when I input the correct username and password – I’m not usre this is supposed to happen when the submit button is not pressed.

Here is my json:

[
    {
        "name": "update-user-test-form",
        "title": "Update User Test Form",
        "active": true,
        "field_groups": [
            "group_66e4ba409b412"
        ],
        "settings": {
            "location": false,
            "honeypot": true,
            "kses": true,
            "uploader": "default"
        },
        "attributes": {
            "form": {
                "element": "form",
                "class": "",
                "id": ""
            },
            "fields": {
                "element": "div",
                "wrapper_class": "",
                "class": "",
                "label": "top",
                "instruction": "label"
            },
            "submit": {
                "value": "Submit",
                "button": "<input type=\"submit\" class=\"acf-button button button-primary button-large\" value=\"%s\" \/>",
                "spinner": "<span class=\"acf-spinner\"><\/span>"
            }
        },
        "validation": {
            "hide_error": false,
            "hide_revalidation": false,
            "hide_unload": false,
            "errors_position": "above",
            "errors_class": "",
            "messages": {
                "failure": "Validation failed",
                "success": "Validation successful",
                "error": "1 field requires attention",
                "errors": "%d fields require attention"
            }
        },
        "success": {
            "hide_form": false,
            "scroll": false,
            "message": "Form updated",
            "wrapper": "<div id=\"message\" class=\"updated\">%s<\/div>"
        },
        "actions": [
            {
                "action": "user",
                "name": "",
                "type": "update_user",
                "validation": false,
                "save": {
                    "target": "{user}",
                    "user_email": "{field:field_66e4d67466818}",
                    "user_login": "{field:field_66e4ba4166815}",
                    "user_pass": "{field:field_66e4d60766817}",
                    "first_name": "{field:field_66e4d6f766819}",
                    "last_name": "{field:field_66e4d72f6681a}",
                    "nickname": "",
                    "display_name": "{field:field_66e4e1e796f20}",
                    "user_url": "",
                    "description": "",
                    "role": "subscriber",
                    "log_user": false,
                    "acf_fields": [
                        "field_66e4d60766817",
                        "field_66e4d67466818",
                        "field_66e4e52b0c889",
                        "field_66e4d6f766819",
                        "field_66e4d72f6681a",
                        "field_66e4e1e796f20"
                    ]
                },
                "load": {
                    "source": "{user}",
                    "user_email": "",
                    "user_login": "field_66e4ba4166815",
                    "user_pass": "",
                    "first_name": "field_66e4d6f766819",
                    "last_name": "field_66e4d72f6681a",
                    "nickname": "",
                    "display_name": "field_66e4e1e796f20",
                    "user_url": "",
                    "description": "",
                    "role": "",
                    "acf_fields": [
                        "field_66e4d60766817",
                        "field_66e4d67466818"
                    ]
                }
            }
        ],
        "render": ""
    }
]

I’m sorry, but I’m obviously missing something here, and I’m sorry to be a pain!

I also noted that using the update user action also allows us to create a new user. Is there a code snippet or setting we can use just to enable updating an existing user and not creating a new one?

Many thanks again.

Thanks Konrad, I understand the reasons now. Review updated accordingly.

Thank you very much for the great support. I was confused why we would need to manually select each field as I couldn’t think of a situation where you wouldn’t want this information saved.

Thanks again.

I just wanted to let you know that your code created an error which I’m told is due to the function?wp_add_inline_style. According to the query monitor this function is being called too early, before the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks are fired which is not the correct procedure.

My eventual solution was this code but maybe not ideal:

function my_custom_admin_styles() {  
    echo '<style>  
    button.components-button[aria-label="GenerateBlocks"] {  
        display: none;  
    }  
    </style>';  
}  
add_action('admin_head', 'my_custom_admin_styles');  

I apologise if I upset you. That was not my intention. I did email you our issues and didn’t hear back.

I’m sure it’s not a user issue (in this case) as we have been using your plugin for a year or so now, and some plugin menus do show up, but others don’t. Also, when we disable a particular menu item like discussion for a user role it doesn’t change on the backend.

Happy to remove my review if you are unduly upset.

Thank you for your help.

Sorry, what I mean is child categories.

OK, tried cat and that does not fix the issue. I’ll research more into why the theme developer used SearchWP Live Ajax Search and see if I can roll it out and find another ajax load more solution. Again, thanks for your help.

ok, I uninstalled your ajax live search because it didn’t really work with this search form. But that’s not important.

However, I did use your shortcode [searchform cats=”686″] and tested it with the word “handle” on our development site: https://dev.buildreview.org/test-search-form/

If you type in the word HANDLE you should get 12 posts. But when I use the LOAD MORE ajax button the results get pulled from the entire site again. Any thoughts why this might be happening please?

That’s great, that works really well. Thank you!

So last question from New Zealand for today is, can we use ajax load more with this form search results? I get the standard wordpress page number pagination.

I did load your Relevanssi Live Ajax Search plugin to see if they work together but no change, so perhaps there’s a config setting???

Thanks again for your time, it’s really appreciated.

Hi Mikko,

Thanks for your help. May I ask, is there a search string that I can use to use the shortcode and then restrict the answers to a particular parent category and its siblings?

Thanks,

Hi Mikko,

Thanks for checking. If you follow this search url you’ll see a restricted search to only a particular category id: https://buildreview.org/?s=handle&search_cat=686

I basically wrote a separate code snippet that used your relevanssi_modify_wp_query to reduce the search results to a particular category and that’s when the ajax issue started. I can send you the code but I suspect that it’s a bigger issue than your support allows for on the free version. Saying that though, is there an easy way to create a search form that I can just use as a sidebar widget and using the standard search results template?

Sorry for the confusion, I thought the ajax issue was for the full site search as well.

Many thanks.

Yes, if I unistall the plugin the results return to normal, albeit without the ACF results. I have switched the pagination back to ajax load more for you to test.

By the way I have been researching the theme code and it looks like the original ajax search is provided by SearchWP Live Ajax Search. I can’t be 100% sure, but this may be conflicting with your plugin.

Thanks,

Ian