Closed uleopold closed 9 years ago
This issue is related to the "area of interest" field for the test.iguess version.
If you set area of interest, as in this example, the first time to "Bospolder clipping" it does not register this correctly and still expects data in this field. But it does not tell the user which data set it still expects.
Once you set "area of interest" to "Do not use area of interest" and set it back to "Bospolder clipping" it accepted the data set and the run button appears.
In the production version (iguess) configuration of this module does not work at all. After clicking the "Create Configuration" an error message comes with "We are sorry, something went wrong".
This problem is caused by a major bug with the mod_configs controller. Basically the calculation of the mod_config status is failing spectacularly: there is a huge SQL query joining tables by character fields based on wrong assumptions. I am not yet sure how to solve this problem, but I will try to produce a patch for the fair.
This has nothing to do with the area of interest.
I found the root of the problem and there was no need to modify the query.
Great! Did you push it out to test already? It still happens for me when I configure a module in the test environment and fails in the production environment.
It seems to work now. I close it.
After successful configuration of a module the run button is not shown (see screenshot below).