Hi @cotur,
Thank you for the link and for clarifying what the issue was. I just had to add a single line of code and it is working as expected. Thak you again and keep up the great work!
Hi @cotur,
Finally opened my eyes. The problem was Redis. I had commented out the Redis configuration form appsetting.json both in Identity and API, for some reason. But today I cam across a ticket of yours explainig the importance of Redis in tiered solutions, https://support.abp.io/QA/Questions/848/Unable-to-connect-to-redis-serverS and I decided to give it a go. And voila...the file management works!
I am sorry to have wasted your time and I hope ,since I managed to untangle myself, this ticket doesn't consume one of our credits :) Best of days to you and the whole team behind this project!
PS: Any news on the DatePicker thing?
Hi @ilitzy
I've tested 2 cases (File Management & DatePicker) with
4.3
(not rc) version. About the File Management, it worked, I could not reproduced. Can you please test it with4.3
version and if you have problem, please send me a reproducable minimal example.About the DatePicker, yes there is a problem, we will investigate it. Thanks so much.
Hello,
I created a simple Blazor- WebAssembly project with abp suite, (Mongo and separated Identity server) in order to test the File management , but I still get the same error. It has been created with the version 4.3.0 without any rc.
Am I doing something wrong?
Me again, @Cotur :) More details on the date piker thing!
So, I altered the CreateAsync function in AppService.cs with an extra switch statement This switch saves dates ok except for: 30 and 31, in which case it saves dates :29 and 30 instead. If I comment out the first 2 cases of the switch I get an error (only for Day=30 or 31)
I don't know if this aspect is related to your framework or if it has to do with Blazorise, but please fix this. Thank you again and I appologise for nagging, but our customers will not accept this behaviour!
Hello @Cotur,
The settings are: Blazor+Mongo+separate Identity Apart from that, I upgraded an existing project I am working on to v4.3-rc.2 and there stil are problems with the date picker, in the sense that it allows you to write a year with 6 digits, and I choose a date eg:02.01.2021 I saves it inside Mongo as (chosen date-1) on the 01.01.2021 and it is returned that way in the Blazor Grid The setting is the same: tiered , Blazor+Mongo+separate Identity
Thank you in advance!
Literally saved the hair on my head! Thank you!
Hello @alper,
I was hoping this bug to be fixed in 4.2 (first saw it in 4.1.2) but it seems to want to stay. My problem is, when I build a Blazor + separate Identity Server project, the basic DateTimePicker is not behaving how it should. Tried both Sql and Mongo and results are as follows:
SQL: -starts from 01/01/01 and allows you to manually modify only date or month. If you attemp to modify both date and month it turns back to 01/01/0001.The year is untouchable , as it appears you can only modify the last 2 digits of it. -The today button however, works ok, but it is unpleasent to scorll down to the required year starting from 2021 -Saves date exactly
Mongo: -same problem with DateTimePicker and manual modifications -saves not the chosen date, but the day before that (eg: I pick 05.02.2021 and it saves 04.02.2021)
Must mention the project and CRUD pages were generated by the abp suite and there were no modifications whatsoever to the page rendering the grid, nor were there any modifications to the AppService Create method.
Thank you in advance for your response and keep up the good work!