-
Notifications
You must be signed in to change notification settings - Fork 1
WordPress signon for FeedLand #226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Dave, The first time I tried I was signed in to FL with email on iPad, got the same message. Cheers John |
@troutcolor -- could you do it again? i have the log running now, didn't have it before. should be easy to fix (he said too confidently). |
I believe I found and fixed the problem that was making it not work for @troutcolor. |
@scripting just logged on on on iPad successfully, thanks. Cheers John |
BTW, this place is just for support, things like this --
It's not a place to discuss blog posts that may be about this product, those are my opinions. If you have questions or comments about my blog writing, or even why certain features are not in the product, you can if you want write a blog post of your own and send me a link. I'll read it, but can't guarantee that I'll respond. |
Uh oh!
There was an error while loading. Please reload this page.
You can now sign on feedland.org with a WordPress account.
It's a good idea to read this whole page before trying it, so you know what to expect.
How it works
If you sign on with WordPress, one of three things happens.
This is only complicated because on feedland.org we are supporting both kinds of login. On a system that only allowed one, it would stay simple.
Also if you're worried about creating an extraneous account, please go ahead. Accounts take up very little space on the server. As far as I know you can't hurt your existing account this way. (Knock wood.)
How to
When you're done, you're signed on exactly as if you had signed on with an email address, except you have signed on with WordPress.
Screen shots
The text was updated successfully, but these errors were encountered: