Kit import unnecessarily fails in some edge cases

[jamieburchell]

Prerequisites

• I have searched for similar feature requests in both open and closed discussions and cannot find an existing request.
• I have verified that the feature is still missing from the latest stable versions of Elementor or Elementor Pro.

What problem is your feature request going to solve? Please describe..

Two things bugging me about Elementor's kit import function:

1. It refuses to import a kit if the root of the wp-content directory is not writable, even though it doesn't write here during import (it writes to wp-content/uploads/elementor and that is writable).

In an environment where permissions are locked down (such as when using Roots Bedrock and/or implementing WordPress hardening best practises) this is an unnecessary barrier.

2. If you have already installed a newer version of a plugin the kit requires and you have DISALLOW_FILE_MODS enabled, the import will complain that the required plugins cannot be installed. If you temporarily disable DISALLOW_FILE_MODS and retry, the import process will tell you that you've already got the plugin installed at a newer version and will allow you to proceed.

It seems the importer checks if plugins can be installed before it checks to see if it actually needs to install a plugin. Again this is an unnecessary barrier if you have already met the kit's dependencies.

Describe the solution you'd like.

Allow a kit to be installed if the uploads/elementor directory is writable (or whatever location it wants to store tmp files) and the plugin dependencies are met.

Describe alternatives you've considered.

No response

Additional context

No response

Agreement

• I agree that my request may be closed without action if it doesn't meet all the requirements.