For successful installation you will not need to change any code from .env file. Please maintain the documentation about the installation and activation properly.

Please kindly ready and underatdn my commet: i am ot seeing any SYSTEM KEY in the described .env file. that place at which the system key ss supposed to be is blanc.

eg:

SYSTEM_KEY=”system key was supposed to be here”

But this is what i see: SYSTEM_KEY=””

??

Thank you for your comment, and we apologize for the delayed response due to the Eid Ul-Fitr 2026 vacation period.
We are noting your point with importance. We will take care of it in future update.

Are you giving your word that you will resolve this in the coming update? Many updates have passed, but the problem is still the same.

Nope we are not giving word that it will available on next upcoming update but this is already on our task-list and will available future update.

This task had been pending for many years. Still you are not sure

Item updates are driven by overall customer demand and are prioritized based on broader user needs, not individual urgency.

If your requirement is time-sensitive, you’re free to implement it on your end. The full source code is provided specifically to allow customization according to your needs.

This is not the feature, this is bug ,

We respectfully disagree with the claim that the item does not follow proper standards. Items published on a commercial marketplace must pass strict guidelines and review processes, and no product can be approved without maintaining the required coding and structural standards.

It is possible that there has been some misunderstanding or confusion regarding the functionality or implementation. We would be happy to review all of your concerns and clarify them for you.

To ensure you receive proper assistance, we kindly invite you to open a ticket with our support team so we can discuss your questions in detail and help resolve the matter. You can reach our support team here: http://support.activeitzone.com

Hello,

Thank you for your reply.

As suggested, I have already opened a support ticket with your team to review the issues I described. The ticket ID is #4104, created yesterday (8:26 PM). At the moment I have not yet received a response.

I will wait for your technical team to review the concerns I mentioned regarding the missing controllers referenced by routes and the overall project structure.

However, if these issues are inherent to the current architecture of the product and cannot be resolved within the core package, I would still like to discuss the possibility of a refund.

Thank you.

Thank you for your message. We will review your support ticket and assist you there accordingly.

However, we have a small question for clarification. The item already includes a complete installation system along with proper documentation, so normally there is no need to install it directly from the codebase.

Could you please let us know why you are attempting to install the item from the codebase? The standard installation process should handle the setup and activation smoothly without requiring manual codebase installation. This will help us better understand your situation and guide you properly.

Hello,

Thank you for the response.

The reason I am looking at the codebase directly is because I need to evaluate and maintain the application as a developer. Even if an installation wizard exists, it does not replace the need for a coherent and functional codebase.

When reviewing the project, I noticed that basic Laravel commands such as `php artisan route:list` fail because many routes reference controllers that are not present in the core package. It appears these controllers belong to addons that are sold separately, yet the base code still contains references to them. This leaves the application in a state where the framework itself cannot properly bootstrap without missing dependencies.

From a development and maintenance perspective, this is problematic. A Laravel project should at least be internally consistent even if certain features are optional modules.

Additionally, the project structure does not follow the typical Laravel deployment approach where the web server document root points to the `public` directory, which raises concerns about standard deployment and security practices.

Because of these issues, I am unable to properly evaluate or work with the project as expected. For this reason, I would still like to proceed with a refund, as the product in its current state does not meet the expectations I had for a Laravel-based application.

Please let me know how we can move forward with the refund process.

Yes, this item includes several addons, and this is a standard and widely used approach in modern software development, especially for large systems. The main product is designed as a core platform, while addons are developed to extend specific features or functionalities based on different user requirements.

However, it is important to clarify that purchasing additional addons is completely optional. The main item works independently and can be used without any issue even if you do not purchase any of the addons. Addons are simply provided for users who need extended or specialized features beyond the core system.

To ensure transparency and help users make informed decisions, we have clearly explained the available features, addons, and system structure on the main product page. In addition, we have provided a complete live demo so visitors can explore the system interface, features, and workflow before making a purchase. This process is designed to give users a clear understanding of the product and its capabilities in advance.

Our goal is always to provide users with the best possible browsing and evaluation experience so they can verify whether the item meets their requirements before purchasing.

That said, we would be happy to review your situation in more detail. Please feel free to continue the discussion through our support portal, where our support engineers will carefully review your queries and guide you toward the most suitable solution.

Thank you for the clarification.

I understand the concept of a core system with optional addons, and I agree that this is a common approach for extending functionality. My concern, however, is not the existence of addons but the state of the core codebase itself.

The base package currently contains route definitions that reference controllers which are not included in the core product. Because of this, standard Laravel commands such as php artisan route:list fail due to missing classes. This indicates that the core system still references components that are not present unless additional addons are installed.

In a modular architecture, the core system should remain internally consistent and operational even when optional modules are not installed, typically by conditionally registering routes or services only when the corresponding module exists.

Because of this issue, I am unable to properly evaluate or work with the project in its current state. For this reason, I would prefer to proceed with a refund rather than continuing with technical troubleshooting.

Please let me know the appropriate steps to initiate the refund process.

Thank you.

Thank you for your continued communication and for taking the time to clearly explain your use case.

After carefully reviewing the entire conversation, we would like to highlight an important point regarding the license under which this item was purchased.

The Regular License allows the item to be used for a single personal or private project only. In other words, it is intended strictly for personal use and does not cover usage related to businesses, clients, commercial operations, or services provided to third parties. This limitation is part of the standard licensing terms defined in the marketplace.

Based on the details you shared throughout this discussion, it appears that the intended use of the product goes beyond what the Regular License permits. For example:

You mentioned the need to evaluate and maintain the application as a developer.

You discussed topics such as deployment, development workflows, maintenance practices, and security considerations, which are typically associated with professional or production environments.

Your detailed technical assessment of the Laravel architecture and deployment patterns indicates that the system is being evaluated for commercial or professional usage.

Activities such as deploying, customizing, or maintaining the software for business purposes, client projects, or commercial services fall outside the scope of the Regular License.

Thank you for your understanding.

Hi please check quickly the error it is giving Request Not Found its urgent i am paying my developer and my time is getting waste here

ticket #4099

Already your ticket is responded. Please check this screenshot https://prnt.sc/D-foAK7PIOVW

Replied very late now i have provided what they need please check and update quickly as i have waited a lot for simple queries time is very precious please

As weekly off days, our support system is offline on Friday and Saturday. Due to the urgency, we could nevertheless attend on Saturday (GMT+06).

it is actually very urgent

According to your support ticket it has been seen that your ticket is replied and our support team demand a file but did not the files yet.

i have shared and they have confirmed that they have received the file please refresh your system and check again

Please continue on ticket and reply as soon as possible there.

yes already replied them back long back still no update