Search in List view on publishing page layout

Question

UPDATE after trying the OOTB list app:

I have a strange issue with placing a list view web part on a publishing page layout.

The searchbox is displaying, but when I search it does not load any results (the spinner never stops spinning).

The javascript console spits out:

inplview is undefined

so I tried referencing inplview.js. This makes the error message disappear, but still no luck with loading search results. Filtering and sorting works great though.

Note that this it true both for custom XSLT webpart and for the "App" for the list.

Answer 1

Thanks Robert! I am banging my head on the wall for this!

Basically you don't have to add a code just to show the ribbon by default. Just go navigation and tick NO to show or hide command ribbons.

According to the error that i got below, it is referencing to a script outside our domain.

Webpage error details Message: Script error Line: 0 Char: 0 Code: 0 URI: https://cdn.sharepointonline.com/6274/_layouts/15/sp.ui.listsearchbox.js?rev=SMNOuJrjiX3HzGpk4HWtJg%3D%3D

And showing the ribbon works well. And this only happens to publishing pages.

Answer 2

This is an issue with InplView not loading on demand when a publishing page is in published state. Still a bug in Feb 2017.

To force the script to load, add the following script to the page:

window.vendor_ensureInplView = function () {
    var typ;

    if (ajaxNavigate.get_hash().indexOf('InplviewHash') === -1) {
        try {
            typ = typeof inplview.RestoreAllClvpsNavigation;
        }
        catch (e) {
            typ = 'undefined';
        }

        EnsureScript('inplview', typ, function() { inplview.RestoreAllClvpsNavigation(); });
    }       
}

_spBodyOnLoadFunctionNames.push('vendor_ensureInplView');

Answer 3

Yes this is sharepoint OOTB error.. No solution for this

If you want all users to have search enabled you can break permission and give them contribute permision at list level. Enable the show ribbon ->Always true

Answer 4

have you deployed a design manager package to your publishing site?

that can corrupt some of the OOTB content type for publishing sites, and your behavior of it works until published can indicate one of the fields you need is gone. I had this happen with a roll up image in a custom page layout. Worked fine and was visible until I hit publish, then it stopped showing up

if you have, try you webpart and edit scenario on a Plain & fresh site collection.