When you're inserting the View, you should find the option 'Don't include the current page in the query result', in the 'Content Selection' box for the View block, like this: hidden link
Could you please check if it is disabled? If so, just try to enable it, save the page and check if it solves the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Just to make sure, do we have your authorization to make a copy of the website and migrate it into another server? In order to perform more complex tests without compromising the live production.
I added the following condition "[wpv-conditional if="( '[wpv-loop-index]' gt '0' )"]" to the Loop item in View for both products and projects. This basically removed the first entry.
This is a temp workaround as we need to get customer site functional, but the issue still needs to be resolved as I suspect in the future this will have an effect of always removing the first entry which may be a correct entry.
In this case, would you be able to provide a staging version where we can make complex tests without compromising the live production? Or, if you prefer to do the test directly there, please try it:
- Deactivate all the plugins that are not related to WPML
- Switch for a moment to a WordPress default theme like Twenty Twenty-one
- If the issue is gone, activate one by one to see with which one there is an interaction issue
Could you please tell me the results of this investigation?
I'm enabling the private fields, if it is possible to provide a staging version, so that we can check it better.
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
Upon further inspection, we have found a very simple solution.
By editing the View in question we see that in the Loop Editor you have included the shortcode for the template used for each loop iteration before the loop as well as within it: hidden link
Deleting that shortcode fixes the problem. Could you please review it and let us know if the issue is solved now? Thank you.
