The server edit form has the Backend field disabled after initial server creation. This was part of a large commit here: #2445251: Plugin form validation/submission logic. I ran into an issue where I had to switch from a Solr backend to a Multilingual Solr backend which would have forced me to create a new server, a new index, and then recreate the associated View too. Ideally, I could simply toggle the Backend option which seems to work fine.
Don't disable the Backend field. I did not have an issue enabling the field and switching my Backend. If there is a reason that I am not aware of for disabling this field then maybe it would be possible to only allow switching to similar backends? For example, the Database backend could be disabled, but the Solr backends (Solr and Multilingual Solr) would be enabled if the original Backend was Solr.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2980635-3.patch | 536 bytes | mahtab_alam |
| #2 | allow-switching-backends-2980635-2.patch | 536 bytes | daniel korte |
Comments
Comment #2
daniel korteComment #3
mahtab_alam commentedComment #4
gchauhan commented@mahtab_alam instead of review the earlier patch added by daniel korte you have created the same patch.
Comment #5
drunken monkeyJust a new server – you can then simply set that as the index's new server and everything will continue working the same as before. That's why we designed it this way.
Therefore, I don't see any necessity to allow switching the server backend. It's the same as saying you want to switch a block's plugin – just create a new block instead!
Comment #6
daniel korteOkay, but there's no technical reason why you can't simply switch the backend of an existing server... So why make it more difficult than it has to be?