Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
i think its due to how sitetree automagicaly did it
E.G. Add a property that explicitly does not publish the connected asset with the object instead. Default behavior should be to publish them. Or at least make this globally configurable.
So I feel like the whole $owns thing is around the wrong way personally. Not wanting them published with their object is probably the exception to the rule.
> if you add "owns" it does get published on save (or has it changed)
Yeah it does. I'm saying that this will be the desired intention more than the alternative (in my mind). If they are ready to publish an object, they are more likely to want the contents of the object published.
but as a usecase maybe a client wants to muck around with a site before allowing customers to view things
if you add "owns" it does get published on save (or has it changed)
@Shannon Holmes has joined the channel
https://silverstripe-users.slack.com/archives/C0QSDASKT/p1571228642227000 I think it should be the default in relationships with publishable objects. I struggle to think of a case where you really want to publish a DO and keep the files attached to it in draft. Not that I've tried for very long.
With a build task, what's the correct way to print status info as text to the terminal when running in cli while also printing to screen when running in browser?
Debug::message and setting up the logger to run
$this->logger->info though they're not printing anything to the terminal.
var_dump shouldn't be reasonable options, though they seem to be the most reliable to print to both cli and web.
@Naomi Kudaka has joined the channel