Inline images to be posted to Drupal.org project pages need to option/toggle to hide them. If project creator/maintainer want to display inline image into project else where then he/she can do it by attaching image through file upload module and place inline image through img tag. In this case image will display twice. It's display by default under screenshot image place and with img tag. So we need to toggle check box to make it optional whether it display by default or not.
Please review attached images to understand it clearly.
| Comment | File | Size | Author |
|---|---|---|---|
| drupal_org_project_image_issue.png | 470.97 KB | itapplication | |
| drupal_org_node_127049_edit_toggle.jpg | 102.34 KB | itapplication |
Comments
Comment #1
itapplication commentedAfter waiting for more than 3 weeks making it normal to major.
Comment #2
dwwIf you query for all the feature requests for Drupal.org that are older than 3 weeks, you'll understand that this isn't "major". Especially since there are at least two work-arounds to this problem:
A) Don't also try to place the image inline manually -- let it appear where it does.
B) Attach your image(s) to an issue in your project's queue or something and then place them inline on the project page (if you must).
Also, the way we're handling images for project nodes is changing for the D7 upgrade, and this will probably be fixed by that.
Comment #3
itapplication commentedThanks for your help and info.
It will better to wait for D.O upgrade to D7.
Comment #4
klonos;)
Comment #5
itapplication commented@klonos as per dww info it won't fix at least with current D.O. version. Entire site is under process of upgrading for D7. At that time it will be fix.
Changing Component: from "Other" to "redesign.drupal.org"(may be "updates.drupal.org" is suitable. But it's update not upgrade.)
@dww, @klonos I am thinking to redirect this issue from Project:
"Drupal.org infrastructure" to "Drupal.org customizations" or "Drupal.org site upgrade QA" or "Upgrade Status" or keep it current issue queue. Please advice.
Comment #6
dwwupdates.drupal.org is the server that the Update Manager in core (formerly Update Status) queries for info about available releases of Drupal.org projects, so not that.
redesign.drupal.org is deprecated and we should probably just remove that as an option.
Upgrade Status is a separate contrib module that has nothing to do with the Drupal.org D7 upgrade, so not that, either.
However, it's true this isn't really an infrastructure issue. Drupal.org customizations is fine, I suppose.
If you wanted to verify that this is working as expected on https://git7site.devdrupal.org then I think we could safely just call this "closed (works as designed)" and be done with it.
Thanks for asking!
-Derek
Comment #7
itapplication commentedHi Derek,
Thanks for advice and detail info.
I think instead of closing issue we should keep it open for Drupal 7 upgrade team until we get this essential feature on upgraded Drupal.org.
-Shiv.
Comment #8
dwwI'm on the upgrade team. ;) I'm saying that you can already see if this feature is working how we want in the D7 version of the site. If so, there's no real reason to keep this issue open. It'll be fixed ("by design") whenever the D7 upgrade goes live. See what I mean? We're just marking things fixed once they're verified to work on the D7 site, instead of leaving everything open until they actually go live.
Thanks,
-Derek
Comment #9
itapplication commentedOK. I agree with you. But please guide me how I can test it.
I guess link you provided into #6 post is for test the feature but it ask authentication. I try to use my Drupal.org user id and password without getting success.
-Shiv
Comment #10
klonosUse drupal/drupal for both username/password to authenticate access to the test site. Once you're allowed to the site, then you can use your actual d.o username and password to log in ;)
PS: I'll give this a go too soon as I can and report back.Nah, I just realized that I need project creation rights to actually test this :/
Comment #11
itapplication commentedI could not test. I bump on Error "The website encountered an unexpected error. Please try again later. " ...Uncaught exception thrown in shutdown function.
:.(
Comment #12
tvn commentedThat website is being automatically rebuild every day. The process takes about 2 hours and git7site is not accessible during that time, showing all kinds of errors. Please try again in an hour or so.
Comment #13
itapplication commentedThanks for info. I successfully test the functionality which I expect.
Now I am eagerly waiting for Drupal.org upgrade for D 7. Is there any info available regarding to milestone (final release) of D.O.upgrade for D7?
Thanks all of you.
This is why I love Drupal community.
-Shiv.
Comment #14
dwwExcellent! Sorry for the confusion on how to test, I could have been more explicit.
Yes, we're all eagerly awaiting the d.o D7 upgrade. ;)
Weekly reports are going out over the Drupal Association blog (e.g. https://association.drupal.org/node/18268) which is published to Planet Drupal.
Thanks for testing, and glad this is already working as expected!
Cheers,
-Derek
Comment #14.0
dww...typos ;)
Comment #15
mgiffordReferenced from:
https://drupal.org/node/997024