Use yaml document type without a fusion template

Hey,

I have a basic document type for contact persons in which I have the properties for name, telephone number, email address and a picture. The documents are NOT for frontend view and just for pasting data. The contact persons gets included in a special module.

I worked without a fusion template so the content gets displayed like in the „Raw Content”-view. Which is just fine for me.

Now I see that I have a lot of exceptions like this:

Exception #1332493995 in line 410 of /homepages/11/d82437635/htdocs/mywebsite/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/Neos_Fusion_Core_Runtime.php: The Fusion object "WG.BaseSite:Document.Ansprechpartner" cannot be rendered:
Most likely you mistyped the prototype name or did not define 
the Fusion prototype with "prototype(WG.BaseSite:Document.Ansprechpartner) < prototype(...)".

Can I stop the exceptions without building a fusion file with all properties?

Thank you,
Julian

Hi, are those errors from backend or frontend requests. You might need to prevent frontend access if they accidentally show up in the sitemap or other places.

I think the backend shouldn’t throw this error.

Hi Sebastian, I have removed the pages from the sitemap by setting a ‘noindex’.

Unfortunately, the pages are still being crawled and exceptions are still being logged.

Is there a way to forbid crawlers to visit the pages?

Here are two request infos from two different exceptions (the references are also a nodetype without a fusion file).

HTTP REQUEST:
target: /contact-persons-de/name-xyz
Host: www.mywebsite.com
Accept: * / *
User-Agent: meta-externalagent/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/crawler)
X-FullPageCache-Enabled:
HTTP REQUEST:
target: /references-api/node-19ifg21xm2sxm
Host: www.mywebsite.com
Accept-Encoding: gzip, deflate, br
Referer: https://www.mywebsite.com/
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36 Edg/135.0.0.0
Accept: * / *
X-FullPageCache-Enabled: 

I have a half built package for some customers that allows to mark pages as “backend-only” pages, f.e. for documentation or other specific page types. I’m not able to finish this package quickly up for release but the following snippet could already solve it for you:

root.backendPage {
    @position = 'before rawContent'
    condition = ${!documentNode.context.inBackend}
    renderer = Neos.Fusion:Http.Message {
        httpResponseHead {
            statusCode = 404
            headers {
                'Content-Type' = 'text/html; charset=utf-8'
            }
        }
        body = 'Page not found'
    }
}

It works very well. The pages are now marked as 404.

Now, I just have to wait for the crawlers to get it and stop crawling.

Thank you very much, Sebastian.

If you don’t hear from me, that’s a good sign :wink: