View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008718 | VALENTINA SERVER | ini-file | public | 2020-02-06 07:14 | 2020-02-15 18:28 |
| Reporter | François Van Lerberghe | Assigned To | Ivan Smahin | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | ALL | OS | ALL | OS Version | ALL |
| Product Version | 9.7.x | ||||
| Fixed in Version | 10.0.x | ||||
| Summary | 0008718: VServer now will not create file 'vServer.ini.example' | ||||
| Description | Each time vServer is launched, a file vServer.ini.example is created, even if vServer is customised (name has been modified). In a embedded vServer configuration, this file creation is not needed/wanted. | ||||
| Steps To Reproduce | Launch vServer or change its name and launch it | ||||
| Additional Information | I think it must exist a way to bypass this file creation. Today, someone can see the example ini file - in a fresh download - detailed in the comments of the ini regular file - explained in the wiki Why a developer could want to see it again if he/she has customised the vserver file ? The rule could be : Create the example ini file if - there is no ini file or - if vserver name is the same or - both | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-02-06 07:14 | François Van Lerberghe | New Issue | |
| 2020-02-15 10:15 | Ivan Smahin | Assigned To | => Ivan Smahin |
| 2020-02-15 10:15 | Ivan Smahin | Status | new => resolved |
| 2020-02-15 10:15 | Ivan Smahin | Resolution | open => fixed |
| 2020-02-15 10:15 | Ivan Smahin | Fixed in Version | => 10.0.x |
| 2020-02-15 18:28 | Ruslan Zasukhin | Summary | The file vServer.ini.example is created each time vServer is launched => VServer now will not create file 'vServer.ini.example' |
