GD Library checked twice (a.k.a. merge with core GD status)

I'm noticing the same thing. GD Library is checked twice.

I am experiencing the same issue where GD library is listed twice on the Status report page.
This is a new 6.13 install and I wonder if this is something to worry about?

Yup me too. I'm having an amazing amount of grief with imagecache not working so I'm looking at every conceivable possibility. I've followed every step I've found so far and this double listing for GD library is about the only possible thing I can see that might cause a problem.

I'm concerned that it might be messing imagecache up, I'm not sure but ANY evidence of flakeyness is not a good thing - Anyone found a way around this?

You need to describe in more detail than "imagecache not working".

Although GD library is listed twice on the Status report page, I am not experiencing any problems with ImageCache at all.

i don't think it's totally accurate to say it's double listed. one of them is from core and one is from imageapi. if gd is enabled it's used to warn about insufficient memory and other conditions that might cause the library to not work as expected. perhaps we just need to clarify the labeling.

@drewish... that sounds like a good solution. When might that be done?

I know it's not a *real* problem (not functionally at any rate) but it does seem to be causing more than a few people to go searching for the solution to a *perceived* problem - which is, in fact, a waste of time.

As not to waste Andrew's time on something trivial as this, a short comment on the project page would be sufficient for now. 8-)

Hmmm... wouldn't it take the same amount of time (or perhaps even more) to add a comment on the project page rather than just changing the label as he suggested?

I understand that he probably has better things to do than make such a trivial change - but that's exactly my point... we *all* have better things to do than go searching for a problem that isn't really a problem. We only see a few comments left here in this thread, but that doesn't tell us how many others (tens?... hundreds?) have wasted *their* valuable time on this. Compare that to one person's time to make a small quick change.

You are right, changing label does not take much time and I bet that the change has been made in dev already. However, there are other issues that need to be resolved before the next version is released.

Same thing here too.
Any answers?

I am seeing this in Drupal 6.16 and ImageAPI GD2 6.x-1.8 and it looks like an error to have two identical status checks on the status page.

The status report is there to give admins confidence that their installation is correct and information to help them correct errors. The current situation erodes that confidence.

Lower the priority of the issue if it is trivial, that's what it's there for. Just 2 cents.

same here... subscribing

The label is still broken in 6.17. Closing in on a year now.

yep! *not* fixed in latest 6.x-1.x-dev (2010-Jul-11) either as guessed in #9.

I think that changing the label to something more distinguishing/meaningful is a nice temporary measure, but the real solution would be to eventually merge any status message with core status.

Subscribe, same problem. What is going on?

subscribe

...can we have an update on this one from the maintainer(s) please?

I'm really not seeing this as a big deal. If you have ImageAPI enabled with no toolkits it complains that you need to enable one. That's a good thing.

If you have Drupal's Color module and ImageAPI GD module enabled you'll see two messages. ImageAPI GD does additional checks that Color does not need because it uses additional functionality. I've got no idea why that would concern people but to make everyone happy here's a patch that doesn't stick the check that duplicates color module's check.

Went ahead and committed the attached patch.

Thanx again ;)

Yay, thanks - confirmed that it only has one line now on admin/reports/status for the GD Library. Really appreciate this, attention to little details can make a big difference.

I too can confirm that the fix works for me

@Andrew, #18:

I'm really not seeing this as a big deal...

...well see? Big a deal or not, you already have three happy customers ;)