[RESOLVED] Package Editing

[Tom]

Hello,

Following the migration of the WAPT server from version 2.2 to 2.4.0.14143 on Windows, I can no longer edit packages in the "WAPT Package Development (Tech Preview)" console.

Every time I try to edit a package, I get the message shown in the attached image.

Regards

[Tom]

Hello,

I'd like to explain the problem in more detail.

When I create a package via WAPT Package Development and then edit it, I get an error message when I try to save it locally or upload the build.

Regards

[sfonteneau]

Do you then use the package development tab to edit it?

[Tom]

Yes, I use this console to create and modify packages because I haven't installed the WAPT DEV tools on my machine.

[sfonteneau]

Is the package folder already present locally?

Is drive G a network drive? (Note that in this case, editing a package involves privilege escalation; if you use an account that doesn't have drive G, it will crash.)

[Tom]

I tested it by creating a new empty package and on the packages I had already created.

I create the packages directly on the WAPT server, and they are located on the local G drive. My account is the local admin of the server.

[vcardon]

I create the packages directly on the WAPT server and they are located on the local G drive. My account is the local admin of the server.

It is strongly recommended to have a WAPT administration and package creation PC that is not the WAPT server, see the official WAPT documentation.

If you develop your packages on the server, then the server has your WAPT administrator key and the server becomes an ultra-sensitive asset.

It's just good advice, not an obligation.

[Tom]

Hello,

this is the solution I wanted to test. I installed the WAPTDEV tools on my machine to create the packages and I will compile them on the server.

Regards