Actions
Bug #5200
closedGlistenrea-->home Page --> Buy/Rent --> Filter property --> View property -->Owner details below the map, when the Login applicant clicks on the view phone number button it is not working on the first time but when the applicant clicks on it the second ti
Status:
Closed
Priority:
Normal
Assignee:
Manoj jaswal
Start date:
11/16/2022
Due date:
% Done:
0%
Estimated time:
Description
Step to reproduce the bug:
Home Page --> Buy/Rent --> Filter property --> View property --> Owner details below the map, when the Login applicant clicks on the view phone number button it is not working on the first time but when the applicant clicks on it the second time then owner phone number is shows
See attached screenshot:
Files
Updated by Mohd Irfan almost 2 years ago
- Subject changed from Home Page --> Buy/Rent --> Filter property --> View property --> Owner details below the map, when Log in applicant click on view phone number button it is not working on first time when applicant click on second time then show phone number to Glistenrea-->home Page --> Buy/Rent --> Filter property --> View property --> Owner details below the map, when Log in applicant click on view phone number button it is not working on first time when applicant click on second time then show phone number
Updated by Mohd Irfan almost 2 years ago
- Subject changed from Glistenrea-->home Page --> Buy/Rent --> Filter property --> View property --> Owner details below the map, when Log in applicant click on view phone number button it is not working on first time when applicant click on second time then show phone number to Glistenrea-->home Page --> Buy/Rent --> Filter property --> View property -->Owner details below the map, when the Login applicant clicks on the view phone number button it is not working on the first time but when the applicant clicks on it the second ti
Updated by Mohd Irfan almost 2 years ago
- File clipboard-202211301749-tufu7.png clipboard-202211301749-tufu7.png added
- Status changed from Resolved to Closed
This issue has been verified
and it has been found that the issue is fixed!
See attached screenshot:
Actions