Community « Discussion forum « Installation support « Update issue «
Comment: Update issue
| << Previous | Next >> |
Actually this is a feature, not a bug! Yes, I know, it may sound like a statement from Micro$oft, but this is true.
Versions made available to synchronization are either stable versions, or, in some cases, beta versions.
The synchronization process does not take care of dates. Its only purpose is to ensure that your server is an exact copy of the reference one.
This means that if you install an alpha version, and would like to go back to previous version, you just have to synchronize, and this is what you did...
Maybe it would help that the synchronization process could generate a warning and ask for confirmation if it detects that the current server has a higher version number than the one provided by the reference server.
If you think that this would be a nive feature, please post a new requirement to the suggestion box, and let the community discuss this.
Versions made available to synchronization are either stable versions, or, in some cases, beta versions.
The synchronization process does not take care of dates. Its only purpose is to ensure that your server is an exact copy of the reference one.
This means that if you install an alpha version, and would like to go back to previous version, you just have to synchronize, and this is what you did...
Maybe it would help that the synchronization process could generate a warning and ask for confirmation if it detects that the current server has a higher version number than the one provided by the reference server.
If you think that this would be a nive feature, please post a new requirement to the suggestion box, and let the community discuss this.
by Bernard on Apr. 20 2007
