Skip to content

Document module export warning for invalid file paths #11887

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MarkTr0 wants to merge 3 commits into
base: development
Choose a base branch
from
Open

Document module export warning for invalid file paths #11887

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0d63e80
Document invalid path warning on module export (SOLP-4182)
MarkTr0 Sep 8, 2026
385d247
List disallowed paths and soften version wording for module export wa…
MarkTr0 Sep 8, 2026
4023aa8
Review
quinntracy Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/en/docs/refguide/modeling/import-and-export/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ Current undesired locations:
* deployment/
* nativemobile/builds/
* vendorlib/temp/
* mprcontents/
{{% /alert %}}

{{% alert color="warning" %}}
Expand Down Expand Up @@ -234,6 +235,22 @@ The app package is created and exported.

To export a module, right-click a module in the **App Explorer**, and select **Export module package**.

If your module contains files with paths that are not allowed in module packages, Studio Pro shows a warning listing the affected paths before you choose where to save the package. Studio Pro cannot import such a package. Review and correct the file paths before distributing the module. Contact Mendix Support if you need assistance.

Disallowed paths are the same as those listed above for importing, as well as path-traversal patterns (for example, `../../`):

* directories starting with '.'
* releases/
* packages/
* deployment/
* nativemobile/builds/
* vendorlib/temp/
* mprcontents/

{{% alert color="warning" %}}
In an upcoming version of Studio Pro, exporting a module that contains files with disallowed paths will also not be possible. Make sure all file paths in your module package are valid to avoid issues later.
{{% /alert %}}

If your module refers to other modules in the app (that is, it is not self-contained), you will see a warning pop-up window.

Select **Find usages of other user modules** to view the references, or click **Continue exporting** and you will see the **Select Dependencies** dialog box:
Expand Down