About ACL / access control

I understand the need to enforce access control, but this can still be achieved without proxying through the main server, for example:

Using pre-signed URLs from S3 (time-limited access) Or integrating S3 with Amazon CloudFront and using signed URLs/cookies

This way:

Access control is preserved Files are delivered directly from S3/CloudFront The main server is completely bypassed for file delivery Why this feels unusual

The current design is a bit unusual because it combines:

the complexity of external storage (S3) with the load characteristics of local delivery (server as proxy)

So it doesn’t fully benefit from either approach.

So, as far as I’m concerned, the current S3 implementation, although technically working, is completely unusable because instead of reducing the server load, it actually increases it. It doesn’t really make any sense.

For further texhnical discussion please feel free to open a support request, comment section is for general questions.

it would be easily add a control filesize after the user select it, before upload, ex 100mb

javascriptdocument.getElementById(‘file-input’).addEventListener(‘change’, function(e) { const file = e.target.files⁰; const maxSize = 100 * 1024 * 1024; // 100MB });

if (file.size > maxSize) {
    alert('filesize bigger than (100MB)');
    this.value = ''; // resetta l'input
    return;
}

// proceedwith upload chunk...

This way you can also define multiple maxfileupload thresholds, differentiated by plan. A very useful feature with little effort.

Since you mentioned you’ll be revisiting the S3 implementation, I think this would be a good opportunity to handle file size validation directly at the storage level rather than relying on client-side JavaScript.

A more robust approach would be to enforce file size limits directly when uploading to Amazon S3. For example:

Use pre-signed POST policies with a content-length-range condition to strictly limit file size Validate Content-Type and other constraints at upload time Optionally reject oversized uploads before they even reach your application layer

this could be implemented cleanly using pre-signed POST policies, where the maximum file size is dynamically defined through a parameter (e.g. content-length-range).

This would allow:

Setting different file size limits depending on context or configuration Enforcing the limit directly at the storage level (not just in JavaScript) Avoiding unnecessary load on the main server

Compared to a simple client-side check, this approach is:

More secure (cannot be bypassed easily) More efficient (upload is rejected immediately if too large) More flexible (limit can be changed dynamically via a variable)

In this way, the file size limit becomes part of the upload configuration rather than something loosely enforced on the frontend.

Thanks

Not currently, we will add UTM builder, its in the roadmap.

Thanks Is it possible to store the business card into Apple Wallet / Google Wallet? How?

I’ve found the apple wallet thing. The google wallet?

No support yet for Google Wallet.

Please send an email from the form in my profile page if you would like to see those features soon.

Apologies for the delayed reply. We have now responded to your tickets.

Just go to System > Advanced > Embed Iframe > Allow

ok thanks

Hello,

Yes I would do that, please send me an email from the form in my profile page

You can do that with the extended license my friend.

I placed order for extended license, also purchased installation service. Please proceed with installation. thanks

Thank you so much, we will be taking care of that for you!

No worries we can provide you for a staging license, please send me an email from the form in my profile page for additional details.

I would like to use a server with LiteSpeed. Is it compatible?

Yes it is compatible with LiteSpeed

Today or tomorrow

We have release the new dashboard UI, but for the front end it will take 2-3 more days.

You can check the new UI on our demo

Please open a support ticket.

Can you please open a support ticket with a screenshot?

Hmmm, yes that is possible, please see this section https://docs.quickcode.digital/features/wordpress-integration/#using-main-domain

Please feel free to open a support request if you have any further questions, https://quickcodesupport.atlassian.net/servicedesk/customer/portal/3

Thank you so much for your help as always, I will use support for any questions.

Aplogies for the late reply, we missed your ticket in the queue.

We will get this resolved for you today.

Issue is resolved now.

It’s up to each developer to decide the price of their scripts.

The amount of features and tools offered here is very huge, we have been continuously updating the script every week for 4 years.

Now our team has expanded and we think it’s time for price change.

That’s right, everything has been updated except the main website theme. And you said at the beginning of January you would update it, and it’s already March and nothing has happened yet. The updates are in full swing, except for the one you mentioned, right?

It will come soon

Hello,

No, no third party payments, it’s self hosted.

Hey, sure thanks your message, all good here

Bonus without paying

Hello,

Yes it’s enough, but not all types are available in the regular license, many types are available in the extended license which can be bought from our website from just $250

See differences here: https://quickcode.digital/pricing

Sure, please send me an email from the form in my profile page

Done! I have send a message.

Email is sent

Yes