Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Apr 2015 at 10:37 UTC
Updated:
2 Jul 2015 at 07:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxsumitkumar2467223git
We 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
jaskaran.nagra commentedPA Review Error:
FILE: /var/www/drupal-7-pareview/pareview_temp/js/custom.js
----------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------
1 | ERROR | Missing file doc comment
----------------------------------------------------------------------
Comment #3
jaskaran.nagra commentedAlso, can you please copy the git clone command for manual review.
Comment #4
jaskaran.nagra commentedJust another quick one. Please consider using Drupal behaviours in custom.js
Comment #5
Sumit kumar commentedPA Review Error is Resolve
Comment #6
Sumit kumar commentedComment #7
Sumit kumar commentedComment #8
Sumit kumar commentedComment #9
Sumit kumar commentedComment #10
Sumit kumar commentedComment #11
narendrarHi Sumit,
Thanks for the contribution.
I checked your theme and found some initial issues.
1. When search is enabled for site, main menu disappears (hidden under search box).
2. When main menu button is clicked, it expands. But it does not hide when I click at some random place. (Close only when menu button is clicked again).
3. Cursor should be pointer, when hovered on buttons.
4. Logo and User login title overlap.
Attached are some screenshots.
Comment #12
narendrarChanged status to Needs work for earlier posted comment.
Comment #13
manjit.singhThanks sumit for the contribution. here is my review
Headerin info file.path that you have mention in README.txt is not working. Please check error.png
custom.jsfileresponsive.css, line no. 31
box-sizing: content-box;style.css, line no. 14
Comment #14
Sumit kumar commentedThanks for review
@Manjit.Singh
@NarendraR
I had fix the bug
Comment #15
manjit.singhSeems like you forget to add vendor prefixes in style.css file.
Please take look into it.
Comment #16
manjit.singhRather than to resolve the issue, i guess you removed the path from README.txt .
Comment #17
Sumit kumar commentedHi @Manjit.Singh
added vendor prefixes in style.css file.
Comment #18
Sumit kumar commentedComment #19
narendrarHi Sumit,
I found some more issues related to UI.
1. Huge space between footer and content (screenshot attached).
2. If main menus are disabled, design breaks (screenshot attached).
Please do a complete regression testing before review, so that more serious issues can be found.
Comment #20
Sumit kumar commentedHi @NarendraR ,
please explain in details.
1. Huge space between footer and content
I can't see this issue on my machine. Please share more detail for clarity.
Comment #21
Sumit kumar commentedComment #22
Sumit kumar commentedComment #23
Sumit kumar commentedComment #24
manjit.singhIs there any updation in code ? Please do not change status everyday without getting any review.
If you want to speed up your own project through the review process, Please check this, and also you will learn a lot from this. The hope is that you will continue your involvement thereafter.
Comment #25
andrefy commentedI took a quick look to it, and think it maybe be still need some updates, custom.js is still not using Drupal behaviours,
Comment #26
andrefy commentedComment #27
Sumit kumar commentedUsed Drupal behaviors in custom.js
Comment #28
andrefy commentedHi Sumit kumar
I took a look to the themplate and tested agains a W3C validator. I found some errors that can be fixed, for example at page.tpl.php
There are some scenarios in which the
will be printed twice, it will recommended that id will be print only once on the document.
Regards
Comment #29
andrefy commentedComment #30
ayesh commentedHi Sumit,
Thanks for your contribution!
I haven't had the chance to install this in a test site yet, but I read the code anyway.
- in your js/custom.js file, feel free to "$" inside the behavior function. You have already taken jQuery to the local scope. That will save may be half a kilo byte from the file size.
- Also, be careful when attaching behaviors. Usually we need to use the jQuery once plugin (comes with Drupal core) to prevent subsequent event bindings.
- are you sure the fonts you have included are GPL'd?
Comment #31
Sumit kumar commentedComment #32
klausiRemoving review bonus tag, you have not done all manual reviews, you just posted the output of an automated review tool. Make sure to read through the source code of the other projects, as requested on the review bonus page.
Comment #33
Sumit kumar commentedadded manual review
Comment #34
Sumit kumar commentedadded manual review
Comment #35
deepakkumar14 commentedI have checked on my machine but i did not get any issues and i have also checked on mobile resolution 320, 768,480.
Comment #36
ashish_nirmohi commentedI like the color scheme of the Theme. I found no issue with the Theme. Theme is easily configurable with drupal 7. Thanks for your contribution.
Comment #37
ordasoft commentedHello,
Automated Review:
Please fix all error from pareview.sh
http://pareview.sh/pareview/httpgitdrupalorgsandboxsumitkumar2467223git
Manual Review:
README.txt/README.md
NO: Follows README Template.
https://www.drupal.org/node/2181737
Coding style & Drupal API usage
NO
-Please fix 2 "id" in logo
-Please check options what you show - you use, I not see in yours theme: "Site name", "Site slogan" - but you write - you use ?!
Please check all other yours theme settings.
-Please fix CSS
all tags what need special prefix for different browsers - so prefix need set.
as example:
- Not understand what layouts your theme has is Responsive or Fluid layout?
These full different layouts, please fix that in THEME description.
yours images not support Responsive.
Thanks,
Comment #38
Sumit kumar commentedThanks for review @Ordasoft
fixed all error from pareview.sh and manual review issues
Comment #39
Sumit kumar commentedComment #40
ordasoft commentedHello,
Please check all what I wrote, please recheck, please fix
README.txt don't fix
CSS - don't fix
options - don't fix
your theme has is Responsive or Fluid layout? - don't fix
Your theme designer, so all theme setting must work and look excellent !!!!
Please no submit part errors fixed
Thanks
Comment #41
ordasoft commentedComment #42
manjit.singhThanks @sumit for contribution
http://pareview.sh/pareview/httpgitdrupalorgsandboxsumitkumar2467223git is clean now.
@Ordasoft Can you please elaborate this your theme has is Responsive or Fluid layout ?
All other changes looks good to me.
Comment #43
ordasoft commentedHello,
your theme has is Responsive or Fluid layout? - don't fix (in Theme description on drupal.org)
README.txt - don't fix Follows README Template. https://www.drupal.org/node/2181737
CSS - don't fix -
as example for
Please check all so CSS styles
Thanks
Comment #44
ordasoft commentedComment #45
klausiREADME and CSS improvements are surely not application blockers, anything else that you found or should this be RTBC instead?
Comment #46
ordasoft commentedHello,
Responsive and Fluid - that full different layouts. Now theme work like responsible, so owner must remove Fluid layout from description
CSS - as me seem important for theme.
Readme Template - also drupal org requirements.
All other good for me.
Thanks
Comment #47
manjit.singhthanks @Ordasoft !!
@sumit Please remove fluid layout from description.
Also It would be god If you can add @file comments in CSS files. Please refer https://www.drupal.org/node/1887862#comments
Other changes are looks good to me.
@sumit Please do these changes, I am setting it to RTBC so that @klausi can take a look into it.
Comment #48
Sumit kumar commentedThanks @Manjit.Singh , @Ordasoft
i had done all the issue that you have mention
Comment #49
ordasoft commentedHello
fluid layout continue exist in theme description - not fixed

https://www.drupal.org/node/2470681#comment-10031661
Thanks
Comment #50
Sumit kumar commentedComment #51
manjit.singhThanks @Sumit, looks good now. Please wait for @klausi's final review.
Also please add new review bonus :)
Comment #52
Sumit kumar commentedadded manual review
Comment #53
klausiReview of the 7.x-1.x branch (commit 3e8671a):
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
But otherwise looks good to me.
Thanks for your contribution, Sumit kumar!
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 #54
manjit.singhCongratulation @Sumit !! Keep contributing and Keep up your good work.
Comment #55
PA robot commentedProject 1: https://www.drupal.org/node/2517820
Project 2: https://www.drupal.org/node/2470681
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 #56
klausiLet's leave this at fixed