I am successfully using the current 7.x-1.x-dev snapshot on a production site for some 3 weeks now. I had to use the dev because it fixes #1097684: Profile tokens are not available directly after adding/registering a user.

Since the current release (7.x-1.3) is already 1 1/4 years old, I think rolling out a new release (7.x-1.4) would be useful.

Thanks.

Comments

Spleshka’s picture

I agree, but we need to commit more features/fixes before new release is created. So I need to find a bit time and process some issues.

roball’s picture

Thanks for the status update Spleshka!

Spleshka’s picture

Welcome :) Btw, if you see some patches that might be commited - I would appreciate any movements there.

roball’s picture

I noted that you have committed a patch to fix #1593230: Restrict profile2 type per roles. Which other issues do you think should be solved before rolling out a new release?

Spleshka’s picture

Good question. At least I need to review RTBC issues, then I'll check if there are some issues with major priority that really have to be solved asap.

imclean’s picture

The issue mentioned in #4 alone would be worth a new release.

The projet page states:

Profile2 allows for creating multiple profile types, which may be assigned to roles via permissions (e.g. a general profile + a customer profile)

This flexibility simply isn't possible unless the dev version is used, which took me longer than it probably should have to work out.

antiorario’s picture

How soon is ASAP? Do you guys need help maintaining the module? I'm offering.

joachim’s picture

The most recently active maintainer is Spleshka, but his last commit is 8 months ago. It might be a good idea for someone to get in touch with him and ask whether he still has time to work on this module.

Regardless of whether Spleshka is still active or not, having new co-maintainers on board is a good idea, as the other 3 maintainers (me included) are definitely no longer active here! We should start an issue for people to request comaintainership, and then the usual procedure is that people should post a number of patches to the issue queue & do patch reviews as well. I'm happy to help with the process of looking at applicants' patches.

kopeboy’s picture

Priority: Normal » Major

Please provide a new stable release, the number of committed fixes and new functionalities in the dev version is ridiculous!! It's 2 years now..

A stable version is also much easier to maintain for a site builder..

joachim’s picture

> It might be a good idea for someone to get in touch with him and ask whether he still has time to work on this module.

Did anyone do this?

> Please provide a new stable release, the number of committed fixes and new functionalities in the dev version is ridiculous!! It's 2 years now..

I agree completely! However, I've not been following development here at all for over 2 years. So I have no idea whether the current -dev is reasonably stable or not... is anyone running -dev? Can they comment to give me an idea of what it's like and whether it's suitable for releae?

rcodina’s picture

I use dev version in two production sites (7.x-1.3+20-dev) No problems so far.

Note: I'm also using the module with patch profile2_inline_entity_form-2449913-10.patch

ikeigenwijs’s picture

still needs a new maintainer

MustangGB’s picture

Would be nice to have a release with at least the patches that have already been committed in the past 5 years.

RickJ’s picture

I'd be happy to be a maintainer on this project. One of my sites is pretty critically dependent on it, and I've been happily using the latest dev release plus a couple of patches with no problems.

The patches I would want to commit are #2683917: Profile 2 types restricted by role, show for admin users and #2845725: Profile2 objects don't return useful label values.

joachim’s picture

> I'd be happy to be a maintainer on this project

Great!

Can you follow the standard steps for applying please? There should be a docs page somewhere about it, roughly, it's: file an issue with the request, then contact the maintainer. You can consider me contacted ;) but please also contact Spleshka, as I wrote above:

> The most recently active maintainer is Spleshka, but his last commit is 8 months ago. It might be a good idea for someone to get in touch with him and ask whether he still has time to work on this module.

RickJ’s picture

Status: Active » Fixed

7.x-1.4 now built and available since yesterday!

The dev build contains 3 further RTBC patches.

Enjoy!

Status: Fixed » Closed (fixed)

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