Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
#1635662: Undefined index: feature in features_get_info() has been fixed in dev but an error message that appears on module enable and cache clears really warrants a new release, I think.
Comments
Comment #1
hefox CreditAttribution: hefox commentedThe one that can create releases, mpotter, is busy as far as I can tell, and whether he deems it worth it to make a new report (making a new release for something that isn't breaking anything -- e.g. just a warning -- seems a bit unusual).
Putting this as a *critical* bug strikes me as totally inappropriate use (abuse) of issue fields.
Comment #2
joachim CreditAttribution: joachim commentedMaking a release takes about 5 minutes.
A lot of users are going to be confused by this, both site builders and site administrators. I really don't think this is much to ask.
Comment #3
hefox CreditAttribution: hefox commentedThis is not a bug nor is it critical. Please do not misuse issue status.
edit: My personal policy is not to use critical status unless I'm a maintainer or there's something like data loss happening due to the issue -- misusing it is one way to really step on toes.
edit 2: and thanks fago, task is much more appropriate type. I don't think much early in the morning u.u
Comment #4
fagoA new release would be nice, yep - but it's not a critical bug.
Comment #5
joachim CreditAttribution: joachim commentedWe're talking about a bug that was fixed on June 18, 2012 at 8:13pm. That's over a month ago.
If the maintainer(s) with the access to make a new release can't find 5 minutes to make a new release in over a month, then there is a meta-bug in the running of this project.
Comment #6
saltednutI feel where joachim is coming from but I also agree with hefox that tagging critical is borderline abuse. The error dump is definitely a deterrent for new users.
Comment #7
imp7 CreditAttribution: imp7 commented"borderline abuse" sounds a little harsh, this is just quality control under what is marked a "recommended release". What software have you ever used that throws errors at you when you download a stable version? if its a simple fix why not just spend the five minutes.
Anyways at least everything seems to be working, features is AWSOME for Drupal, I want it to impress people not worry them with unnecessary errors :)
Comment #8
saltednutPretty sure the word "abuse" was used in comments above before some edits happened? I was simply commenting that its borderline at best. w/e
Comment #9
imp7 CreditAttribution: imp7 commentedNo probs brantwynn I just think that this does harm to drupal's reputation for being stable and supported on such a widley used module.
Anyways I look forward to using a make files etc with stable releases and not getting this error blasting us :)
Comment #10
hefox CreditAttribution: hefox commentedAn RC is not considered a stable version, thus the reason why it's an RC.
Misusing priority and category to gain attention to a issue I defiantly consider abuse; I find it presumptuous and unnecessary. However. discussing proper use of issue status further here is also unnecessary.
I talked to mpotter on IRC and he plans to make that said stable from current dev when he has time.
Comment #11
joachim CreditAttribution: joachim commentedI wasn't asking for a stable, just a fresh RC.
> Misusing priority and category to gain attention to a issue I defiantly consider abuse; I find it presumptuous and unnecessary
I find leaving glaring bugs like this in the most recent point release to be a lack of respect for one's users and irresponsible maintainership.
Comment #12
hefox CreditAttribution: hefox commentedTo my understanding, the decision to make a stable is not influenced but this or the other issue, but by the lack of any truly critical bug reports.
Comment #13
mpotter CreditAttribution: mpotter commentedClosing this issue because it is not a productive use of the Issue queue. If you have issues with how a module is being maintained, contact the maintainer or volunteer to help. Hefox has basically said what needs to be said here. If you went into every module that didn't have "stable" (means non-RC, non-Beta, non-Alpha) releases that still had new committed patches not yet rolled into a new release you'd be posting on a LOT of modules. It is NOT something you post a new issue about.
Comment #14
joachim CreditAttribution: joachim commentedI appreciate that making a stable release is time-consuming. I wasn't asking for a stable, just a new RC: five minutes of a maintainer's time.
Really, it's to the benefit of the maintainer and the module to do this too: an error message like this on install will send most people scurrying back to the last-but-one release, and so you won't get as many users and testers and eyeballs on the current RC as you could have if you just roll a new one.
Comment #15
mattsmith3 CreditAttribution: mattsmith3 commentedhey all- just here to say the patch worked for me.
thanks for all the great work!