I see when I use elementor toolset view element I get the following:
<p>Search Ethnobotanical Uses</p>
<form autocomplete="off" action="<em><u>hidden link</u></em>" method="get" data-viewnumber="8426" data-targetid="8424" data-viewid="8426" data-viewhash="eyJpZCI6Ijg0MjYiLCJ0YXJnZXRfaWQiOiI4NDI0In0=" data-viewwidgetid="0" data-orderby="" data-order="" data-orderbyas="" data-orderbysecond="" data-ordersecond="" data-parametric="{"query":"normal","id":"8426","view_id":"8426","widget_id":0,"view_hash":"8426","action":"<em><u>hidden link</u></em>","sort":{"orderby":"","order":"","orderby_as":"","orderby_second":"","order_second":""},"orderby":"","order":"","orderby_as":"","orderby_second":"","order_second":"","ajax_form":"","ajax_results":"","effect":"fade","prebefore":"","before":"","after":"","attributes":{"id":"8426"},"environment":{"current_post_id":0,"parent_post_id":0,"parent_term_id":0,"parent_user_id":0,"archive":{"type":"","name":"","data":[]}},"loop":{"type":"","name":"","data":[],"id":0}}" data-attributes="{"id":"8426"}" data-environment="{"current_post_id":0,"parent_post_id":0,"parent_term_id":0,"parent_user_id":0,"archive":{"type":"","name":"","data":[]}}"><input type="hidden" data-action="<em><u>hidden link</u></em>" data-page="1" data-ajax="disable" data-effect="fade" data-ajaxprebefore="" data-ajaxbefore="" data-ajaxafter="" /><input id="wpv_param_page_id" type="hidden" name="page_id" value="8424" />
<input type="text" name="wpv_post_search" />
<button type="submit">Submit</button>
</form>
If Ijust use elementor html widget with:
[wpv-view name="ethnobotanical-search"]
I achive the same. I prefer the simple approach - so what's the advantage using elementor toolset view?
Nigel
Supporter
Languages:
English (English )
Spanish (Español )
Timezone:
Europe/London (GMT+00:00)
Hi David
The View widget was introduced for ease-of-use, the results should be the same.
We have no control over the Elementor UI in a way that we can add the Fields and Views buttons to modules of other page builders like Beaver Builder, for example, and without the Fields and Views button you would have to manually enter the wpv-view shortcode or copy and paste it from somewhere else.
So the View widget is intended to be functionally the same as inserting the View shortcode (much like the Form widget).
My issue is resolved now. Thank you!