I managed to have a more detailed look at this for you. It would appear that the cause of the issue is the original view itself where its not respecting the target_id attribute to only display the search bar.
I went ahead and made an exact copy of the view and in this new view the issue isn't there. I was able to successfully separate the view search from the view results. See the test post below. hidden link
From the outset i'm not able to see any idea as to what was the cause of this issue but it would appear to be working as intended now.
Please let me know if this helps.
Thanks,
Shane
Thanks for your support. Would you mind tell me what did you do or what should I do to make them separate? As I have to do it for some other pages also.
What I actually did was to re-make the view, then just use the shortcodes that I provided in our chat to get the search section and the results section.
In summary I went to Toolset->Views -> Add New and then recreated your view. Then I went to the page/elementor template and added the search section of the view using the shortcode below.
[wpv-view name='my_view' target_id="self"]
Then on a different location on the same page I added the results section using the shortcode below.
[wpv-view name="test_view" view_display="layout"]
Please let me know if after doing this on your end if you were able to get the desired results or if you're still experiencing challenges.
As explained in my previous post if you want to display the view as 2 separate components i.e search and results. Then for the search area you will use.
[wpv-view name='my_view' target_id="self"]
Then for the results only you will use.
[wpv-view name="my_view" view_display="layout"]
Please not the use of the attribute in the shortcode view_display="layout" . Also to verify what was actually added to the page I tried to log in again with the credentials that were previously provided but they seem not not work anymore.
Can you provide me with a new set so that I can check again to see what has been done ?
I noticed attraction fields are listed under the "Flight to" custom post type, also.
It seems the attraction is duplicating under all custom post types.