Skip to content
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

[jed4] Add extension restrictions #26

Open
JazParkyn opened this issue Aug 24, 2018 · 0 comments
Open

[jed4] Add extension restrictions #26

JazParkyn opened this issue Aug 24, 2018 · 0 comments

Comments

@JazParkyn
Copy link
Member

The main change from the current system is that a free, paid and cloud service distribution types of the same extension will be submitted, managed and viewed on the same page.

Add extension view to only allow users to add one of each distribution type (free, paid, cloud service) for each extension.

#__jed_extension - contains the information shared between the distribution types
#__jed_extension_detail - contains the information about the specific distribution type

A user must select at least one distribution type, and cannot have more than one of each type.

A file upload will be required for each type selected, and will eventually be run against the JED Checker

The component should check the user’s account for any pending issues. The component should prevent submissions if:

  • the user has 3 pending submissions.
  • the user has a suspended account.
  • the user has any unpublished listings for any reason other than UR5 (per developer request).

Submission checks:

  • All tests currently present in JED
  • Pass JED Checker against all files uploaded
  • Match Listing Name against install name
  • Reserved Words should be accepted (eg. Joomla, component, module, plugin, free, paid, etc)
  • Check to see if the alias for the extension already exists

Please see the spec document for further clarification on this process - see: Front-End Submission Process

If it passes, continue.
If it doesn’t pass, display issues from checker to user.
If it doesn’t pass, the user has the option (via checkbox) to bypass the check and describe why the submission is valid. In this scenario, the submission will be placed in a manual review queue.

The possibility of auto populating some fields using data from the extension’s XML install file should be reviewed.

@JazParkyn JazParkyn transferred this issue from another repository Aug 9, 2019
@roland-d roland-d transferred this issue from another repository Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant