Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
16 Jul 2014 at 07:31 UTC
Updated:
25 Oct 2014 at 10:24 UTC
Jump to comment: Most recent
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxtytus-tytus2298777git
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
howto commentedYour issue is missing:
You should change your git clone command because it's a personal git clone command.
Please see this: https://www.drupal.org/node/1011698
Comment #3
gisleBetter fix this as well:
README.txt, including "Configuration" are currently empty.Comment #4
tytus-tytus commentedComment #5
tytus-tytus commentedHi, I just made an update for mentioned issues. Is there is anything more to do please let me know through comments I will try to do that asap.
Thanks
Comment #6
gisleYou've fixed some. Please fix them all before requesting a review.
Comment #7
tytus-tytus commentedI made more changes.
Please let me know what I am missing. Also should I write here about the changes which I made from last review?
Comment #8
ethantIt would be helpful tytus-tytus, if you could go through all items listed by gisle, and give a brief response to the solution you implemented for each. Example:
Project link page added.
Switched to branch xyz
Added {.....} to project page.
Added {.....} to README.txt
Per documentation guidelines, added {.....} and changed {.....}.
Comment #9
tytus-tytus commentedProject link page added.
Switched to branch 7.x-1.x
Added Features, Requirements, Known problems, Credits and Instruction after installation to project page. Recommended modules was left with "None" because of none of these.
Added Requirements, Configuration, Troubleshooting and Maintainers section to README.txt
Per documentation guidelines, added screenshot, better description to project page. Fill up readme file, add more comments to functions in project code.
Comment #10
tytus-tytus commentedComment #11
tytus-tytus commentedPlease review.
Comment #12
mpdonadio@tytus-tytus, see the comment in #1 about a review bonus. This will get your module looked at quicker.
Comment #13
mxr576Pareview still containing several warnings, please fix them.
http://pareview.sh/pareview/httpgitdrupalorgsandboxtytus-tytus2298777git
If you aren't doing anything on visual_website_editor.install, then why you have this file on your module? FYI: it is not necessary to implements hook_install() and hook_uninstall() on your module if your module not necessary to do sth when it's installed or uninstalled. (Moreover the proper DOxygen comments missing form your implementations...)
Also please comment/indent your code properly:
(Double line breaks before global $user is wrong, which do not visible here.)
Are you sure, that you want to use hook_boot() instead of hook_init()? FYI:
Is this really necessary for your module?
I've tried to test your module on http://simplytest.me/project/2298777, but something weird happened. First of all I can not switch on the your module several times, after all I've got this error:
Parse error: syntax error, unexpected T_STRING in /home/s23bed938eef8cea/www/sites/default/modules/2298777/TidioElementsParser/PhpQuery.php on line 3753I think it isn't any affect that you have set the status to major, please try to get review bonus (just as I doing it right now) for faster reviews. But first, please fixed the mentioned bugs, improve your code!
Regards, mxr576
Comment #14
tytus-tytus commentedThanks mxr576 for a review. Below is my list of changes with notes for your review:
Most of the errors was fixed. Our module use extra library where we is one more error with function name. Should we change nam of this function in this library?
Files was deleted.
We added extra comments for methods. Should we add something else?
We removed it.
We need it. With hook_init our plugin does not work properly.
After update our module is installed and works ok.
Comment #15
tytus-tytus commentedComment #16
mxr576I recommend you that if you made some changes on your code then always re-test your project in http://pareview.sh/pareview/httpgitdrupalorgsandboxtytus-tytus2298777git before you change the project status to "needs review". While this page contains errors your project never get full project application I think. (If you need some help to solve this problems feel free to ask, of course.)
So this page still contains lot of errors, mostly in your external library:
Comment #17
gisleThe module comes bundled with phpQuery.php, which appears to be third party code created by Tobiasz Cudnik. Third party code is not generally allowed on Drupal.org and should be deleted.
This particular code is made available under the MIT license. This license may be compatible with GPL V2+, but all third party content must be explicitly approved by Drupal.org webmasters to be hosted on Drupal.org.
This policy is described in the 3rd party libraries and content on Drupal.org. It also appears in the Drupal Git Repository Usage policy you agreed to when you signed up for Git access, which you may want to re-read, to be sure you're not violating other terms.
The Libraries API module is a recommended method for adding 3rd party dependencies without directly including the code on Drupal.org.
Comment #18
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.