SSI purpose is user control basically, in a “site wide” top menu bar.
- having a users name appear in the menu’s
- having menu items hide or show dependent upon user role, (eg so a standard user can’t access the admin panel).
The reason for the errors is that these all require the security provider information (user id’s).
So when accessing the website on a live browser, it all works perfectly because the user is logged in.
When editing a page from the file browser, the user is not logged in so the serverconnect queries in the SSI don’t get the values they are expecting, and therefore keep throwing errors.