Campaign payments can generate an invoice, but it depends on how the payment is made.

If the campaign donation is completed through an external payment gateway, the system creates an invoice and the payer can access it from the payment success page or from their payment history.

If the donation is made using the internal wallet/points balance, the current flow records the payment successfully but does not automatically create an invoice.

So the short answer is: yes for gateway/card payments, but not automatically for wallet/points-based campaign donations.

super

Thank you very much for your kind words and for your continued support. I’m really glad to hear that you enjoy the product and the ongoing updates.

Regarding LiveKit, I tested the integration again very recently and it is working correctly on my side. I also made a few small improvements to the integration to further stabilize it.

However, to understand why it is not working on your installation, I need to review your specific configuration. Issues such as a black screen, camera/microphone not initializing, or WebRTC connection failures are usually related to server configuration, SSL setup, LiveKit credentials, or environment settings.

I also noticed that no support ticket has been created regarding this issue yet. Without reviewing the installation details, it is unfortunately not possible to determine the exact cause.

Please create a support ticket so I can investigate the problem properly:

In the ticket, please include:

- Your website URL
- Admin panel access
- Server or hosting panel access (if possible)
- A screenshot of your LiveKit configuration

Once I have these details, I can review your setup and help identify why LiveKit is not working on your server.

Thank you again for your feedback and support. I’m looking forward to helping you resolve this quickly.

Hello,

Thank you for your message.

Please note that the item comment section is not suitable for handling technical support requests. For technical questions or configuration assistance, kindly open a support ticket through our support system so our team can properly review your case.

Regarding your question about the Voting and Q&A sections during live broadcasts, we are already working on a significant improvement for this area. In the upcoming update, the live broadcast interface (especially on mobile devices) will receive important usability enhancements to improve the viewing experience and layout behavior.

Once you open a ticket, we can also provide more detailed guidance based on your setup.

Thank you for your understanding.

No problem, I can wait. I know that you always make great updates, so I’ll wait for the development. Please don’t forget to include in the update that the search bar is missing in Giphy. You can’t search for a GIF even with Giphy integration, the search bar doesn’t appear. You can’t search for GIFs, and this can be quite a serious issue. Thank you very much.

Hello,

Thank you for bringing the Giphy search issue to my attention. I appreciate you taking the time to report it.

For the best support and faster improvements, I kindly recommend sharing this type of feedback as soon as you notice it, rather than waiting until an update cycle or shortly before a new release. Reporting issues early helps me review, verify, and address them more efficiently, which ultimately results in a more stable and polished experience for everyone using the platform.

I have noted the missing search bar in the Giphy integration, and I will review this together with the other improvements planned for the upcoming update.

Thank you again for your helpful feedback and your continued support. It is always appreciated.

Hello,

Thank you for your message.

To properly investigate why the Maintenance Mode feature is not working on your installation, we need to review your server environment and configuration. The fastest way to handle this type of technical issue is through our official support system.

When submitting your ticket, please include the following information if possible to help us investigate the issue more quickly:

- cPanel login details or
- FTP access details
- The URL of the page where the issue occurs

Once the ticket is submitted, our team will review the issue in detail and help you determine why Maintenance Mode is not functioning as expected.

Thank you for your cooperation.

Best regards.

Thanks

I saw your ticket and your reset is done.

Thank you, have a good day.

I perfectly understood your answer. I asked about this because most other content sales scripts include features like right-click blocking and blocking the inspection of source code, regardless of the browser. We know that preventing content downloads or screenshots is still impossible at the moment, but adding these right-click blocking features makes easy copying more difficult for any novice user. The watermark in the footer is almost unnecessary since a simple cut of the footer section would solve that.

Hello MarcosBrito,

Thank you for your detailed clarification. I understand your perspective.

You are absolutely right about one thing: right-click blocking and basic source protection mainly act as a deterrent for inexperienced users. However, it is also important to approach this topic realistically from a security and product quality standpoint.

There is currently no reliable method, at browser level, to truly block Inspect, View Source, Network tab access, screenshots, or asset downloads. Any script that claims to “block inspection regardless of browser” is only applying superficial JavaScript restrictions. These can be bypassed in seconds by disabling JS, using DevTools directly, viewing network requests, or simply accessing the asset URL.

Because of that, Dizzy avoids presenting cosmetic front-end restrictions as a real security feature. My philosophy is to focus on:

- Server-side protection - Controlled media access logic - Storage isolation (local / S3 / Wasabi etc.) - Watermarking at render level - Monetization flow integrity

Regarding watermark placement: The watermark system is not limited to a footer overlay. It can be rendered directly on the media itself during output. If someone crops the footer, the embedded watermark remains part of the image. Of course, extreme editing is always possible, but the goal is traceability and ownership visibility, not absolute prevention.

That said, your suggestion is valid from a UX deterrence standpoint. A configurable global right-click restriction can be added as an optional setting for administrators who prefer that behavior. I simply avoid marketing it as a security layer because it would create a false sense of protection.

Dizzy is built more around sustainable protection architecture rather than visual blocking tricks. But feedback like yours is valuable, especially when it comes to user expectations in this niche.

If you have any other technical concerns or feature comparisons in mind, feel free to share them. I’m always open to constructive discussion.

Best regards.

Thank you very much for the explanations.

Hello,

Thank you for your message.

I have checked your account details. Please note that your support period expired on 23/05/2024.

According to Envato’s support policy, technical assistance and issue resolution are provided only to customers with an active support license. Since your support period has ended, I am unfortunately unable to process or investigate ticket #pTEiS6WZ at this time.

If the matter is urgent, you may renew your support package via your Envato account:

1. Log in to CodeCanyon
2. Go to Downloads
3. Locate the purchased item
4. Click Renew Support

Once your support has been renewed, please reply to your existing ticket and I will prioritize your request.

Thank you for your understanding.

Hello,

The automation model you described represents an advanced, enterprise-level growth layer rather than a basic platform feature.

Such systems require dedicated event architecture and performance safeguards. They must be implemented modularly to preserve core stability.

Dizzy’s evolution follows a structured scalability strategy. Growth tools are evaluated within that framework.

Appreciate your input.

Hello,

Thank you for your detailed feedback and for sharing your ideas regarding the automation (flow) system. Trigger-based media sales, automated messaging sequences, and behavior-driven actions such as follow or visit-based triggers can indeed create strong retention and monetization strategies.

In order to properly evaluate and prioritize such feature requests, I kindly ask you to submit your idea through our official feature suggestion platform:

Once submitted, other users will be able to vote on the suggestion. The number of votes helps me objectively measure how many customers truly need this functionality. Features that receive higher demand and broader community support are prioritized and added to the development roadmap accordingly.

This approach ensures that product improvements are driven by real community needs rather than individual requests alone, allowing for a more strategic and sustainable development process.

Thank you again for your valuable contribution.

Hello,

Dizzy already supports a structured role and permission architecture for Users, Creators, and Agencies. The current registration flow is intentionally simplified to reduce friction and keep onboarding flexible for different platform models.

Role-based entry at sign-up is a strategic UX decision, not a missing capability. Structural enhancements are evaluated carefully to maintain balance, performance, and flexibility for all platform owners.

Dizzy is designed to scale thoughtfully, not impulsively.

Thank you for the suggestion.

Hello,

Thank you for your suggestion regarding EPOCH billing support for adult payment processing.

I truly appreciate feature requests like this, as they help shape the product roadmap in the right direction. To properly evaluate demand and prioritize development in a fair and transparent way, I kindly ask you to submit this suggestion through our official feature request platform:

Once submitted, other users can vote on the idea. The number of votes helps me clearly understand how many customers actually need this integration. Features with higher demand are prioritized accordingly and added to the update roadmap.

This ensures that new integrations are implemented based on real community needs rather than individual requests alone.

Thank you again for your contribution and support.

thanks for the info, if it was in the documentation I wouldn’t have asked.

Hello,

I understand your point.

Different scripts are built with different monetization architectures. Some systems are designed around direct wallet top-ups, while this script is structured around a controlled points and transaction flow model for security, accounting consistency, and platform balance.

Feature differences between products are normal and depend entirely on how the core system is engineered. The current wallet and campaign structure works as designed and is not a malfunction.

If a platform requires a different financial flow, that would involve a structural modification rather than a simple setting change.

Thank you for your feedback and understanding.

Best regards.

Thank you, have a nice day.

Hello,

Thank you for your detailed questions. I’m happy to clarify everything clearly.

Bunny Storage can be integrated seamlessly for both photos and videos. Once the Bunny Pull Zone and CDN URL are configured correctly, videos can stream directly from Bunny’s infrastructure. In this setup, media files are delivered through Bunny’s CDN, ensuring stable and efficient performance.

Regarding the PWA, the system already includes a site-wide Progressive Web App that can be installed on both Android and iPhone devices. However, separate branded PWA applications for individual creators are not available by default. Creating a dedicated PWA per creator would require additional development, such as assigning a separate domain or subdomain, implementing dynamic manifest configuration with custom branding elements, and setting up creator-specific notification handling. While technically possible, this falls under custom development rather than standard functionality.

In terms of notifications, creators receive in-app notifications for subscription sales and tips. Web push notifications are also supported if they are enabled in the admin panel and the user has granted browser permission. For paid post purchases, creators receive an in-app notification and an email notification flow is available; however, there is no dedicated web push trigger by default. Product sales are processed successfully, but a specific push notification for the creator is not included as a built-in feature.

For subscribers using the PWA, push notifications are supported when a creator goes live, provided that the push system is active and the user has granted permission. However, automatic web push notifications for standard new content posts are not currently included as a built-in feature and would require additional customization.

Once you join the Dizzy family, please remember to create a support ticket through the official support panel for any technical questions or configuration guidance. After purchase, full assistance is provided throughout the setup and configuration process.

Best regards.

so for individual PWA what would be the cost can you please reply me on kaamaapp@gmail.com coz i am not finding from here to mail you

Hi Botor,

Thank you very much for your kind words and for taking the time to share your feedback. I truly appreciate your support and I’m very happy to hear that you are satisfied with the new features.

Regarding ticket #ngc8WvEg, I completely understand that you need assistance. Please don’t worry, I will review your ticket as soon as possible and provide you with a detailed response directly through the support system.

Thank you again for your continued trust and support.

Best regards

Hi,

Thank you very much for your feedback and for taking the time to test the demo.

The public demo environment occasionally experiences high traffic and concurrent testing, which can affect responsiveness at certain times. It is configured primarily for demonstration purposes and is not running on a dedicated, high-performance production infrastructure.

That said, performance optimization is an ongoing priority in Dizzy’s development roadmap. Each update includes improvements in database query efficiency, asset loading, caching mechanisms, and overall front-end responsiveness. The script itself is built on a scalable architecture, and when deployed on a properly configured hosting environment with optimized PHP and server settings, it performs significantly faster and more smoothly.

Thank you again for your valuable observation.

Regards

and set redirection when buying a frame with a zero account to buy points

thanks