Commerce My Delivery Times allows you to configure desired time slot. You can configure master time slot which will appear on checkout pane. You can also create an individual time slot which is different from Master slot configuration which will appear on checkout time slot pane respectively. Edit or delete feature of slot configuration is also provided.
Sandbox URL :
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/pratik.mehta19/2555313.git commerce_my_delivery_times
Sandbox Page:
https://www.drupal.org/sandbox/pratik.mehta19/2555313
You can configure start time and end time of every slot. Maximum number of order to be placed in every slot and threshold time of accepting order.
Holiday can also be configured. User cannot choose an holiday date.
A configuration setting page is provided for maximum number of days in checkout pane, maximum number of slots per day and whether to allow same day delivery or not.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | commerce_my_delivery_times.zip | 160.41 KB | pratik.mehta19 |
Comments
Comment #1
jcontreras commentedI runned your code through "pareview.sh" there are errors to fix before a manual review.. please fix those errors first.
You can see the list for your module here:
http://pareview.sh/pareview/httpgitdrupalorgsandboxpratikmehta192466947git
Comment #2
pratik.mehta19 commentedComment #3
jcontreras commentedI don;t know why the link to the error list I gave you before is not working. Try this:
http://pareview.sh/pareview/httpgitdrupalorgsandboxpratikmehta192466947git
Comment #4
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.
Comment #5
ajay_reddyComment #6
ajay_reddyGit Clone URL not working
Change it as git clone --branch 7.x-1.x http://git.drupal.org/sandbox/pratik.mehta19/2466947.git commerce_my_delivery_times
Comment #7
klausiLet's keep this closed until we get a response from @pratik.mehta19.
Comment #8
pratik.mehta19 commentedComment #9
pratik.mehta19 commentedComment #10
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 #11
pravin ajaaz commentedHi Pratik,
I didn't completely know the purpose of your module yet. But When I installed it and used the form elements, I could detect some serious Security vulnerabilities.
Here is the list of my suggestions:
1. Security Issue first :) In the page
admin/commerce/delivery-times/holiday-configuration, try inserting the Holiday reason as:<script>alert('xss');</script>Did you get a alert box when seeing the list again, this is because you have not sanitized the text before outputting them. Please read through Handle text in a secure fashion. Use check_plain while building the $row in holiday_calendar_form function.
2. What is this function used for
my_delivery_times_checkout_form. Is this implementation of hook_form(), then the function name should start with commerce_my_delivery_times. Read through the function of hook_form before using it. Also In the function build the table manually using HTML tags, You should not bring the theming part inside a module. Use theme function to build the table.3. Take care of the pareview there are many.
Comment #12
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.
Comment #13
sfederico commentedHi,
I've installed this module and setup elements in page Delivery Time Slots Configuration
but in page chekout this appear this error
Warning: max(): Array must contain at least one element in my_delivery_times_checkout_form() (linea 83 di C:\htdocs\devcibario\sites\all\modules\commerce_my_delivery_times\includes\my_delivery_times.checkout_pane.inc).
have you any idea? what's i missed setup?
Thank's
Comment #14
pratik.mehta19 commentedHi sfederico,
Please have a look into, i have resolved bug and you can proceed further.
Comment #15
liampower commentedAutomated Review
[Best practice issues identified by pareview.sh / drupalcs / coder. Please don't copy/paste all of the results unless they are short. If there are a lot, then post a link to the automated review and mention that problems should be addressed.]
You have some automated review issues identified here: http://pareview.sh/pareview/httpgitdrupalorgsandboxpratikmehta192555313git
FILE: ...www/drupal-7-pareview/pareview_temp/commerce_my_delivery_times.module
---------------------------------------------------------------------------
FOUND 0 ERRORS AND 6 WARNINGS AFFECTING 6 LINES
---------------------------------------------------------------------------
79 | WARNING | Open page callback found, please add a comment before the
| | line why there is no access restriction
128 | WARNING | #description values usually have to run through t() for
| | translation
131 | WARNING | All variables defined by your module must be prefixed
Note that perfect adherence to Drupal Coding Standard is NOT a reason to block an application, except for total disregard of them. However, modules should follow them as closely as possible.
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #16
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.
Comment #17
avpaderno