BeycanPress LLC

Thank you so much.

I understand, but I’m having problems with the “development process” of a modular plugin for which you provide an API for development, and you say you can’t support it. If you only provide me with an unminified js file, I think I can already handle the rest of the process. Also, if I remember correctly, unminifed js files were mandatory for wp.org.

My goal is to develop “Field” and “Payment gateway” for Forminator. I have started the process on the PHP side and “Field” appears in the list. However, when I select “Field”, Forminator crashes, probably because something I need to add on the JS side is not added.

You can support me even just by reviewing the code below.

https://github.com/BeycanPress/cryptopay-gateway-for-forminator

But if you don’t want to. I guess I can understand that.

That’s exactly what search console says. “do not lazy load images that should appear”

Make sure if I was still getting the current problem. I would have taken a screenshot or a video, but because of this problem I removed “img” and started using it as background. You can check it out if you don’t believe me.

https://beycanpress.com/how-to-create-a-paid-membership-site-with-wordpress/

All you need to do is put an image in the part that appears while the page is loading, this can be the featured image in a blog post or the image in the slider. Previously, I was only getting this warning in “native lazy load”. When I changed the Search Console data, when I checked everything again, it started to say the same warning in “breeze lazy load”. “Visible images cannot be loaded late”

What I mean by visible here is that it is visible when the page is loading

• This reply was modified 11 months ago by BeycanPress LLC.

When the page is first loaded, the top images are lazy loaded. This affects the first color appearance. Because it loads late. In other words, the area on the screen that is visible in general should not be loaded late. The images that appear when scrolling should be loaded late.

I have no problem on the PHP side, I have already done it, but I think we need to specify something on the React side. Because React crashes as soon as I select the field. Here below you can examine the repo. If you can provide unmified js code, I can handle it.

https://github.com/BeycanPress/cryptopay-gateway-for-forminator

I tried this but everytime have error ?? i cannot fixed. Mayeb you guys can do it.

Thanks for your reply, I’ve created a topic there. Actually I’m almost done, there’s just a routing problem with the old structure. I sent you an email so that you can list it in your plugin lists, but I’m not getting a response.

I guess in general Stellar WP doesn’t want to list external resources :D. Because I developed an integration in LearnDash, I could get a response before, but they don’t respond to mail to add to add-ons lists.

This is strange ??

I have tried many things but the page it is on also loads the redirected page. Is there a hook that can control the donate now button? We can disable the current process and open our payment modal first and submit the form after the payment is completed (backend control will be done in createPayment).

Here is repo, you can check it.

https://github.com/BeycanPress/givewp-cryptopay-gateway

• This reply was modified 1 year ago by BeycanPress LLC.

Thanks, so we need custom integration.

Ah yes, the problem was caused by another plugin, but this was appearing on the error screen. Therefore, there is no issue caused by MailPoet.

I just reverted back to the old version. I don’t know the reason for this, maybe it is due to the versions.

As I said, if “breeze lazy loader” is selected, it will give a warning in accordance with W3C standards. I conveyed this in the picture.

If “native lazy loader” is selected, Google will give a warning because it adds tags to the images while the page is loading at the very beginning of the screen.

I think both cases need to be investigated and resolved.

In case 1, the relevant data should be corrected using this site https://validator.w3.org/.

In the 2nd case, the relevant warning should be resolved by using this site https://pagespeed.web.dev/

? fixed everything about of speed in my site. Only this problem showing in W3C checker. Also, if i use native lazy loader “The loading of the large-scale image at the top of the page should not be delayed. He gives a warning in the style of spoiling large paint.” giving like that warning.

Yes, the Native one can be used. However, because it causes late loading in the images at the beginning of the page, google drops a lot of points in the speed test.

I finded, thanks.