More understandable publishing errors in UI

In order to make notifications regarding publishing errors more clear, we have introduced easily understandable explanations of the 10 most common errors. Users will now better understand what’s going on the next time a post might fail, for instance.

Errors that are included:

• (#200) Subject does not have permission to post photos on this page
• The content you're trying to share includes a link that our security systems detected to be unsafe:\n\ngmil.com\n\nPlease remove this link to continue
• (#200) Requires manage_pages and publish_pages to manage the object
• (#200) The user hasn't authorized the application to perform this action
• (#200) Subject does not have permission to post videos on this target
• (#200) User does not have sufficient administrative permission for this action on this page
• Due to activity related to copyright infringement on your Facebook account, you can't upload videos. For more details, visit the Help Center.
• Timeout on hera remote: POST /1/facebook/proxy
• There was a problem uploading your video file. Please try again with another file.

Split multipost in Publisher into individual posts (Approval, Scheduled, Error)

• Posting to numerous profiles at once is nothing new. However, in the past, if one of the pages required approval, all of the pages in the list were blocked and no post was published. This will be now solved thanks to “multi-post” publishing. The multi-post in question will be split into two parts - one containing all posts for approval, one ready to be published (scheduled). As a result, more content will be able to be published straight away, making for a more streamlined content flow.

"Waiting for approval" feed in Community

• In order to streamline Community-related actions, we have added a new feed that will contain all comments, replies and direct messages waiting for approval to Community. Not only will this allow users to have a more complete overview of the actions they need to take on their profiles - given enough permissions, users will additionally be able to approve content directly from this feed in Community, allowing for clearer and more time-efficient community management. 
• A user without the appropriate approval permissions will see the following explanation message in Community’s “Waiting for approval” feed: 

"Publishing Problems" feed in Community

• In addition, a second feed - “Publishing Problems” - has also been added to Community, making it easier for users to review all publishing problems of comments, replies and direct messages. Users will additionally be able to sort everything out in Community by clicking on “Resolve Error”. 
• Moreover, these particular publishing problems will be removed from Publisher’s “Publishing Error” feed.

Comments and direct messages no longer in "For approval" feed in Publisher

• Finally, with the launch of the above mentioned “Waiting for approval” and “Publishing problems” feeds in Community, users will be able to approve all Community-related content directly there, making for a much smoother process and allowing users to take care of most actions without going back and forth to different tabs.
• Comments and DMs have therefore been removed from Publisher as it didn’t make sense to have them there. They are now part of Community and can be accessed in the “Incoming” and “Direct Messages” feeds.