This module extends the office hours module in various ways.
1) a new and userfriendly widget to select the office/opening hours for the field
2) a new field which is intended to organize exceptions from the weekly timetable. a widget is there to set these days in a calendar. besides explicit closing days its possible to activate profiles of closing days, so the user can choose from predefines times like christmas. at the moment these field has no formatter because its used for internal calculations but eventually it can be used in future to build advanced formatter options for the office hours module.
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/phoehne/2329615.git
Dependencies:
office_hours
jquery_update
Manual reviews of other projects
Comments
Comment #2
phoehne commentedComment #3
phoehne commentedComment #4
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxphoehne2329615git
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 #5
jimmyko commentedI love the idea as it improves the UX of office hour module.
I have a quick look on the code and found you use document ready rather then attach behaviours in js/timetable.js.
I recommend you to change above into below which would make other developer to have better control :
Comment #6
phoehne commentedHi Jimmy,
thanks for your time, i have implemented your suggestion and did some code cleanup.
Peter
Comment #7
ttronslien commentedAutomated Review found a couple of errors (Non-critical, but best practices)
http://pareview.sh/pareview/httpgitdrupalorgsandboxphoehne2329615git
Individual user account Follows.
No duplication: Does not cause.
Master Branch: Follows.
Licensing: Follows
3rd party assets/code: Follows.
README.txt/README.md: Does not follow.
Code long/complex enough for review: Follows.
Secure code: Meets the security requirements.
Coding style & Drupal API usage:
*Use the template for README.txt https://www.drupal.org/node/2181737
Additional Comments
I see you are now using Drupal.behaviors in javascript (Awesome)
Still using document ready in office_hours_extra.admin.inc ln 74
The css class naming is not unique to the project, this could cause conflicts. I'd suggest adding ohe to css class names
Which version of jQuery is required? Add to readme?
Comment #8
phoehne commentedHi ttronslien,
thanks for your review.
the errors reported by the autoreview:
-the intendations are correct in my opinion(i even tried as the bot suggest but it only throws other errors)
-the other two errors can not "really" removed. it's because calendars and timetables are big matrices on which i had to operate. there are by nature nestings necessary. sure i could refactor the code so these warnings vanish but this would not reduce the amount of calls and it would reduce the code readability.
readme:
-the readme follows now the drupal-standard
document ready in office_hours_extra.admin.inc:
-you are right i forgot the admin, its fixed.
The css class naming is not unique to the project:
-as you suggested a added ohe as prefix
version of jQuery:
-added Information on the required Version
Greetings
Peter
Comment #9
phoehne commentedComment #10
phoehne commentedComment #11
_KurT_ commentedinstalled module, went to
admin/config/date/timetable, got an error:Notice: Undefined variable: rows in office_hours_extra_list() (line 177 of C:\work\office_hours_extra\office_hours_extra.admin.inc).added:
i've just realized, seems like this error happened when i tried to add new profile without choosing any dates.
Comment #12
phoehne commentedHi Kurt,
thanks for your finding. fixed it.
Peter
Comment #13
gotosolr commentedWorks great, A couple of minor improvements for usability
1. When user is selecting the time slots whether to "Add" or "Remove" , the appropriate button should be highlighted. Although the mouse cursor has that indication, having it on the button would help
2. Saving a profile without choosing a date redirects user back to profile page without telling the user what happened. You should give a message indicating the reason
Automated Review:
Passed Coder module rests
Manual Review
Individual user account : Yes
No duplication : Yes
Master Branch : Yes
Licensing: Yes
3rd party assets/code : Yes
README.txt/README.md: Yes
Code long/complex enough for review: Yes
Secure code: yes
Comment #14
phoehne commentedHi,
Thanks for your time.
Added the proposed functionality.
Greetings Peter
Comment #15
klausiReview of the 7.x-1.x branch (commit 298f839):
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:
<script>alert('XSS');</script>as field label for an office hours field I will get a nasty javascript popup on the edit form of an entity. You need to sanitize user provided text before printing, make sure to read https://www.drupal.org/node/28984 again. And please don't remove the security tag, we keep that for statistics and to show examples of security problems. This is mitigated by the fact that an attacker must have the permission to administer fields, but currently that is already possible with the relatively innocent "administer taxonomy" permission in Drupal 7.Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
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.