Possible Bug with ampersand '&' After Migrating.

[Antonelos]

Hi everyone,

I'm experiencing a problem after migrating some domains from Plesk 10.4.x to 11.0.9. More specific every time migration manager meets a password in
configuration or email account containing the '&' symbol, then by default erases anything follows. An example if in my wp-config.php
use define ('DB_PASSWORD', '41yRe&sl4!') then after the migration this line will be define ('DB_PASSWORD', '41yRe&'). The migration
manager does not produce an error regarding this changes.

 

[abdi]

An example if in my wp-config.php
use define ('DB_PASSWORD', '41yRe&sl4!') then after the migration this line will be define ('DB_PASSWORD', '41yRe&'). The migration
manager does not produce an error regarding this changes.

This is almost impossible to believe ie the much I know is that the migration manager only moves physical files and databases AND does NOT modify any web files (unless if possibly these web files were installed through the APS) but otherwise, no way ..

About the email passwords, that could be possible if earlier in your plesk 10 version you had not enabled high security measures such as encrypting passwords ...

Never the less, if you really believe this is abug, you can report it here (with instructions of how to reproduce this situation):

http://plesk.uservoice.com/

 

[Nikolay.]

Never the less, if you really believe this is abug, you can report it here (with instructions of how to reproduce this situation):

http://plesk.uservoice.com/

Parallels representatives have said it several times: uservoice is not a place for bug reports, but only feature requests and ideas so that community may vote for them. Bugs are usually reported here.

Please don't mislead other community members.

 

[Antonelos]

Parallels representatives have said it several times: uservoice is not a place for bug reports, but only feature requests and ideas so that community may vote for them. Bugs are usually reported here.

Please don't mislead other community members.

Thank you both for your replies,

I'm sorry for misguided you. I will take adbi's advice and open a report.

 

[IgorG]

if you really believe this is abug, you can report it here (with instructions of how to reproduce this situation):

http://plesk.uservoice.com/

Really, abdi, I warned you already that it is absolutely wrong suggestion! Please stop suggest uservoice as place for bugreports!

 

[Antonelos]

I believe i make a mess for open this thread without read the rules first. So, I'm going to ask anyway, is there a bug report thread?
because i did a fast research and most bug keyword threads were opened under this section. Again, sorry for troubling you.

 

[IgorG]

First of all, have you checked this behaviour on latest version of Plesk 11.5.30 with all installed microupdates?

 

[Antonelos]

No, the migration was from Plesk 10.4.4 to 11.0.9

 

[IgorG]

Why you can't use latest version of Plesk?

 

[abdi]

Really, abdi, I warned you already that it is absolutely wrong suggestion! Please stop suggest uservoice as place for bugreports!

Copy that ...& sorry for the inconveniences caused.

 

[Antonelos]

Why you can't use latest version of Plesk?

because I met this problem between this two versions. Obviously we did not upgraded to the latest version,
at least not until we make sure that it is possible for many reasons.

 

[IgorG]

Try to play with Password strength on pge Tools & Settings>Security Policy

 

[Antonelos]

I could do that, our custom password strength is set at "medium" on both servers, but I believe this is obviously
a bug because the password strength on some email accounts is 14digit, also on my first post this example is something
that really happened and this is the exact password.