Activities of "berkansasmaz"

Hi,

The logs show that the problem started with write operations at the physical link layer (PhysicalBridge).

ABP is the Microsoft.Extensions.Caching.StackExchangeRedis package and we don't have any custom code there. Honestly, I think the problem may be for a different reason. For example, a user reported the following problem on stackoverflow. In your case, where are you deploying the application and is this error only happening in production?

Reference: https://stackoverflow.com/a/72729503/9922629

Hi,

I understand your problem now. Yes, you can implement this method, there is no problem with that. However, instead of implementing this manually to all CRUD pages, my advice to you would be to customize the templates of ABP Suite. You can find all the templates in the picture below, you can customize the templates here according to your needs, ABP Suite will generate the code according to your customization. See more: https://abp.io/docs/latest/suite/editing-templates

If you don't want to do this, you can generate custumizable code with ABP Suite so you can customize the generated code as you want. See more: https://abp.io/docs/latest/suite/customizing-the-generated-code

Hello,

First of all, thank you for sending your project. Interestingly, when we override the OnPost method, the action value is not added to the form. I haven't found the root cause, but you can update your Login.js file as follows and continue.

Login.js:

$(function () {

    var isRecaptchaEnabled = typeof grecaptcha !== 'undefined';
    if (isRecaptchaEnabled) {
        grecaptcha.ready(function () {
            $("#loginForm button[type=submit]").removeAttr("disabled");
        });
    } else {
        $("#loginForm button[type=submit]").removeAttr("disabled");
    }

    $("#loginForm button[type=submit]").click(function (e) {
        e.preventDefault();
        var form = $("#loginForm");
        var submitButton = $(this);

        var actionInput = $("<input>")
            .attr("type", "hidden")
            .attr("name", "Action")
            .val(submitButton.val());
        form.append(actionInput);
        
        if (form.valid() && isRecaptchaEnabled && abp.utils.isFunction(grecaptcha.reExecute)) {
            grecaptcha.reExecute(function (token) {
                form.find("input[type=hidden][data-captcha=true]").val(token);
                abp.ui.setBusy("#loginForm");
                form.submit();
            })
        } else {
            if (form.valid()){
                abp.ui.setBusy("#loginForm");
            }
            form.submit();
        }
    });

    $("#PasswordVisibilityButton").click(function (e) {
        let button = $(this);
        let passwordInput = $('#password-input');
        if (!passwordInput) {
            return;
        }

        if (passwordInput.attr("type") === "password") {
            passwordInput.attr("type", "text");
        }
        else {
            passwordInput.attr("type", "password");
        }

        let icon = $("#PasswordVisibilityButton");
        if (icon) {
            icon.toggleClass("bi-eye-slash").toggleClass("bi-eye");
        }
    });

    // CAPS LOCK CONTROL
    const password = document.getElementById('password-input');
    const passwordMsg = document.getElementById('capslockicon');
    if (password && passwordMsg) {
        password.addEventListener('keyup', e => {
            if (typeof e.getModifierState === 'function') {
                passwordMsg.style = e.getModifierState('CapsLock') ? 'display: inline' : 'display: none';
            }
        });
    }
});

Hi,

I'm very glad that the problem is solved. Yes, we can make it even easier in the future. As you can see, we have related issues, but it is not among our priorities at the moment because there is already a way.


Closing the issue. Feel free to create a new issue if you have further questions.

First of all, thank you for submitting your project. I am also using macOS M1 and I was able to reproduce the problem. Interestingly, I found that the application crashes when the GetListAsync repository method is called. According to my findings, I think that the problem is not in the query but in having too many parameters when calling the method. I would like you to do a few experiments to make sure that you have the same problem.

Comment out the GetListAsync method in AppService as below and see if there is a problem:

If there is no problem, remove the method from the comment line and update the content of the GetListAsync repository method as below and run it again. You will see that the problem has started to occur again.

If all this is happening in your case, it indicates that the problem is not in the query, but in calling the method.

Probably more than 200 parameters are not supported by the dotnet runtime, but I am not sure. We can investigate in detail after you verify them.

Hi,

I got it, I think the problem is somewhere else. Because when I try the same code, I don't encounter any problems. Can you send your project to berkan.sasmaz@volosoft.com address?

Hi,

Yes, I missed the problem of repeating CSS's. I sent a commit again. Can you check it?

No, this does not mean that you cannot run the application with ABP Studio. It just means that you cannot add a new service with ABP Studio.

If you want to run your solution via ABP Studio, follow steps below:

1-) Click on the "Initialize existing solution" menu item like below:

Select your solution(*.sln) file.

2-) Then, if there is no solution runner profile, you can add it and add your services to it. This document explains how to do it.

Answer

I understand, you can send it to berkan.sasmaz@volosoft.com mail address.

Answer

There doesn't seem to be any error here. Can you please send me the full recording?

Showing 211 to 220 of 737 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.1.0-preview. Updated on December 17, 2025, 07:08
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.