Find bugs in nopCommerce 4.00 BETA and earn $10

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
Hard coded text in Customer edit page.

Text: Some comment here...

screen shot:
https://ibb.co/jZBjRR
6 years ago
Hard coded text in kendo grid

text: Save changes
text: Cancel changes
6 years ago
a character space required in product tag edit page.

screen shot:
https://ibb.co/iQNf0m
6 years ago
bakbuz wrote:
There are multiple script references in page source.


screen shot:
https://ibb.co/jDjzt6

You're absolutely right. Fixed
6 years ago
bakbuz wrote:
TinyMceHelper.GetTinyMceLanguage() static method does not work correctly.

Source of the problem: $"{path}{langFile}"

Solution to the problem: $"{path}\\{langFile}"
(line numbers: 30, 36, 43, 50)


screen shot:
https://ibb.co/nHdOmR

Thanks again. Fixed
6 years ago
bakbuz wrote:
Hard coded text in Customer edit page.

Text: Some comment here...

screen shot:
https://ibb.co/jZBjRR

Although we don't consider non-localizable strings as bugs, thanks a lot anyway.Here is a work item
6 years ago
bakbuz wrote:
Hard coded text in kendo grid

text: Save changes
text: Cancel changes

Thanks. But already reported
6 years ago
bakbuz wrote:
a character space required in product tag edit page.

screen shot:
https://ibb.co/iQNf0m

And the third confirmed issue. Fixed. Good job! Thanks a lot!
6 years ago
Hi,

We believe there is a bug introduced in v4.00.
Customer is unable to login if customer is created from Admin when CustomerSetting.UsernameEnabled is set to false.

Steps to Reproduce:
1. Set UsernamesEnabled as false in Settings -> customer Settings.
2. Create new customer from Admin area.
3. Try to login from customer area with this new user's email.

Actual Result:
User is unable to login and the page ends up to exception.

Reason:
When customer is created from admin area, username field is left 'null' which in turn ends to null exception while creating claim in CookieAuthenticationService.SignIn(Customer customer, bool isPersistent)

Solution:
In '..\Presentation\Nop.Web\Areas\Admin\Controllers\CustomerController.cs'
'Create' Post action near Line 900 where Customer object is created the username should be set to model.Email if UsernameEnabled is false else it should be model.Username

Username = _customerSettings.UsernamesEnabled ? model.Username : model.Email


Hope this helps.

Best Regards,
Atluz Nop Team
6 years ago
atluz.com wrote:
We believe there is a bug introduced in v4.00.
Customer is unable to login if customer is created from Admin when CustomerSetting.UsernameEnabled is set to false...

Thanks a lot for reporting. You're right. We'll fix it soon
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.