❓Frequently Asked Questions
Last updated
Last updated
When setting up your project on a subdomain, head to Site Settings > Setup > Subdomains and add your desired subdomain, such as app.domain.com.
You can configure overnight working hours by setting the start time to 08:00 PM and the closing time to 02:00 PM.
A common issue is incomplete email reception due to missing passwords or email addresses. Here's why and how to fix it. Please refer to this video for assistance.
This issue is quite common, often occurring due to incorrect or incomplete SMTP setup. To resolve it, please refer to our guide on configuring SMTP correctly.
On the frontend of the script, there's a Registration form for restaurants. When interested restaurants fill out the form, a restaurant owner account is automatically created, and an email is sent to them.
The restaurant owner can then log in using the email and password provided (the generated password can be changed on the profile page). From there, the owner can begin adding items and categories for their restaurant.
Initially, they are assigned to a free plan.
The site operates in a single language, which can be defined using the .env variable. It's easy to translate to any language since all strings are contained in a few files.
Web ( Storefront and Management System )
Framework: Laravel 10
Database: MySQL
Bootstrap: Based on AdminLTE 3
Mobile Apps ( User, Driver and Owner )
Framework: Flutter
Backend: Laravel API
Log in as admin.
Navigate to settings.
Delete the demo data.
Issue: When clicking on the update button, a blank screen with error 500 appears.
Cause: This often occurs due to insufficient available memory. You can verify this by checking the "Error" pages in cPanel.
Solution:
Access your cPanel.
Locate the "MultiPHP INI Editor" tool.
Select the project.
Set the memory_limit to 512M.
This allocation should be adequate.
This allocation should be adequate.
Issue: Clicking on the update button results in a blank screen with error 500. Enabling debug mode reveals the error "directory 'tmp/v3.0.x' not found."
Cause 1: This issue often occurs when the /tmp directory is not associated with the workspace.
Cause 2: Another common reason is an interruption during the download process, leading to the server creating a zip file with an incorrect structure. Subsequent attempts to re-download trigger the error.
Solution 1:
Access your cPanel.
Open File Manager.
Locate and open the .env file (it may be hidden, so ensure hidden files are enabled).
Add the following variable:
SELF_UPDATER_DOWNLOAD_PATH="/home/YOUR_WORKSPACE_NAME/tmp/"
Attempt the update process again.
Solution 2:
Contact your hosting provider to clear the contents of the system tmp folder, specifically the v3.x.x.zip file. If possible, you can also do this yourself.
A server restart often clears the tmp folder as well.
Solution 3:
Change the update server:
Access the .env file and modify the update path to a different update server.
Access your cPanel.
Open File Manager.
Locate and open the .env file (ensure hidden files are enabled).
Add the following variable:
SELF_UPDATER_REPO_URL=
Save the changes.
Solution 4:
Important: Backup all your project files in case something goes wrong.
Do all the steps in Solution 1, then try to update.
Afterward, navigate to your file manager at /home/YOUR_WORKSPACE_NAME/tmp/.
Inside this directory, you should find the files extracted for the update.
Access the folder, for example, v3.x.x, select all the files and folders, and click on the move button.
Select all the files and folder and click on the move button.
Move them to /public_html (if your project is in the root directory) or /public_html/sitedomain.com.
Problem: After an update, some users experience error 503 | Service not found.
Cause: This mostly happens because your PHP setup doesn't have the ZIP extension enabled.
Solution: You will need to enable the ZIP extension. This is the best and simplest guide we could find on how to enable the ZIP extension in cPanel.
Also, please contact your hosting provider to inquire about enabling the ZIP extension for you.
When the one-click update isn't functioning, updating via FTP is an alternative option.
We provide updated files publicly, which you can download from our platform.
Locate your current version and check if there's a corresponding zip file available for a newer version.
Download and extract the zip file locally on your system.
Connect to your FTP server and navigate to the root directory.
Drag and drop the folders from the extracted update to your FTP, overwriting the existing files.
Continue this process until you confirm that you've updated to the latest version.
Issue: You encounter a white screen displaying Error 500, similar to what's shown here.
Cause: The occurrence of this general error indicates a system malfunction resulting from various potential factors, including bugs or misconfigurations.
Option 1: Enable debug mode from admin
To diagnose the cause of this error, enable debug mode to uncover the underlying issue behind the 500 error. Here's how:
Log in as admin.
Navigate to settings.
Choose the setup tab.
Select APP_DEBUG.
Next, attempt to replicate the issue. With debug mode enabled, you'll receive more detailed information about the problem. If you comprehend the error message, you might be able to resolve the issue independently. Common problems include SMTP and Stripe misconfigurations. For these, check your settings to ensure that your entries are accurate.
Option 2: Enable debug mode from cPanel file manager
If you're unable to log in, you can manually activate debug mode.
Navigate to your cPanel file manager.
Locate the file named .env and open it for editing. Since this file is hidden, you may need to enable the option to show hidden file in cPanel.
Locate the line in the .env file that says "APP_DEBUG=false" and change the value from "false" to "true".
Now debug mode is enabled.
Now, try to replicate the issue. With debug mode enabled, you'll receive more detailed information about the problem. If you understand the error message, you may be able to resolve the issue independently. Common causes include SMTP and Stripe misconfigurations. For these, you can attempt to fix them yourself by verifying the settings in the admin panel.
Share a link to the error
If you encounter any other reported errors, please feel free to contact us and provide a link to the Flare Error of the problem https://help.natadtech.com. This will help us quickly address and resolve any issues you may be experiencing.
Here's how to acquire a link.
Issue: Attempting to migrate language settings could result in a 500 error. Additionally, certain items such as categories may be translated multiple times.
Cause: This occurs because the script did not consider the active status of objects. Consequently, it crashed when attempting to translate an inactive record.
Solution: If you have only a small amount of data affected, you can manually edit them through the admin interface. If you have a large amount of data,
Export the categories and items table from your database.
Perform a find and replace operation to ensure that the data appears in a normal format.
Remove categories and items from the database while ignoring foreign key constraints, then import them again. Alternatively, seek assistance from us.
After completing the steps mentioned above, proceed with the translation migration again. This time, it should proceed without any issues.
Error: After installation, upon opening your site, you encounter an error screen displaying a report similar to this one.
Reason: The most common cause of this error is incorrect database credentials, such as username or password, or incomplete setup of the database.
Solution:
Ensure that the information for your database in the .env file is accurate.
Delete the file named Installed located in the Storage directory.
Attempt the installation process again by accessing your website's domain followed by "/install" in your web browser.
If the issue persists, please submit a support ticket. If possible, provide us with your cPanel or Admin login details so we can investigate the problem further.
Error: Got an error message saying "PHP Fileinfo extension must be installed"?
Reason: The Intervention Image library, which is used for image processing, requires the PHP fileinfo extension to be installed and enabled on your server. This extension is necessary for Intervention Image to properly read and manipulate image files.
Solution: As depicted in the image, you can enable it from the PHP Selector. However, if there is no PHP Selector available, you should have access to your WebHost Manager.
In your WebHost Manager
Got it. Initially, we log in to WebHost Manager and follow this path:
Software >> EasyApache 4 >> Customize >> PHP extensions.
Then, we search for fileinfo and enable "phpx.x-php-fileinfo" for all versions. Finally, we click on Review and Provision.
This process enables the file extension for all PHP websites on the server
Let me know if you have any questions about this.
To enforce HTTPS for your site, log in as admin, then navigate to Site Setting and locate the Setup tab. In the App environment setting, set it to Production.
This ensures HTTPS is enforced at the project level. However, ensure you have a valid SSL certificate and that HTTPS enforcement is also configured at the hosting level.
If you encounter an error similar to this one
This message suggests that the INTL extension, or potentially another required extension, is not enabled on your server..
You can watch a helpful video tutorial on how to enable it. If you encounter difficulties, it's advisable to contact your hosting provider for assistance.
Issue: Error 500 occurs when attempting to add a new staff member.
Cause: The staff role is absent in older installations or databases.
Solution: Add it manually to the database.
