Content.exists throws error if content doesn't exists

Bugs
1

Enonic version: Enonic XP 7.16.1

OS: Debian KDE

It took me some time to see that I was getting an Error with no clear explanation (ERROR io.99x.i99x - (/lib/enonic/react4xp/index.js) Error in processor for page “io.99x.i99x:default” at: /).
After adding a lot of logs, I saw that the error was in a content.get, so I through I could fix it with content.exists.
Turns out that content.exists has a very stange behavior: it throws an error if the content doesn’t exist.
I had to wrap everything in a trycatch to fix this, but looks like this isn’t intentional and doesn’t really make sense for a method that should simply check if a content exists and return a boolean value to throw an error if it doesn’t.

Thanks.

2

Hello,

Sorry for the delayed response.

We have tested this on 7.16 and didn’t find any issues with how it works. `lib-content.exists` correctly returns either “true” or “false” depending on whether the content with provided `key` exists or not.

Can you share your code?