Follow button "internal server error" when not logged in
#408
Open
opened 5 years ago by hmmwat
·
6 comments
No Branch/Tag Specified
paginate-search-init
main
s3
fix-delete-user
timeline-cli
blog-title
signature
remove-dup-images
ldap-non-anon
drone-ci
DearRude/force-lang
igalic/go/async-all-mut
go/async
floreal/translations-update
missing-docs
RAOF/fix-arm64-build
epsilon-phase/authorized-fetch
upgrade
improve-the-editor-once-again
igalic/feat/custom-fairing-domains
feature/ldap
test/dotenv_error
fix-mobile-margin
0.7.2
0.7.0
0.2.0-alpha-1
0.3.0-alpha-2
0.4.0-alpha-4
0.5.0
0.6.0
0.7.1
Labels
Clear labels
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Apply labels
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
No Label
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#408
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
Hi, I'm new to plume and was trying to follow a blog (on cafe.sunbeam.city) with my mastodon account. Not sure if that's how it works but anyway, when I clicked the follow button it went to an error page of "internal server error". I also tried it on some other instances and it still did the same thing. Hopefully this is the right place to report what might be a bug.
Plume version (and/or commit):
Hello! This is indeed the right place to report bugs.
Is the follow button you are speaking about in Plume's interface or on Mastodon?
It was on plume. But I also couldn't see anyones content when I looked them up from mastodon. Idk if that's relevant.
Ok, then it is normal you couldn't follow them from Plume if you were only connected on Mastodon. Even if the two websites can communicate, you can't login with your Mastodon account on Plume (and vice-versa). The solution is either to create a Plume account or just to follow with your Mastodon account (this second option is probably the best if you don't plan to write anything on Plume, only to follow blogs).
And I think it is a known bug that Mastodon is not fetching previous messages for accounts that were recently discovered, but there is not much we can do about it.
However, I agree that the "Internal server error" page is confusing, it should redirect to the login page instead. Can I edit the title of your issue?
the problem with "Internal server error" is the message used to build the redirect Uri containing illegal characters (spaces). We should
Uri::percent_encode
the message inrequires_login
.We could also implement the remote follow button Mastodon provide to follow users from other instances, it would be more intuitive for users
Hi @BaptisteGelez I think I'm having the same/a similar problem. I'd like to follow a blog on cafe.sunbeam.city as well. Typically, I can paste a URL to a post or profile into the search bar in Mastodon and it will pull up the item for me to act on, but this isn't happening for the blog post or blogger in question:
https://cafe.sunbeam.city/@/Gwenfars Garden
https://cafe.sunbeam.city/~/GwenfarsGarden/what-does-a-solarpunk-future-look-like
Is this likely a Plume issue or a Mastodon issue? (Or both?)
This user has a space in it's username, which we no longer authorize as it's incompatible with most other fediverse softwares, this account was created before the restriction was added. Sadly the only fix would be for this user to recreate their account with another username, or for the admin to tinker with the database to rename the account