The below list contains the issues the maintainers have identified to block the release of a new version. The current version is 1.5 years old and a lot has happened both with the module itself and the services it covers.

The below list origins from comment #3:

Let's start with the "major" bug reports:

Adding a bit of normal bug reports with something to test:

As well as some Feature Requests with patches:

I think everything is ordered by priority (or quite), so it's a start. Thanks for your help!

Original issue post (@tsvenson)
It would be great if a new recommended release could be made of this excellent module. Quite a few commits have been made since the last, a year and a half ago. Including many changes to both existing and new services as well as important and useful new features.

I put this as a major mainly because using a dev version on live sites makes it more problematic and risky to run. Not due to that it is dev, but mostly because of that updating using either the built in Update Manager or Drush includes a huge risk of reverting to the recommended, and older, version.

Comments

simon georges’s picture

A new version should indeed be released shortly (meaning "when we have the time..."). In the meantine, feel free to help review existing patches / patch open bug reports, so we can commit them faster and effectively release something proper and stable ;-)

tsvenson’s picture

I'll do what I can. Would help a lot of there is a list of issues that blocks a new release. I'm not a skilled developer, but fully capable of doing quite advanced testing. However without such list it is a bit difficult to identify the right issues/patches to test. My time is quite limited as well unfortunately.

tsvenson’s picture

Title: New version planned soon as current is 1.5 years old? » [meta] Roadmap to new 7.x release

Thanks @Simon Georges for so quickly putting together a list. I changed the issue title to better correspond with the content and will also update the summary to contain your list so its easier to follow.

I plan to set aside some time within the coming week to go over the issues I am capable to.

tsvenson’s picture

@Simon Georges, just to let you know. I've been decked with flu the last 4-5 days and just now getting back to some form of normality. Meaning I haven't had a chance to look into any of the issues yet. I'm going to take a first round over the weekend though.

simon georges’s picture

@tsvenson, thanks for the feedback. I'm totally swamp with work for the following weeks, I should have more available time after.

TheCrow’s picture

TheCrow’s picture

Issue summary: View changes

Moved the issue list from comment #3 to here so easier to follow and work on.

TheCrow’s picture

#980938: Service links on a front node will be the latest to review and commit together to some detail in the documentation before the 2.2, hopefully it will happen this week.

[Edit]
I had to wait for this #1981474: Error on View gallery page when I add [node:field_image] to Pinterest "media parameter" then had to fix this too #1655428: PHP notices at admin/settings/service_links/services from form elements without #parents, after a code clean session and some fixes in the documentation files i will push the lastest commits and the 2.2 will be ready!

simon georges’s picture

@TheCrow: Wow, well done, and thanks for your huge work these last weeks!

TheCrow’s picture

You're welcome Simon,
i just committed the latest fixes and cleaned up some junk code, in 2 days i would like to tag the new release if no issues pop up.

TheCrow’s picture

Status: Active » Fixed

2.2 officially released, should be available in few hours!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Adding one patch per theCrow's suggestion in #7.