Notice: Undefined index: version_major in update_calculate_project_update_status() (line 556 of /sitepath/public_html/modules/up

i can confirm this with a 7.10 version.

Confirmed with an update from 7.10 to 7.12

A whole bunch... see attached file.

I've got this too :(

Fresh install 7.12
Notice: Undefined index: version_major în update_calculate_project_update_status() (linia 556 din /chroot/home/vmgrup/vreaumateriale.ro/html/modules/update/update.compare.inc).

same issue.

duplicate of http://drupal.org/node/1343768

It may be a duplicate in the sense that drupal 8 also has this error, but this issue was open for drupal 7.12.. Maybe I am not the more indicated to do so, but I am re-opening it since there seems to be no solution for drupal 7.12 yet. Or the duplicated issue needs to be brought back to version 7.12 as it looks as originally started as such?

Bugs are fixed in the current dev version (Drupal 8) first and then back-ported to Drupal 7. The backporting usually does not take long after a fix has been committed to Drupal 8. Efforts are put into one issue so we don't have the discussion and patches fragmented in many issues. So joining the other issue at #1343768: make update_calculate_project_update_status() work nicely with HEAD releases would be the best way to help get this bug fixed :)

Postponed would be the more appropriate status.

based on http://drupal.org/node/156119

postponed = "May mean either 1) that the issue is valid and should be fixed, but other related issues (blockers) need to be dealt with first, or 2) that the issue is removed from current active work but the intent remains to return to it. In the first case, please tag the issue "blocked" and say what issue(s) it's blocked on in a comment."

Because http://drupal.org/node/1343768 was filed first, it makes this issue a duplicate. Further reports of this issue should be made in http://drupal.org/node/1343768 after testing the available patch. Since that issue also contains a patch and this one does not, I'm remarking this as a duplicate of http://drupal.org/node/1343768

I am aware of these defenitions and that't the reason I have changed the status. If you close it, you state that it won't be fixed for the D7 version. Obviously that's the wrong statement here.

As in #9 described, D7 will be fixed later after the D8 is done by backporting it. So currently there won't be any work on it but it will be taken care of later. That's what you have cited above with "postponed". You can still refer to http://drupal.org/node/1343768 as you said, that's not a problem.

That's not the way I've understood issues to work. Duplicate issues are closed in favor of the first one filed or the one in which there is a patch to test. A link to the original issue is placed in the duplicate issue to help users find the discussion or patch to test. I've never seen nor been told that marking a dupe issue as a dupe issue means it "won't be fixed" else, to my understanding it would be marked "won't fix".

If the above has changed, I'm unaware of it. If my understanding has been incorrect over the years, then this is the first I'm hearing about it.

I fully agree with you in cases of duplicates. But I don't see that this is a duplcate. I guess we have a different understanding of what a duplcate is.

The point is that fixing D8 doesn't make this issue obsolete, it still has to be applied sepatately for D7 even if it is "just" a backport. This submission is the only one for D7, so my understanding would be to not close it before it isn't fixed. It would indicate that there would be no further activities for this version. Postpone it and refer to the D8 issue which is intended to be backported as the plan to fix it. Makes a lot more sense to me.

I would agree. The issue might be related to both, but doesn't indicate that it is backported.

So, any status on a patch or such?

According to another post I read by (maximilianuhl) this problem can be solved as he states below:

"I just had this error with the taxonomy_menu module. I am working with version 7.x-1.x-dev of this module, but in the file taxonomy_menu.info the line added by the drupal.org packaging script says version = "7.x-1.2+28-dev". Changing this line to version = "7.x-1.x-dev" makes the error disappear. So maybe its an error of the packaging script and not of the update module."

That dev version denotation is a nice piece of clarification, IMO. Perhaps a validation (file format) error.
I too have the dev version of Taxonomy Menu installed; so perhaps a source of my errors, as well.

This worked with me too. Like a charm!

Thanks.

Solution in #16 worked for me. Thanks

Solution in #16 worked for me too. Thanks

#16 isn't a solution. It's a work-around, preventing Taxonomy Menu from doing any update checking until the issue is solved.

Confirm #16 workaround worked for me.

Agreed #16 isn't a solution, but got rid of the error for me as well.