phyzical

i think its due to how sitetree automagicaly did it

Aaron Cooper

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.

Aaron Cooper

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.

Aaron Cooper

> 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.

phyzical

but as a usecase maybe a client wants to muck around with a site before allowing customers to view things

phyzical

if you add "owns" it does get published on save (or has it changed)

Aaron Cooper

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.

Show 1 attachment(s)
Lorrain Fontaine

Yeah I now know how to and almost never forget to do it, but jesus, when I had to make my first website using SS4, I struggled for a few hours with that :stuck_out_tongue:. It should be written in caps and red, above anything else haha

Hide attachment content
taoceanz

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? I've tried Debug::message and setting up the logger to run $this->logger->info though they're not printing anything to the terminal. echo or var_dump shouldn't be reasonable options, though they seem to be the most reliable to print to both cli and web.