I would like to offer some help in maintaining the module. I am currently using the module for a project and would like to get some patches in. I have created a fork in a sandbox to get going while awaiting approval.

Comments

wizonesolutions’s picture

Status: Active » Postponed (maintainer needs more info)

Which patches? I can commit them if they are tested.

pfrenssen’s picture

Working on them :D

pfrenssen’s picture

After working with the module for an evening I'm getting second doubts about maintaining this :-/

Anyway I have committed some cleanup patches to the sandbox + a fix for #1708610: Export content type visibility settings for blocks.

wizonesolutions’s picture

OK - also if others test the patch and give feedback I'll be more comfortable committing it. I will check into things Friday.

I will also create official releases so that I can commit patches with a bit less concern. It's about time for an official release even if there are problems, and even though that'll probably increase the installation count :( - only on Features Extra would I be sad about that!

wizonesolutions’s picture

Assigned: Unassigned » wizonesolutions
Status: Postponed (maintainer needs more info) » Active
pfrenssen’s picture

Ok I have finished my work on Features Extra in my sandbox. I have also reviewed and applied some patches from the queue that were needed to stabilize the module for the project I am currently working on (which has 70 blocks and a test suite of 7000+ tests).

It would be nice if you could consider merging in the sandbox in the main project.

vinmassaro’s picture

Status: Active » Needs review

Would like to see pfrenssen's work merged in. Exported blocks only work for me from his sandbox version. Thanks.

pfrenssen’s picture

I am running my sandbox version in production on a fairly large website since September 6. It is performing well. I will be providing support for this site for a number of months and would still like to be promoted to co-maintainer so I can easily commit any fixes I might need to do.

I have no actual long term plans for Features Extra (it will become obsolete with the CMI in Drupal 8 anyway) but at this moment there is no real alternative. It is not pretty and has no future, but I would love to get this code out as a beta version so people can start exporting their blocks in features.

vinmassaro’s picture

+1, we are using your sandbox code to stand up block configurations on new installs in our university deployment of Drupal 7 and it has worked perfectly so far.

wizonesolutions’s picture

pfrenssen: I've hooked you up now as a full maintainer. Also going to merge your branch tonight because I am probably going to need Features Extra in the distribution I'm putting together.

pfrenssen’s picture

Status: Needs review » Fixed

That's awesome, thanks Kevin!

wizonesolutions’s picture

No chance to merge in the branch yet. If you can do that that'd be great. Rebase if you can, and preferably publish a new release series unless nothing has changed functionally, in which case please make an official release. It's about time since this module seems to be here to stay for a while, albeit against my greatest hopes.

pfrenssen’s picture

I'll make work of this soon, I'll take it up in my free time this weekend.

There is some new functionality, but I have provided backwards compatibility so it should normally work.

Perhaps we could release an alpha version first, then go through the issue queue and mark important issues that should be fixed before releasing a beta.

wizonesolutions’s picture

Yeah, that's fine. Any kind of official release would be better than the status quo.

pfrenssen’s picture

I have released 7.x-1.0-alpha1, it will become available as a download soon.

Status: Fixed » Closed (fixed)

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