Stick/unstick gets 'white screen"

[sterndata]

Attempting to stick or unstick a post generates a screen empty except for "1" or "-1".

see ​https://wordpress.org/support/topic/stick-and-unstick-problem/

[netweb]

Confirmed

A couple of notes from testing:

• Creating a normal topic in a standard forums:
  • Creating a new topic with the topic status set to "sticky" does not stick the topic to the forum as it should.
  • Clicking "Stick" does correctly stick a topic to its forum
  • Clicking "to all forums" does correctly super stick a topic to all forums

• Creating a topic in a plugin forum:
  • Creating a new topic with the topic status set to "sticky" does not stick the topic to the forum as it should.
  • Clicking "stick" from either the topic or sidebar "stick" actions the result is a blank page containing only -1

Related: #2418 / [5329]

[Shelob9]

I tried to unstick a post for a topic in the forum of a plugin I am a committer and contributor​ for that I was not the author of. I got this same error.

I hope that as part of this fix, that power, the ability to unstick any post, not just one's own, is provided to plugin contributors.

[SergeyBiryukov]

In 5358:

Support Forums: Rename Stick/Unstick action keys for plugin and theme topics in Stickies_Compat to avoid conflicts with the same actions for regular topics.

See #2747. Fixes #2418.

[SergeyBiryukov]

Replying to netweb:

• Creating a new topic with the topic status set to "sticky" does not stick the topic to the forum as it should.

Confirmed, but appears to be unrelated to #2418, I can reproduce this even without the changes in [5329].

• Clicking "stick" from either the topic or sidebar "stick" actions the result is a blank page containing only -1

Should be fixed once [5358] is deployed.

[Otto42]

Deployed and this now appears to be fixed. Sticky and unsticky in plugin forum views works again.

[netweb]

Replying to SergeyBiryukov:

Replying to netweb:

• Creating a new topic with the topic status set to "sticky" does not stick the topic to the forum as it should.

Confirmed, but appears to be unrelated to #2418, I can reproduce this even without the changes in [5329].

Likewise, and confirmed as a bbPress issue, created ​#bbPress3103 to track this