Skip to content

[SOLP-3381] Update Import due to security issues #9591

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.

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
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

blis-mendix
Copy link
Contributor

No description provided.

@@ -25,6 +25,17 @@ You can import and export the following:

## Importing Various Elements

{{% alert color="warning" %}}
Studio Pro prevents packages from unpacking content to undesired locations. Contact the content publisher to get the issue fixed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I understand the bit about contacting the content publisher. In the examples below the user can choose the location for the import - so they don't need to contact anyone to unpack it somewhere else.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey! This comment is to the whole chapter 2, part you talk about is in chapter 2.1 as it's specific for the solution based apps while in for example 2.2 you can't choose location.

We added a generic check during import so if we detect that content has anything we consider illegal we inform user and they can contact publisher of such module/template/widget etc.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that makes sense.
Perhaps we could say

Suggested change
Studio Pro prevents packages from unpacking content to undesired locations. Contact the content publisher to get the issue fixed.
Studio Pro prevents packages from unpacking content to undesired locations. If you cannot change the location, contact the content publisher to get the issue fixed.

Or specify the types of import where you would need to do this?

Is this urgent, or can we wait until Maria comes back to pick this up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants