Overview
The Toolbar Paths module provides a simple settings interface which allows you to
control the display of the drupal 7 Toolbar, by simply invoking path conditions.
This module may come to use, while using internal iframes and such.
Also handy to tidy up on unique necessities.
It came to use while migrating my project BeeSmart to drupal 7.
Features
This module will show/hide the toolbar due to the settings configured.
Requirements
Toolbar module - Drupal 7 Core.
The module itself has no particular PHP, database, or Drupal requirements, other than it only works with Drupal 7.x.
More information on the Project Page
Git access:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/ohadsh535/1858152.git toolbar_paths
Comments
Comment #1
ohadsh535 commentedComment #2
tomgeekery commentedHello,
You are using the master branch of git, you need to be using a version specific branch. Good article here.
There is no need for the license.txt file. Drupal will add that for you.
Your info file contains some lines that were added by the drupal packaging script, not sure why those are there, but I am pretty sure they shouldn't be there.
There are also a few errors shown here: http://ventral.org/pareview/httpgitdrupalorgsandboxohadsh5351858152git
Comment #3
tomgeekery commentedComment #4
ohadsh535 commentedOkay, I've fixed all the PAReview logs.
Fixes made:
Pretty basic stuff, I will pay more attention.
Comment #5
monymirzaHi,
README.txt
change line #13
admin/config/user-interface/toolbar-pathsto "Configuration > User interface > Toolbar Paths"Comment #6
ohadsh535 commentedHey,
Thanks monymirza.
Change was made, will be on the next commit.
Comment #7
asifnoor commentedIn the function toolbar_paths_settings, please use t() function for descriptions. Also remove unnecessary line break before return statement.
Comment #8
ohadsh535 commentedFixes made and committed.
Not sure it's worthy a commit, but it has been committed.
General question:
- All fixes, even minor as on comment #7 are a reasonable cause to put a project on status "needs work" ?
Comment #9
miloyz commentedHi ohadsh535,
Thanks very much for contributing this very nice module and fixing the coding standards errors.
I have reviewed your module quickly and didn't find any particular issues, except one comment I would have:
In file toolbar_paths.module, at lines 74:
I was wondering if you could perhaps consider moving this code out of the toolbar_paths.module.
The function toolbar_paths_settings would be moved to toolbar_paths.admin.inc.
You could then add a call to this file in the menu callback that actually calls this form, so pretty much after line 32:
If you made this change it would slightly optimize the memory footprint upon execution of the module, which I guess it something probably quite important to get a validation here.
So far, that's all I could find, but I will keep looking and certainly let you know if I can find anything else.
I hope this comment will help you to improve this nice module.
Cheers!
Comment #10
ohadsh535 commentedHi miloyz,
Thanks for taking the time and reviewing.
I have adjusted the module due to your comment. It's already committed.
I really would apply this improvement in other developments of mine.
Thanks again for tour help mate !
Comment #11
klausiProject 1: http://drupal.org/node/1859944
Project 2: http://drupal.org/node/1858950
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.
We are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)
Comment #11.0
klausiFixed the git branch link.
Comment #12
avpaderno