Eventually, you can login into my website using your Facebook, Twitter or GitHub account. Also, you can login using you Google account, what was already announced in a separate news.
My version of the plugin requires the OAuth provider to provide the e-mail address of the user, who attempts to log in. So, if the e-mail address is not available you will get an error.
Here are the possible reasons (the ones, that I’m aware of):
Here are some steps, that I took to configure the plugin:
To make Twitter send me the e-mail address of the user, that attempts to login, I had to write Privacy policy and Terms of use for my website. These pages are required by Twitter for the app (my website, in this case), that wants to have access to the user’s e-mail address.
But, this did not help… Additionally, the app should explicitly ask for the e-mail in its request and the version of the omniauth-twitter gem, which is used by the official plugin, does not do this. So, I had to change the plugin to require omniauth-twitter 1.2.1 (the version, which starts to do this) or above.
The original plugin crashed, when I tried to login into my website using my Facebook account. This appeared to be caused by a bug in omniauth-facebook, which was fixed in version 3.0.0 of this gem. So, I had to modify the plugin to require this version or above too.
GitHub appeared to be the only OAuth provider, that worked fine without any modification in the plugin.
<nickname>_<uid>
).
Previously, Google used the OpenID protocol to allow third-party websites (like mine) to authenticate users using their Google accounts. But then, eventually Google switched to OpenID Connect. OpenID (without Connect) was natively supported by Redmine and worked fine with Google (with the help of my OpenID Fix plugin). OpenID Connect, on the contrary, is not natively supported by Redmine and needs a third-party plugin.
I installed the Redmine Omniauth Google plugin for Redmine, that was (initially) created by Dmitry Kovalenok from Twinslash Ltd. This plugin adds support for Google’s OpenID Connect to Redmine. Also, I had to modify the plugin a little to make it work under Redmine 2.5.xd, which is used by my website.
I don’t see, where it’s needed… I used it for Google authentication, but do not need it for this any longer. Also, I’m not sure, if it helped for other OpenID providers (I guess, some of them still use OpenID). So, I’m about to abandon it.
Let me know, if you still need it, though.
OpenID Connect is supported not only by Google, but also by, e.g., Facebook, Twitter and GitHub. So, I’m looking to allow you to authenticate on my website using your accounts on these websites as well. Looks like the TweetBook plugin for Redmine, that was created by Sandeep Kumar, is what I need (but I’m not sure, if it supports Redmine 2.5.xd).
]]>From time to time being away from my computer I was trying to check issues, reread news, Wiki pages and the similar on my old Samsung bada-powered smartphone (well, I use the cell phone just for calls, mostly). And it was an awful experience! This way I became curious about making my website responsive (but, certainly, first I needed to learn, what does “responsive” mean)…
Currently, I have the blog (this one), which runs on WordPress and still is much based on Redmine… Thus, my blog uses the Redword theme, which in turn uses the Red-Andy theme for Redmine. So, certainly I decided to make my Red-Andy theme responsive. But it appeared to be not easy…
The problem around Redmine themes is that they are pure CSS customizations. Having figured out, that for a responsive website I needed the viewport META, I gave up (as META tags can’t be added using just CSS). But later, thanks to Xander Dumaine, I found, that the viewport META tag can be added using JavaScript and Redmine themes are able to include custom JavaScript code. So I got back to experimenting with my site, its Red-Andy theme and my mobile phone. These experiments (i.e., improvements, customizations and so on), in fact, last till today and will, probably, last some more time… Anyway, the site now works fine on mobile devices – is responsive and usable (but some more improvements are to be or can be done)! So this article is a news/announcement for this! In other words, you can access this site from your smartphones now!
Also, this article is an announcement of the upcoming Red-Andy theme release, which will include responsiveness and, therefore, mobile support. This way the Red-Andy theme will become, as far as I know, the first and only responsive Redmine theme. Certainly, there were other tries like the Mobile theme from Xander Dumaine, but they were incomplete and/or unmaintained (at least accordingly to the information I have – I personally have not tried the Xander’s theme).
And, finally, here are some screenshots of my website taken on my old Samsung bada smartphone:
]]>For this reason I devoted a whole page (161) to using projects as categories in my book Mastering Redmine.
I got the will to implement true project categories for Redmine a long time ago (see #1777) and, finally, I came up with this solution – the Project Sections plugin.
Why “section” and not “category”? First, I used to implement a proprietary categories plugin for Kayako and did not want to use the same name (as these plugins are too different). Second, assuming, that some day Redmine guys would implement true project categories in the Redmine core, I wanted to avoid conflicts. And the third, sections really resemble the sections (see the project list)!
From many points of view a section is not just a usual project category… I prefer thinking, that I implemented it in a Redmine way. Anyway it’s quite specific.
Thus, sections help to describe projects better, as they usually get prepended to project names. For example, instead of just “WordMine” you get, e.g., “WordPress » Plugin › WordMine”. As long as sections, unlike projects, do not require you to spent time for configuring them, you can manage them much faster and more effectively.
Also sections allow splitting the project list into sections grouping projects by whatever you like. Each section gets its own page and includes links to parent and child sections as well as to other system sections. A section page lists projects of the section and all its subsections this way providing the complete project list and smaller collections simultaneously.
Additionally, sections affect the primary project URL (the one, which points to the overview page) by prepending section identifiers to the project one. So in result you get an URL, which looks like:
/project/top-section/subsection/project-identifier
But this is not only a more descriptive URL, but also a reliable source of information for search engines.
Generally, project sections were implemented in the way, it should be very easy to migrate from project-based categories to section-based categories.
This is the only plugin, which I release without first using it on my website or other production Redmine installation. That’s because currently my site is running Redmine 1.0 and the minimal supported Redmine version for the plugin is 1.4 (it required many changes to support Redmine 1.0). Anyway right now I’m working on moving my site to Redmine 1.4 soon, and to install this plugin afterwards.
]]>Therefore, right after putting the plugin on my website I sent the request to Twitter for approving my domain (using this page). Usually I deploy the plugin to the site in some time before I release it (to test, how it works in the real environment), so I hoped to get approved before the release. But Twitter guys appeared to be slow in this – I released the fixed 0.2.1 and the domain was not approved yet. Eventually, I stopped expecting the approvement to be done… But today, finally, I got an email notifying, that my domain had been approved!
So now, for the case, if you were wondering, what exactly this feature does, you can check this using my website!
For example, check this tweet, which links to this news item:
By default, the Twitter “summary” card won’t be shown and you will need to click on the “View summary” link to see it. The new block, which will appear after you do this, is the Twitter card.
Alternatively you can add the tweet:
Want to know, what does the Meta plugin for #Redmine and @ChiliProject do? Check the View summary link on this tweet! http://projects.andriylesyuk.com/news/64
To check the Twitter card in your Twitter account (and to promote the Meta plugin ).
The Twitter Cards support was not yet available in the Meta plugin, when I was writing the Mastering Redmine book (and was not even planned). And this is sad, as this feature greatly supplements the plugin. Anyway, you can find many other interesting things in the book. Check the Mastering Redmine project, if you have read the book or are interesting in reading it.
You can subscribe to further news regarding the Meta plugin using the Subscription form on the sidebar.
]]>I’m quite sure, that this book and this project will bring new users to my website. I hope, that such users will read this particular news, where I’m going to describe, what you can find on the website and in this particular project…
This website is built on… Redmine! On this website, at the moment of writing these words, I share my Redmine plugins mostly. None of these plugins have a special usage in any organization, I work in. Well, some of them are used on the Kayako Forge (and I work in Kayako)… But, what I’m trying to tell is that this work is totally volunteer (and was done before I entered Kayako). And one of the main goals of this website is sharing – sharing the code, ideas, views and so on. This way anything this website uses is available for download and free usage! Thus, the theme of the website is available in the Red-Andy project, Redmine customizations are available in the Projects project, and customizations for this particular project (e.g., how did I add the “Table of contents” and “Sample chapter” tabs) are available under the “Repository” tab of this project.
That’s was a short story about the website. Now let’s talk about this project:
The book has the official book page on the publisher’s site, where you can leave a review, submit errata and so on. All this will go to the publisher and the appropriate requests will be forwarded to me. So anyway this will be me, with who you will discuss Redmine issues or technical details from the book. Therefore, to establish a direct channel between you, as readers, and me, as the author, I created this project. It is aimed to be the first source of the technical information related to the book.
So here you will be able:
For quick news regarding the book (not such huge ones as this one) you can also:
I’m sorry! Really!.. Recently many events occured in my life so I could not update them in time. Of course, I plan to and will do my best to do this a.s.a.p. I hope for your patience.
I will begin with Redmine 1.4, then will work on Redmine 2.0 and only then will continue with ChiliProject…
Why ChiliProject is the last? Well… I have a feeling I need to go this way. You can influence the order by letting me know.
When you should expect updates? Can’t give any ETA!
P.S. Also I would not recommend anyone to upgrade to Redmine 2.0 right now… It changes much in API used by plugins! So you need to give more time to plugin authors to update their plugins (including but not limited to me)! At least be sure to check if plugins are compatible with Redmine 2.0 before upgrading!
]]>