View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002563 | OXID eShop (all versions) | 6. ------ Setup ------- | public | 2011-02-25 12:34 | 2012-03-07 14:41 |
| Reporter | DerDaniel | Assigned To | |||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | Hetzner Root-Server | OS | OpenSuse | OS Version | 11.0 |
| Product Version | 4.4.6 revision 32697 | ||||
| Summary | 0002563: Database password with '$'-char creates incorrect config | ||||
| Description | Setup-routine creates the database correctly but then writes a wrong password to the config file. Example: Orig-Password: "b4F5$saWv" Password in config: "b4F5saWv" Looks like the $ is stripped while writing the config. | ||||
| Steps To Reproduce | Create a DB with a password with a $ in it. Use the Setup to create a new shop installation. Setup-routine runs correct. DB is created. First request to the Shop-Frontend:: Connection Error [...]Access denied for user '#####'@'localhost' (using password: YES) ->offline.html Shop-Backend: Connection Error [...]Access denied for user '#####'@'localhost' (using password: YES) -> redirect /admin/offline.html -> 404 | ||||
| Additional Information | Looks like the $-char is stripped out of the password before writing it to the config file. I didn't check for other special characters but it's reproducable with a $. | ||||
| Tags | No tags attached. | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.3 | ||||
| Database Version | any | ||||
|
|
Reminder sent to: DerDaniel Hello, sorry, but i can not reproduce the case. password with '$' symbol in it is added correctly to config file and shop works after instalation. could you please let us know if you experience same problem on other servers and with our latest eShop 4.5.0 release? greetings, |
|
|
same problem here with the $ in database password: http://www.oxid-esales.com/forum/showthread.php?p=69229#post69186 |
|
|
Hi, We cannot reproduce such issue on current versions (nor 4.5.8, neither latest 4.6 development version). Could you please let us know if you still experience same problem on our latest eShop version 4.5.8 or latest development 4.6)? Best regards, |
