Different user input file for upgrades?

Is there any way to show a different user input screen for those upgrading a package? There are questions you might want to ask (or not ask) during an upgrade.

If not, would it work to create the user input source file dynamically in a script resolver attached early in the install?

Also, am I correct in assuming that setting update_object->false will prevent the install from overwriting an existing resource or element?

Bob,

Could you create a ticket for that? That’s a good idea.

As for your first question, resolvers only work after the install is running, which is after the setup options are running.

And your second question, yes. That is correct.

Quote from: splittingred at Nov 28, 2008, 08:14 PM

Bob,

Could you create a ticket for that? That’s a good idea.

Done -- [#MODX-538].

I had another idea related to build scripts. It may kind of late to implement it and there may be reasons why it isn’t a good idea, but I thought I’d mention it.

It’s to change the name of the $vehicle->resolve() method in PB to $vehicle->addResolver().

I think the name of that method is a big part of why I didn’t like the term "resolver" in the first place. I think calling it addResolver() might be more clear about what’s happening and also kind of informs people that you can add more than one (once you "resolve" something, you wouldn’t think of resolving it again).

The current name suggested to me that the method involved the vehicle resolving itself, which I found very confusing. Adding a resolver to a vehicle and, in the process, specifying it’s type and source file seems much more "down to earth," without, IMO, being significantly less accurate.