Bug report #8772
Deactivating a module in Modeler has no effect after the save and close of the model
|Affected QGIS version:||2.4.0
|Pull Request or Patch supplied:||No
|Crashes QGIS or corrupts data:||No
||Copied to github as #:||17478
Deactivating a module in Modeler only takes effect while the Modeler is open. From the moment you close Modeler, desabled modules are automatically reactivated. If you reopen the model, they appear activated.
In the same way, if you run the model with the Modeler still open, it jumps the deactivated modules. If you run after closing, all modules are executed.
Tested on Linux with QGIS 2.0.1.
- Priority changed from Normal to Severe/Regression
Im going to change the priority of this bug because in complex models it is sometimes necessary to disable parts of the processing chain in order for them to run successfully.
I'm changing this to non-blocker for different reasons:
a blocker means a regression, this should not be the case, and then processing can be always updated as plugin update, so I don't think that even a huge issue should block a qgis release.
- Priority changed from Severe/Regression to High
- Project changed from 78 to QGIS Application
- Category deleted (
- Crashes QGIS or corrupts data set to No
- Affected QGIS version set to 2.4.0
- Category set to Processing/Modeller
- Status changed from Open to Closed
This is no longer true. Since the modeler was rewritten, the enabled/disabled state of algorithm is kept in the modeler file, and used when running it
I am closing this issue, since it should already be fixed
Also available in: Atom