Project page: https://www.drupal.org/sandbox/redhead/2535100
Project name: Masquerade float block (masquerade_float_block)
Git repository: http://git.drupal.org/sandbox/redhead/2535100.git
Pareview: http://pareview.sh/pareview/httpgitdrupalorgsandboxredhead2535100git
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/redhead/2535100.git masquerade_float_block
cd masquerade_float_block
Drupal version: 7,
Dependencies: masquerade
Description:
This is simple module which works with Masquerade module and provides float
Masquerade block.
The module is useful when you use panels everywhere on the site and
features to export the configuration.
With this module you don't need to care about removing Masquerade
block from panel configuration for stage or live environment.
Initial block position is left top, but it can be changed by dragging the block.
Position will be remembered.
Block inherits all settings from native Masquerade block.
USAGE:
Once module was enabled, you will see the Masquerade block on the
left top position.
Also, you can control appearing of the Masquerade block in three ways:
- With admin UI: navigate to
admin/config/people/masquerade/float-block
(People > Masquerade > Float block) , enable or disable float block. - pass the
?mfb_show
parameter in GET request to 1 or 0
ex.:http://site.com?mfb_show=1
- enable Masquerade block
-1
enable Masquerade block on all pages
-0
disable Masquerade block on all pages -
set the "masquerade_float_block_visible" variable to
1
or0
.
ex.:variable_set('masquerade_float_block_visible', 1)
- enable Masquerade block
in settings.php:
$cong['masquerade_float_block_visible'] = 0
- disable Masquerade block
My manual Reviews of other projects:
- https://www.drupal.org/node/2536388#comment-10138882
- https://www.drupal.org/node/2533002#comment-10139092
- https://www.drupal.org/node/2536988#comment-10139252
- https://www.drupal.org/node/2193367#comment-10145420
- https://www.drupal.org/node/2155969#comment-10145608
- https://www.drupal.org/node/2536388#comment-10176466
Other reviews:
https://www.drupal.org/node/2333893#comment-10131198
Comments
Comment #1
ajalan065 CreditAttribution: ajalan065 as a volunteer and at Innoraft commentedHi dstorozhuk,
Please fix your git clone command. It requires your password. You can get correct command from the version control tab of your sandbox project
Comment #2
ajalan065 CreditAttribution: ajalan065 as a volunteer and at Innoraft commentedAnd no need of assigning it to yourself.
Comment #3
dstorozhuk@ajalan065 Done, thanks.
Comment #4
ajalan065 CreditAttribution: ajalan065 as a volunteer and at Innoraft commentedComment #5
dstorozhukUpdate Pareview.
Comment #6
dstorozhukComment #7
PA robot CreditAttribution: 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 #8
babusaheb.vikas CreditAttribution: babusaheb.vikas commented1) It would be better if your *.info file looks like:
2) You should provide the hook_help to allow site builders to find information about your module using Drupal UI.
Comment #9
dstorozhuk@babusaheb.vikas,
#1 is done, thanks for your review. But can you, please, explain reasons why #1 (or provide a link)? Here Writing module .info files (Drupal 7.x) I can't find any directions about the .info file content order. Only table of content, but there is nothing about following the order.
#2 done.
Comment #10
dstorozhukComment #11
dstorozhukComment #12
dstorozhukComment #13
dstorozhukComment #14
dstorozhukComment #15
dstorozhukComment #16
dstorozhukUpdate the description.
Comment #17
dstorozhukComment #18
dstorozhukComment #19
dstorozhukComment #20
Torvald CreditAttribution: Torvald commentedHi dstorozhuk,
Pareview / Coder review: OK
I have reviewed your project.
I think everythink works fine.
Good work!
Comment #21
dstorozhukOk, thanks.
Waiting for review from Drupal admins.
Comment #22
rutel95My suggestions:
1) After turning on the float block is disclosed, make it better shut.
2) By default it would be better to open the popup float block was in the middle
3) It is better to hide the float block from admin / * pages
And so all good for me.
Comment #23
dstorozhukComment #24
dstorozhuk@ruslan_03492, thanks for your review.
Let's wait for other users feedback. If I get same opinion as your from one more user, I will perform changes in behaviour you suggest.
Comment #25
apadernoThank you for your contribution!
I am going to update your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thank you, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thank you to the dedicated reviewer(s) as well.