kinglozzer

@will__ That’ll be because you’re logged in and in stage viewing mode

kinglozzer

e.g. https://github.com/bigfork/silverstripe-recipe/blob/master/app/src/Admin/SiteSettingsAdmin.php

Show 1 attachment(s)
GitHub  
bigfork/silverstripe-recipe

Bigfork’s quickstart recipe for simple SilverStripe 4 projects. Contains frequently used modules, templates, config settings, JavaScript and CSS. - bigfork/silverstripe-recipe

Hide attachment content
kinglozzer

We usually use a separate modeladmin for that kind of stuff, so we don’t have to give non-admins access to those “who can view/add X” settings

kinglozzer

I think you should be able to do that with those

kinglozzer

Have you looked into the permissions options in groups?

kinglozzer

If you’re serving data for other applications to consume, you might want to try the restfulapi module: https://github.com/colymba/silverstripe-restfulapi/tree/2.1

Show 1 attachment(s)
GitHub  
colymba/silverstripe-restfulapi

SilverStripe RESTful API with a default JSON serializer. - colymba/silverstripe-restfulapi

Hide attachment content
kinglozzer

(we didn’t have silvershop, just silverstripe-omnipay, but I imagine it’s the same problem just a different cause)

kinglozzer

Basically what’s described here: https://github.com/silverstripe/silverstripe-omnipay/issues/212

Show 1 attachment(s)
GitHub  
Composer seems to install wrong version of omnipay/common · Issue #212 · silverstripe/silverstripe-omnipay

Installing silverstripe-omnipay per docs as follows: composer require silverstripe/silverstripe-omnipay ^[email protected] This installs the following: Package operations: 6 installs, 0 updates, 0 removals Ins...

Hide attachment content