Activities of "berkansasmaz"

Hello, thanks for the report.

I'm creating an internal issue on the topic.

Hi, you don't need to define RequiredFeatures at permission group level. Because if all the permissions under it are not already accessible, the group will be invisible either.

Thanks for reporting the issue. I'm opening an internal issue on the subject.

Please let us know if you need a workaround solution.

We use the ABP framework on our websites, but we did not encounter such a problem. We need to examine it in detail. However, before starting the detailed examination, can you write the code below and send the rendered version using your browser's developer tool?

        <abp-container>
            <abp-row>
                <abp-column>1 of 2</abp-column>
                <abp-column>2 of 2</abp-column>
            </abp-row>
            <abp-row>
                <abp-column>1 of 3</abp-column>
                <abp-column>2 of 3</abp-column>
                <abp-column>3 of 3</abp-column>
            </abp-row>
        </abp-container>

The rendered version should look like this:

         <div class="container">
            <div class="row">
                <div class="col">1 of 2</div>
                <div class="col">2 of 2</div>
            </div>
            <div class="row">
                <div class="col">1 of 3</div>
                <div class="col">2 of 3</div>
                <div class="col">3 of 3</div>
            </div>
        </div>

If there is no problem with this, we may need to examine the CSS.

Can we confirm that Problem 2 and 3 are solved?

Any chance you could send your OrderService.Web/Pages/Orders/index.js and OrderService.HttpApi.Client/wwwroot/client-proxies/OrderService-proxy.js files?

Problem 3: See https://support.abp.io/QA/Questions/3501/Microservice-screen-loading-issue#answer-ffcbbe27-6d6f-ec83-9812-3a057689958c

I'll check for other problems.

Can you run the following two commands in the YourProjectName.OrderService.HttpApi.Client project?

Note: Before running the commands, make sure to write your OrderService's port in the {YourOrderServicePort} section and make sure the application is running.

1. abp generate-proxy -t csharp -u https://localhost:{YourOrderServicePort} -m OrderService
2. abp generate-proxy -t js -u https://localhost:{YourOrderServicePort} -m OrderService

Afterward, it should be sufficient to run the project again.

I'm creating an internal issue on the topic. Thanks for reporting it.

Sure I can, you can find all the information you need below.

Volo.CmsKit.Pro.Public.HttpApi/Volo/CmsKit/Public/Contact/ContactPublicController.cs

using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Owl.reCAPTCHA;
using Owl.reCAPTCHA.v3;
using Volo.Abp;
using Volo.Abp.GlobalFeatures;
using Volo.CmsKit.GlobalFeatures;

namespace Volo.CmsKit.Public.Contact;

[RequiresGlobalFeature(typeof(ContactFeature))]
[RemoteService(Name = CmsKitProPublicRemoteServiceConsts.RemoteServiceName)]
[Area(CmsKitProPublicRemoteServiceConsts.ModuleName)]
[Route("api/cms-kit-public/contacts")]
public class ContactPublicController : CmsKitProPublicController, IContactPublicAppService
{
    protected IContactPublicAppService ContactPublicAppService { get; }

    protected IreCAPTCHASiteVerifyV3 SiteVerify { get; }

    public ContactPublicController(IContactPublicAppService contactPublicAppService, IreCAPTCHASiteVerifyV3 siteVerify)
    {
        ContactPublicAppService = contactPublicAppService;
        SiteVerify = siteVerify;
    }

    [HttpPost]
    public virtual async Task SendMessageAsync(ContactCreateInput input)
    {
        var response = await SiteVerify.Verify(new reCAPTCHASiteVerifyRequest
        {
            Response = input.RecaptchaToken,
            RemoteIp = HttpContext.Connection.RemoteIpAddress.ToString()
        });

        if (response.Success && response.Score > 0.5)
        {
            await ContactPublicAppService.SendMessageAsync(input);
        }
        else
        {
            throw new UserFriendlyException(L["RecaptchaError"]);
        }
    }
}

Volo.CmsKit.Pro.Public.Web/Pages/Public/Shared/Components/Contact/Default.js

(function ($) {
    var l = abp.localization.getResource("CmsKit");

    abp.widgets.CmsContact = function ($widget) {
        var widgetManager = $widget.data("abp-widget-manager");

        function init() {
            $widget.find(".contact-form").on('submit', '', function (e) {
                e.preventDefault();

                var formAsObject = $(this).serializeFormToObject();

                volo.cmsKit.public.contact.contactPublic.sendMessage(
                    {
                        name: formAsObject.name,
                        subject: formAsObject.subject,
                        email: formAsObject.emailAddress,
                        message: formAsObject.message,
                        recaptchaToken: formAsObject.recaptchaToken
                    }
                ).then(function () {
                    abp.message.success(l("ContactSuccess"))
                        .then(function () {
                            widgetManager.refresh($widget);
                        });
                })
            });
        }

        return {
            init: init
        }
    };
})(jQuery);

We are aware of this issue, it will be fixed with the patch version soon. As a workaround, you need to override ContactPublicController's SendMessageAsync method and delete the reCAPTCHA related code, also you need to override the Contact component's default.js and assign a value to its RecaptchaToken because RecaptchaToken Required attribute is added in ContactCreateInput.

With this workaround solution, we disable reCAPTCHA, but as you said, it doesn't work even if we make the necessary configurations, but it will be solved with the patch version, so my advice is to wait for the patch version.