Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Jun 2013 at 12:50 UTC
Updated:
5 Oct 2013 at 10:24 UTC
Jump to comment: Most recent file
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxgastas1819740git
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
itapplication commentedTested on latest version of Firefox, IE, Chrome and Safari. Happy to see this project for production if developer fix errors of 'Bad line endings were found' reported by "PA robot" and some css errors found at w3.org validator. Please check this http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fthemes.gas....
Comment #3
gastas commentedFix errors of 'Bad line endings were found'
Fix validator error on style.css.
Comment #4
Ujval Shah commentedManual Review :
(1) page__error.tpl.php
1. unwanted numerics are on line - 1
Example : 123412
2. use l() for links and t() for texts.
Example : line no -180 and 183
Drupal should be l(t('Drupal'),'http://drupal.org')
(2) page.tpl.php
1. use l() for links and t() for texts.
Example : line no -180 and 183
Drupal should be l(t('Drupal'),'http://drupal.org')
(3) js/script.js
1. remove un-wanted code - line no 15 to 19 and line no - 21
General :
Drupal Coding standards are missing (please check the Drupal coding standards).
Comment #5
gastas commentedDeleted page__error.tpl.php
Fix page.tpl.php and js/script.js
Comment #6
jnettikThank you for your contribution.
After first enabling the theme on a fresh install of Drupal I get the following errors:
Those regions don't exist in the theme's .info file but still referenced in the page.tpl.php.
Comment #7
jnettikComment #8
jnettikManual Code Review:
template.php
Line 127 has a reference to page__error, however that file no longer exists.
File structure
Not necessary, but I like to put my template files in a templates/ directory, which helps keep the theme root cleaner. Some other contrib themes follow this convention.
Comment #9
gastas commentedFix template.php
Put template files in a /templates directory.
Comment #10
itapplication commentedHi gastas,
I manually installed your theme 'dynamic'. I get following errors.
Please fix above errors.

I also attached screenshot for your reference.
Comment #11
itapplication commentedChanging status until fix all bugs.
Comment #12
gastas commentedErrors fixed.
Comment #13
hatuhay commentedFor the integration of Twitter Bootstrap into Drupal, the Base Theme Twitter Bootstrap appears to be a solid option and I will rather recommend to build a subtheme instead of going all the way again with a new base theme.
Page is not showing on 1200px width, styles overwrited on style.css
Do not find TB javascript files, only images and styles.
Documentation does not help, neither readme.txt nor the project page.
Reviewing your templates found this hardcoded info on node--product_display.tpl that actually refers directly to you. This cannot be changed unless you hack this theme file.
Comment #14
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.