Tkuldeep/issue 85

[tkuldeep]

reference -> #85

[tkuldeep]

@sumeetpareek Please review this pull request..

[sumeetpareek]

My take -

• do not do any work wihtout an issue.. even if there is no code involved.. use relevant issue.. this helps in keeping the context out there that can be shared with others..
• branches should be named as per the convention YOURNAME/ID-SOME-WORD (eg: kuldeep/85-data-maps) .. drupal.org too has a neat convention for naming patches, and it really works..
• cut your branch off the top of develop .. most of the cases that is .. genuine expections (and prod hotfixes) are acceptable ..

I am removing the top 2 commits pointed below and cherry picking the remaining 3 in a new branch of mine.. you can continue working on the new branch to fix any more changes needed (I am not sure if you can rename that branch and update this same pull request .. or you would have to create a new one..)

[tkuldeep]

I think, if I send new branch, that new pull request pull will be created.

[sumeetpareek]

@tkuldeep I have pushed the new branch by the name - tkuldeep/85-92-branch-fix

[sumeetpareek]

This pull request is not relevant anymore.

[tkuldeep]

For deploying this pull request

• Enable the feature f_map_details
• Revert the feature f_candidate_details

After mredirect module is working correctly

• Disable the module mobile_js_redirect
• Enable the module mredirect module.