You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subscribe newsletter component not working as it is linked to a getrevue website that is no longer in use. It needs to be linked to hashnode. I think there are 2 ways to fix this issue :-
Simply replace that old getrevue website link with kubesimplify's newsletter page of hashnode with this link https://blog.kubesimplify.com/newsletter but with this link users will get redirected to kubesimplify's newsletter page of hashnode from kubesimplify's website (Refer below screenshot).
Like other websites, making user subscribe to newsletter directly at kubesimplify's website by taking user's email address and clicking a subscribe button. And adding user's email to hashnode's mailing list of kubesimplify using some kind of API.
Screenshots
Additional information
An issue similar to this one #230 is already open with unsuitable tag of [Other] and i think that's why it's been 4 months and that issue has not been taken much seriously and its still not resolved.
The text was updated successfully, but these errors were encountered:
Description
Subscribe newsletter component not working as it is linked to a getrevue website that is no longer in use. It needs to be linked to hashnode. I think there are 2 ways to fix this issue :-
Simply replace that old getrevue website link with kubesimplify's newsletter page of hashnode with this link
https://blog.kubesimplify.com/newsletter
but with this link users will get redirected to kubesimplify's newsletter page of hashnode from kubesimplify's website (Refer below screenshot).Like other websites, making user subscribe to newsletter directly at kubesimplify's website by taking user's email address and clicking a subscribe button. And adding user's email to hashnode's mailing list of kubesimplify using some kind of API.
Screenshots
Additional information
An issue similar to this one
#230
is already open with unsuitable tag of [Other] and i think that's why it's been 4 months and that issue has not been taken much seriously and its still not resolved.The text was updated successfully, but these errors were encountered: