When will roadmap items be added?

[VarenSwaab]

I really love the functionality of this plugin and will probably buy it for a site I'm working on but there are a few items listed in the Roadmap that I'd like to have. I'm wondering if these items will ever make it into the plugin?

[matthewbacon]

Yes the AJAX Follow/Unfollow would be top of my list as would be different lists per siteId.

[bymayo]

I'll add AJAX follow to the top of the list.

This plugin seems to be getting some traction and bug reports over the past few weeks. So i'll drop some features on it.

Any questions, hit me up on Discord (@bymayo)

[VarenSwaab]

Thanks for the reply bymayo, any guesstimate of when you will release an update?

[bymayo]

@VarenSwaab Which roadmap feature are you in need of?

[VarenSwaab]

@bymayo Thanks for asking, this would be my preferred order:

Notifications
Ajax for follow buttons
Different lists per siteId
Accept / Deny the follow request
Limits on queries.
Auto output users elements, rather than passing a list (not really sure what this is)

[bymayo]

@VarenSwaab No problem.

Just FYI the accept/deny follow request will be added in the next week as this got added in due to a request from a client. Notifications will follow not long after.

Ajax for buttons, this will just be an example. I might also put an AlpineJS example in. I'm working on generating examples today.

[matthewbacon]

Great to hear

…

On 12 Jun 2020, at 11:14, Jason Mayo ***@***.***> wrote: @VarenSwaab <https://github.com/VarenSwaab> No problem. Just FYI the accept/deny follow request will be added in the next week as this got added in due to a request from a client. Notifications will follow not long after. Ajax for buttons, this will just be an example. I might also put an AlpineJS example in. I'm working on generating examples today. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACT7D3UKCOX3DWRHKRHJGA3RWH52HANCNFSM4KIVQ6FQ>.

[tom-byrom]

@VarenSwaab No problem.

Just FYI the accept/deny follow request will be added in the next week as this got added in due to a request from a client. Notifications will follow not long after.

Ajax for buttons, this will just be an example. I might also put an AlpineJS example in. I'm working on generating examples today.

looking forward to this update @bymayo

[JMKelley]

Following this, looking forward to the AJAX buttons.

[tom-byrom]

Seen a couple of you were interested in Ajax follow buttons (@JMKelley @VarenSwaab @var` ), I've just done this in Vanilla JS. @bymayo might be able to advise a better solution, not sure what your example was going to be mate? But this works well enough for me atm without dependencies. Might need to change things depending on your setup.
This would also work if JS didn't fire on the page for some reason as the links are standard.

HTML/TWIG

{% if currentUser %}
{% if craft.follow.check({ elementId: author.id }) %}
<a id="followBtn" data-author="{{ entry.author.id }}" class="unfollow btn btn-outline-primary btn-sm d-block" href="{{ craft.follow.unfollowUrl(author.id) }}">Unfollow</a>
{% else %}
<a id="followBtn" data-author="{{ entry.author.id }}" class="follow btn btn-primary btn-sm d-block" href="{{ craft.follow.followUrl(author.id) }}">Follow</a>
{% endif %}
{% else %}
<a id="followBtn" data-author="{{ entry.author.id }}" class="nofollow btn btn-primary btn-sm d-block" href="/register">Follow</a>
{% endif %}

JS

let followBtn = document.getElementById('followBtn')

followBtn.addEventListener('click', function(){

    let authorId = this.dataset.author

    if (followBtn.classList.contains('follow')) {
        event.preventDefault()
        fetch('/index.php?p=actions/follow/element/follow&elementId='+authorId)
        .then(function(response) {
            if(response.status) {
                followBtn.classList.remove('follow', 'btn-primary');
                followBtn.classList.add('unfollow', 'btn-outline-primary');
                followBtn.setAttribute('href', '/index.php?p=actions/follow/element/unfollow&elementId='+authorId);
                followBtn.innerHTML = 'Unfollow'
            }
        })
    }
    if (followBtn.classList.contains('unfollow')) {
        event.preventDefault()
        fetch('/index.php?p=actions/follow/element/unfollow&elementId='+authorId)
        .then(function(response) {
            if(response.status) {
                followBtn.classList.remove('unfollow', 'btn-outline-primary');
                followBtn.classList.add('follow', 'btn-primary');
                followBtn.setAttribute('href', '/index.php?p=actions/follow/element/follow&elementId='+authorId);
                followBtn.innerHTML = 'Follow'

            }
        })
    }
    else {
    }
})

FINAL EDIT

Updated - so now does not use inline JS and gets element id from a data attribute on the follow button itself