Utility-Image-Rebuild-module
This module is a small utility tool.
It can help you rebuild the image(s) information stored in the image field within certain content types.
The two common cases are:
- Image(s) were replaced manually on the server, such as cover.jpg from a small size to a larger size.
- Image(s) name(s) or path(s) were updated in the database and were replaced manually on the server. For example, from public://publication/1.jpg to public://article/01.jpg
In particular, the {file_managed.filesize} and the {file_managed.timestamp} columns will be incorrect after making these changes and the image dimension in the field_data_filename table will be incorrect as well.
This module will rebuild said information and then update them in database.
Installation
Installation is quite simple:
Enable the module from admin/modules or use Drush:
drush pm-enable utility_image_rebuild
Dependencies
The Utility Image Rebuild module is dependent on two Drupal 7 core modules:
- file
- image
You will be prompted to enable these modules if they are not already enabled.
Project page:
https://drupal.org/sandbox/joseph.zhao/2035347
Git repo:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/joseph.zhao/2035347.git utility_image_rebuild
Code base:
http://drupalcode.org/sandbox/joseph.zhao/2035347.git
Screenshot:
- https://drupal.org/files/project-images/QQ20130711-1.png
- https://drupal.org/files/project-images/Screen%20Shot%202013-07-05%20at%203.25.52%20PM.png
Reviews of other projects:
- https://drupal.org/node/2033339#comment-7614395
- https://drupal.org/node/2035305#comment-7617341
- https://drupal.org/node/2038287#comment-7634663
Second review list:
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | language_edits-2035383-16.patch | 4.18 KB | gabesullice |
Comments
Comment #0.0
pandaski commentedUpdate the project desc.
Comment #0.1
pandaski commentedRemove email from the desc.
Comment #0.2
pandaski commentedUpdate project desc.
Comment #0.3
pandaski commentedadd code base.
Comment #0.4
pandaski commentedUpdate project desc.
Comment #1
PA robot commentedProject 1: https://drupal.org/node/2034575
Project 2: https://drupal.org/node/2035383
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2.0
PA robot commentedUpdate the project desc.
Comment #2.1
pandaski commentedUpdate the project desc.
Comment #2.2
pandaski commentedUpdate project desc.
Comment #2.3
pandaski commentedUpdate the review of other project.
Comment #3
pandaski commentedWaiting for your review, many thanks.
Comment #4
feolius commentedHi!
From my not expert point of view code seems to be correct. The only strange thing, that I noticed, was in README file. You wrote that there are 3 common cases of using the module, but in you project page you point only two of them. And it seems that the case 2 and case 3 (2?) should be combined into one, i.e. user should replace files manually and also replace uris in database, right?
And another one suggestion (but maybe it is not necessary). Maybe you could also put error message in watchdog?
Comment #4.0
feolius commentedUpdate reviews of other projects.
Comment #5
pandaski commented@feolius many thanks for the review.
I've updated the README.txt, please feel free to let me know if sounds better now since English is my second language :)
And db_log is definitely a very nice suggestion, I will add this feature in the branch ASAP.
Comment #6
feolius commentedMuch better now:)
English my second language too.
Thanks!
Comment #6.0
feolius commentedUpdate the project desc
Comment #6.1
pandaski commentedAdd screenshot images
Comment #7
pandaski commented@feolius Many thanks mate, if found no major flaw, would you mind to give it a sign off?
Comment #8
feolius commented"give it a sign off" what does it mean?
Language problems. sorry:)
Comment #9
pandaski commented@feolius you can update the status to "reviewed & tested by the community" if found no major flaw. Many thanks.
As mentioned here:
Comment #10
feolius commentedSure, no problems
Comment #11
pandaski commentedThank you for the review mate! I sincerely appreciate it!
Comment #12
klausimanual review:
But otherwise this looks almost RTBC, knowing where to use check_plain() and where not is an application blocker. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #13
pandaski commented@klausi many thanks for the review and kindly advices.
The issues have been fixed now, and it is ready for the review.
Comment #13.0
pandaski commentedAdd screenshot images link
Comment #13.1
pandaski commentedSecond review list
Comment #14
pandaski commentedRemove review bonus tag until another 3 reviews
Comment #14.0
pandaski commentedSecond review list.
Comment #15
pandaski commentedThank you for the review folks, learnt a a lot. I sincerely appreciate it!
Comment #16
gabesulliceThis is an interesting module. I don't see any errors in formatting or on pareview.sh, I'm not expert, but i don't see any blockers in the code either. I went ahead and made some language changes as a native English speaker (Good job though! There wasn't anything egregious :) ) and broke the dependencies into their own section in the README. These are all in the patch, it was easier than writing them all out here. I made no code changes.
None of these things are a blocker though so I'm not moving this back to needs work.
I'll let someone more experienced check the code changes in #12.
Comment #16.0
gabesulliceUpdate the review second round.
Comment #17
pandaski commented@gabesullice very appreciated your kindly language patch file, and I have applied the patch in the latest release.
Drupal is with such a nice community, and I am encouraged to contribute more just like you. :)
Comment #18
klausiLooks RTBC to me now! Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Assigning to stBorchert as he might have time to take a final look at this.
Comment #19
stborchertThanks for your contribution, Joseph!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #20
pandaski commentedMany thanks @klausi and @stBorchert
I will keep in minds all the thing I learnt here especially sharing the knowledge and be responsible.
Comment #21.0
(not verified) commentedUpdate project desc.