Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Jan 2012 at 05:01 UTC
Updated:
27 Jul 2012 at 16:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
klausiYou need to set the status to "needs review" if you want to get a review.
Get a review bonus and we will come back to your application sooner.
Comment #2
hamburgers commentedComment #2.0
hamburgers commentedadded git clone line to description
Comment #3
alex dicianu commentedHi,
I just launched an automatic review with this tool http://ventral.org/pareview. I've attached the report. It seems you have some code formatting issues. You should also check the coder module. I've done a quick test with it and it seems he has also found some issues.
You can also check the drupal coding standards. Generally it's a very good idea that people should write code the same way for a given application.
Looking into the code, in the file html.tpl.php, I saw:
I think you should be more explicit with the doctype and html declaration like you've done in the maintenance page. Here is an example:
In the file contact-site-form.tpl.php.
I think it would be better to just print
print drupal_render($form);instead of the 3 lines. This would print the rest of the form elements and you won't have to worry about printing them separately.Comment #4
hamburgers commentedThanks dicix!
I have gone through and cleaned up the code based on the recommendations of the coder module.
all files have been emptied from master except README.txt
I have also done some cleanup based on your suggestions
Comment #5
hamburgers commentedI have made some improvements to the theme with the addition of a left sidebar and support for larger monitors. CSS has also been improved. All code has been cleaned up to comply with Drupal coding standards. Coder module seems to come back clean and pareview comes back mostly clean with the exception of numerous occurrences of the following errors:
269 | ERROR | Blank lines are not allowed between class names
270 | ERROR | No style definition found on line; check for missing colon
Both of these errors are because of the media queries in the CSS file.
Comment #6
klausiSounds like false positives in drupalcs, can you open a bug report in the drupalcs issue queue about the media queries?
Comment #7
dudenhofer commentedHi hamburgers, I ran your code through the review again and it flagged your CSS spacing.
http://ventral.org/pareview/httpgitdrupalorgsandboxhamburgers1417228git-...
Check out the "properties" section here: http://drupal.org/node/302199
I also noticed some spacing issues in your template files, particularly on the page.tpl.php and html.tpl.php there are a lot of tab indents instead of 2 spaced indents
http://drupal.org/node/318#indenting
Comment #8
dudenhofer commentedupdating status
Comment #9
hamburgers commentedspacing issues in CSS and page.tpl.php have been resolved
Comment #10
hamburgers commentedthank you for your help dudenhofer
Comment #11
dudenhofer commentedHi Hamburgers,
You might take a look at your fieldsets, particularly around the textareas with input format filters. The input formats options are pushed off to the side.
I also noticed that your aside classes "left" and "right" aren't wrapped in any sort of if statements, so there is always an aside container present. You might use a statement like if($page['left']) to wrap around those (similar to how the $title is handled in your page.tpl.php)
Lastly, multiple selectors should each be on a single line, look at lines 8, 280, 303, 309, and 329 of your style.css.
Comment #12
hamburgers commentedI have made some changes related to dudenhofer's suggestions and some other minor CSS tweaks.
Comment #13
nitvirus commentedunable to clone the branch as it is asking for "hamburgers@git.drupal.org's password: "
also tried cloning the master but seems you have removed the file from it.
Comment #13.0
nitvirus commentededited git clone line to replace master with proper branch
Comment #14
patrickd commenteduse:
git clone --branch 7.x-1.x git.drupal.org:sandbox/hamburgers/1417228.git adapticComment #15
scot.hubbard commentedHi Hamburgers,
There still seems to be quite a few coding standards issues getting picked up (see http://ventral.org/pareview/httpgitdrupalorgsandboxhamburgers1417228git-...).
Looking at your code manually, I would say there are some minor issues regarding indentation (in some places there seems to be too much indentation).
In your template.php I would change the comment block from:
to
Other than that, it seems to work well.
Comment #16
hamburgers commentedI have gone through the code and cleaned it up based on some suggestions from scot.hubbard.
I have also made some changes to the look of the theme to make it a little nicer out of the box.
DCS is finding issues with two files, both min.js files. I have reported this as a bug with the Drupal Code Sniffer module. Aside from this DCS and Coder module are coming back clean.
Comment #17
hamburgers commentedComment #18
igoen commentedJust suggestion.
I think you could add some css to fix this one, see screenshots.
Css could be added:
Comment #18.0
igoen commentedcorrect git url
Comment #19
misc commentedIt is almost RTBC for me - but one important issue - it seems that we fonts included are not GPL, is that correct? If so, they can not be included.
Comment #20
hamburgers commentedThanks MiSc, I'm not certain about the font license, doesn't seem to be GPL. I've removed the font from the theme and made some edits to the CSS to compensate.
thanks again.
Comment #21
hamburgers commentedComment #21.0
hamburgers commentedcorrected git link
Comment #22
hamburgers commentedadding reviews bonus tag.
Comment #23
klausiLooks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #24
klausiNo objections in more than a week, so ...
Thanks for your contribution, hamburgers!
I updated your account to let you 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 get 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 #25.0
(not verified) commentedadding links to reviewed projects