Skip to main content
Two things have to happen before a script is in the catalog: a version passes its build and checks, and you put the item on the market with the button at the bottom of the editor. This page covers both, and what happens when either says no.

​
The button

You press it once per item. New versions after that don’t need it: each one goes live on its branch when it passes.

​
When the button refuses

​
Fields in red

First the editor checks the form. Wrong fields turn red, the page scrolls to the first one, and the toast says Fix N fields.

​
Not published

Then the server checks the item and answers Not published with every reason at once:
A failed build’s number is free again: nobody saw that version. You can fix the code and publish the same number.

​
Moderation

Only code with extra permissions is reviewed by a person. A version goes to a moderator when:
  • it ends up with ffi or filesystem, its own or through a library;
  • or most of its code matches an open script whose author doesn’t allow forks (“Looks like a fork”).
Everything else is published by the automated checks alone, in the time the build takes. A moderator reads your sources, the dependencies, the permissions and what changed against the live version, usually within a day. The decision is one of: The note is in the editor’s Moderation section and next to the item in My items. Fix the code and run spd publish again. While a request is open, a new version on the same branch replaces the old one in it, so the moderator always looks at your latest.

​
After approval

  • You already pressed Send for review: the item goes live by itself. Nothing else to do.
  • You didn’t: the version is approved, but the item stays a draft until you press the button.
  • The moderator requested changes: the item went back to a draft. Publish the fix and press Send for review again.
  • A new version of a published item: it becomes current on its branch, and buyers on that branch get it.

​
Automated checks

Every build, with or without a moderator, goes through these checks. Any failed check stops the version: the build is failed with checks-failed, and the log lists why. Warnings don’t stop anything.

​
States

​
After publishing

  • Text and price edits are live as soon as they’re saved. They aren’t reviewed in advance.
  • Category can’t change, and the product stays what you picked.
  • Hide from catalog in the item’s menu in My items takes it off the shelf; Back to catalog returns it. Buyers keep their access either way.
  • Delete draft works only for a draft or a rejected item that nobody owns. A script or library with approved versions can’t be deleted: hide it instead.
  • Moderators can take an item down after a report. See Reviews, reports and disputes.