Why?: "we have standardized our publishing"

[brad]

@George

Furthermore we have standardized our publishing and automatic file upload, so that it happens only on development target sites.
For production sites you will have to do full publish/deploy to update your site.

What is the purpose of this? This makes no sense to me and takes ten times longer to make a simple edit to a site. Even worse if all you did was make a simple change to a server action.

[sitestreet]

If you want it as it was before, just set the target to be ‘development’ and it will behave as you’re used to.

[brad]

So, the only differences between the three target settings is when it saves?

[sitestreet]

I think so.

[Teodor]

@brad

This makes no sense to me and takes ten times longer to make a simple edit to a site.

Well, ask people like @TomD who says he’s scared to save or publish
Set your target to development and it will auto upload on save.

[brad]

@Teodor

Set your target to development and it will auto upload on save.

So, again, is that the only functionality difference between the three target settings? For now and in the future?

That’s just a dead setting that really doesn’t do anything other than save or not as of 3.7.3?

If it’s just a dead setting that does nothing else I will change to development.

[Teodor]

@brad

So, again, is that the only functionality difference between the three target settings?

Yes

[JonL]

@brad

What is the purpose of this?

It’s just one of those little things we like to call “good practice”
The day will come when you regret deploying on save

[George]

See:

Restrict Product and Staging Environments to Publish Only

Referencing this topic: I believe that a Staging or Production target should NOT allow for the direct upload of any file upon saving a change. The risk of inadvertently making changes to these environments is too great. Files should only be pushed to the target if the Deploy or Publish buttons are pressed – and even then the user should be presented with a dialog reminding the user which target they are deploying to. The main point being, that the workflow to publish to staging and produ…

[brad]

Thanks guys. I now understand the reasoning. I will leave my target set to Production and adjust my workflow. At least I know that when just making simple changes I can adjust it. All good.

[TomD]

@Teodor

Well, ask people like @TomD who says he’s scared to save or publish

Not exactly . I’m not scared to ‘save or publish’. I’m scared to ‘save and publish’ - at the same time, particularly when I just intended to save .

It was too easy to do before - you just pressed Ctrl+S, but failed to notice you have left the target to ‘production’.

[Dave]

@Teodor

@TomD who says he’s scared to save or publish

@Dave too! Those auto upload days did my tiny little head in!

[Teodor]

I was just joking guys
I agree with you both.

[max_gb]

I’m still waiting for the “are you sure you want to exit Wappler” and “are you sure you want to Minimize Wappler” popups…

[Dave]

@max_gb Ouch hahahahahaha. Spat coffee out!

[max_gb]

Tbf I did vote for the save/upload request. Just being salty