Forwarded to devs PHP attribute not migrated

[mr-wolf]

TITLE:

PHP attribute not migrated​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk 17.5.3 / Ubuntu 16.04​

PROBLEM DESCRIPTION:

It has happened to me a few times before I discovered this pattern.
Sites stopped working after migration.

This was due to the PHP-parameter "allow short tags on" was not migrated to the new server.

I do not know if this is for all attributes.
I do know that I just tested this between 2 servers that have "allow short tags on" turned to off by default.
A site that has this explicitly turned on was not migrated properly​

STEPS TO REPRODUCE:

Migrate site with "allow short tags" set to on​

ACTUAL RESULT:

The migrated site has "allow short tags" set to off​

EXPECTED RESULT:

The migrated site has "allow short tags" set to on​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Need Info:

• What is the exact way for "Migrate site with "allow short tags" set to on"?

We have "Site Import" on "websites&domains" and Extensions -> Migrator -> Start new migration.
For site import, we do not migrate php settings at all, for Migrator we do.

• If you use Extensions -> Migrator then please provide screenshots with this option from source and destination servers.

Thanks.

 

[mr-wolf]

I'm using Extensions -> Migrator...
On the source server I have a site setup with this attribute:



On the target server I can see that this attribute is NOT transferred.
There I see this:



I expect that all PHP-attributes I can set with Plesk are properly transferred...

 

[IgorG]

Thank you!
Confirmed bug PMT-3183

 

[mr-wolf]

Hi @IgorG,

Apologize my ignorance in this respect.
Where can I find these?
I'm interested in keeping track of some outstanding bugs..

 

[IgorG]

Fixed bugs are listed in ChangeLog Change Log for Plesk
Plesk internal bugtracker is not public.

 

[mr-wolf]

OK...
I'm too much used to open source projects.
I can understand that it's not public...

What was exactly meant by "confirmed bug"?

Someone confirmed the bug I discovered or it was already a confirmed bug?

 

[IgorG]

it was already a confirmed bug?

Yes, it was known and already submitted bug.

 

[IgorG]

After additional investigation developers have discovered that root cause was on Plesk side in Backup/Restore module. The corresponding request was created - PPPM-7195

 

[mr-wolf]

I can remember having that issue in the past after I did a restore of only the Plesk settings of a certain site.