27

Okay, I want to build an App that allows me to create questions on Stack Exchange. I registered it here on Stack Apps but now when I want to create a question I get this message:

{
  "error_message": "Applications must have a registered Stack Apps post to write",
  "error_id": 403,
  "error_name": "access_denied"
}


On my profile the Stack Apps Post is set to Not set and it tells me that my app has to be published first:

Stack Apps Post

Not Set

When you've published your application, it should be listed on Stack Apps with the app or script tags.

But how should I publish something, that I could not initially test? And how would I publish my App (not that I would be ready for this now)?

1 Answer 1

20

It's a bit of a Catch-22. Work around it by:

  1. Make a (or ) post for your app (or script).
  2. Also tag it with .
  3. And put "PLACEHOLDER - " at the beginning of the title.
  4. Provide a summary of what your app will do.
  5. Go to Your apps and click your new app registration
  6. Click Edit details and in the Stack Apps post field post the link to the post you created

Also, indicate in the post text that the app is not yet ready for prime time.


This has already been done a few times, for example:


Warning: Don't abuse this, or create an essentially empty post and not update it expeditiously. Otherwise the question will be closed and, if not corrected, quickly deleted.

5
  • 6
    Oh, I was wondering why people were creating placeholder questions. Thanks for explaining this because I was considering flagging them. Commented Mar 2, 2014 at 23:50
  • @jmort253 Ok, I can surely do this. How will this then be linked to my App and its identifier? With the "Chatdump" example there is no reference to any Stackapps app. Commented Mar 3, 2014 at 7:09
  • 2
    @Besi, go to your app page -- which only you can see -- and press the Edit This App button near the bottom. Then paste a link to your app post in the Stack Apps Post box and submit the changes. Commented Mar 3, 2014 at 7:58
  • Can you please explain the "placeholder" close reason, then? Commented Apr 4, 2018 at 1:29
  • @gparyani, see the inaugural post. That close reason is a response to a rash of questions that never showed any effort whatsoever. Best I can tell, it's actually been used about 3 times, and I guarantee that no one who has read this Q&A has had that close reason applied to them. In practice, no one here has made any effort to close all stagnant [placeholder] questions -- of which many remain. And if such a question is put on hold, it's not "just procedure" and they can't just fix it by removing placeholder indications. Commented Apr 4, 2018 at 3:10

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.