maverick/docbrown
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Mark Buffer as legacy (#9907)

Browse source 
* Mark Buffer as legacy

* Fix logic
This commit is contained in:
Ben Halpern 2020-08-24 08:48:15 -04:00 • committed by GitHub
parent cf3db038c7
commit 17df627f0d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.env_sample
View file

@ -63,6 +63,8 @@ export AWS_S3_VIDEO_ID="Optional"
export AWS_S3_VIDEO_KEY="Optional"
# Buffer for sending to buffer
# This is legacy, as Buffer no longer supports this functionality for NEW accounts.
# DEV is still using this for now.
# (https://buffer.com/developers/api)
export BUFFER_ACCESS_TOKEN="Optional"
export BUFFER_FACEBOOK_ID="Optional"

8
app/views/admin/articles/index.html.erb
View file

@ -1,4 +1,10 @@
<% if @user_buffer_updates.any? %>
<% if ENV["BUFFER_ACCESS_TOKEN"].blank? %>
<div class="alert alert-warning" role="alert">
<p><strong>All references to "Buffering" are legacy and social media functionality is not currently operational.</strong></p>
<p>Buffer, the social media scheduling tool, has discontinued its API, so send-to-buffer functionality only works for legacy clients.</p>
<p>We will replace this functionality in the future with a functional alternative.</p>
</div>
<% elsif @user_buffer_updates.any? %>
<div class="alert alert-primary">
You have sent <strong><%= @user_buffer_updates.size %></strong> buffers so far in the past 24 hours. Keep it up!
</div>