cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Moving Web Site Migration from Dev to Test

ToddDavey
Super Contributor

Version = HOPEX V4 CP2

Web Site Template = HOPEX360_900_v2.9

 

Hi All,

I am having a little trouble moving my custom web site template from Dev to Test.

 

To create the Web Site Template in DEV I:

- Installed Solution Pack HOPEX360_for-HOPEXV4-900-2.9

- Duplicated it (so I wasn't messing with standard objects)

- Modified necessary descriptors

- Created a few new descriptors

- Created a few new Code Templates

- Created a web site, generated and everything is looking good in DEV

 

To migrate it to Test I:

- In DEV Exported the custom web site template (at the folder level)

- In DEV Exported the HOPEX360_900_v2.9 Web Site Template (just in case)

- In DEV Exported the Code Templates

- In TEST Installed Solution Pack HOPEX360_for-HOPEXV4-900-2.9

- In TEST Imported the Code Templates

- In TEST Imported the custom web site template
This throws the error:  "Error 16811102:  There is no ‘Descriptor’ for ‘Absolute Identifier’ that has the ‘xxxx’ value" for all 55 descriptors.

It actually imports the descriptors but:

- each descriptor reverts to the original HOPEX360_900_v2.9 code

- each page (in the template properties) drops the body formatter

 

I have tried:

- overwriting the HOPEX_900_v2.9 Web Site Template descriptors by importing the ones from DEV - No change.

- Manually importing descriptors one at a time but they always revert to the HOPEX360_900_v2.9 code.

- Removing HOPEX360_900_v2.9 web site template and associated descriptors and just importing the custom web site template - no change

 

I followed exactly the the same process with HOPEX360_v1.9 and everything worked very smoothly.

I am completely stuck on this.  

Does anyone have any suggestions?

 

Thanks.

2 Replies

ToddDavey
Super Contributor

Thank you.

I was using Manage -> Export as I have for all migrations over the past couple of years.

 

The Properties -> Update method is a bit painful (it actually took almost as long to export the changes as it did to make them). 

I still don't understand why I was able to use Manage -> Export for web template HOPEX360 v1.9 without any issues but have to go through this extended processes for HOPEX360 v2.9??

 

Regardless You have solved my problem and I will move forward.

Many thanks.

LMeden
MEGA Partner
MEGA Partner

When you export from DEV, do you export via File>Properties? Or do you right click on the object and select Manage>Export? There is a big difference between the two methods. From Properties you can export all System Repository log changes (create, connect, update, delete) or data changes.

 

46b53fca-36b4-49d0-b4ad-f87b77df2fbf.png

 075f500c-ae4e-4128-ae15-bc8d516f4f90.png

https://doc.mega.com/hopex-v4-en/#page/SUP/Gerer_les_transactions.Viewing_Updates.html  (Possible this link does not work)