Website Demo

The website can be viewed here https://demo.mobileappformyrestaurant.co.uk/
You may register as a new user to try the full order flow.

Backend Admin Demo

The backend admin control panel can be viewed here https://demo.mobileappformyrestaurant.co.uk/admin65453
Username: kitchenlogin
Password: kitchenpassword

iOS App Demo

The iOs Demo App can be viewed here My Takeaway My Restaurant iOs App for Customers Demo

Android App Demo

The Android Demo App can be viewed here My Takeaway My Restaurant Android App for Customers Demo

Order Center App Demo

The Order Center Demo App can be viewed here My Takeaway My Restaurant Order Center Owner App Demo

Pre-requesties for setting up backend server

How To Install Linux, Nginx, MySQL, PHP (LEMP stack) on Ubuntu 18.04

Introduction

                                                $ ssh root@ip
                                                $ sudo apt update
                                                $ sudo apt install nginx

                                $ sudo ufw enable
                                $ sudo ufw allow 'Nginx HTTP'
                                $ sudo ufw allow ssh
                                $ sudo ufw allow http
                                $ sudo ufw allow https

You can verify the change by running:

$ sudo ufw status

									Output
									status: active

										To                    Action            From
										--                    ------            ------
										openSSH               ALLOW             Anywhere
										Nginx HTTP            ALLOW             Anywhere
										OpenSSH (v6)          ALLOW             Anywhere (v6)
                                        Nginx HTTP (v6)       ALLOW             Anywhere (v6)

With the new firewall rule added, you can test if the server is up and running by accessing your server’s domain name or public IP address in your web browser.

If you do not have a domain name pointed at your server and you do not know your server’s public IP address, you can find it by running the following command:

$ ip addr show eth0 | grep inet | awk '{ print $2; }' | sed 's/\/.*$//'

This will print out a few IP addresses. You can try each of them in turn in your web browser.

As an alternative, you can check which IP address is accessible, as viewed from other locations on the internet:

$ curl -4 icanhazip.com

Type the address that you receive in your web browser and it will take you to Nginx’s default landing page:

http://server_domain_or_IP

If you see the above page, you have successfully installed Nginx.

Step 2 – Installing MySQL to Manage Site Data

Now that you have a web server, you need to install MySQL (a database management system) to store and manage the data for your site.

Install MySQL by typing:

$ sudo apt install mysql-server

The MySQL database software is now installed, but its configuration is not yet complete.

To secure the installation, MySQL comes with a script that will ask whether we want to modify some insecure defaults. Initiate the script by typing:

$ sudo mysql_secure_installation

This script will ask if you want to configure the VALIDATE PASSWORD PLUGIN.

Answer Y for yes, or anything else to continue without enabling.

							VALIDATE PASSWORD PLUGIN can be used to test passwords
							and improve security. It checks the strength of password
							and allows the users to set only those passwords which are
							secure enough. Would you like to setup VALIDATE PASSWORD plugin?
                            Press y|Y for Yes, any other key for No:

If you’ve enabled validation, the script will also ask you to select a level of password validation. Keep in mind that if you enter 2 – for the strongest level – you will receive errors when attempting to set any password which does not contain numbers, upper and lowercase letters, and special characters, or which is based on common dictionary words.

							There are three levels of password validation policy:
							LOW    Length >= 8
							MEDIUM Length >= 8, numeric, mixed case, and special characters
							STRONG Length >= 8, numeric, mixed case, special characters and dictionary
                            Please enter 0 = LOW, 1 = MEDIUM and 2 = STRONG: 1 

Next, you’ll be asked to submit and confirm a root password:

							Please set the password for root here.
							New password:
                            Re-enter new password: 

For the rest of the questions, you should press Y and hit the ENTER key at each prompt. This will remove some anonymous users and the test database, disable remote root logins, and load these new rules so that MySQL immediately respects the changes we have made.

Note that in Ubuntu systems running MySQL 5.7 (and later versions), the root MySQL user is set to authenticate using the auth_socket plugin by default rather than with a password. This allows for some greater security and usability in many cases, but it can also complicate things when you need to allow an external program (e.g., phpMyAdmin) to access the user.

If using the auth_socket plugin to access MySQL fits with your workflow, you can proceed to Step 3. If, however, you prefer to use a password when connecting to MySQL as root, you will need to switch its authentication method from auth_socket to mysql_native_password. To do this, open up the MySQL prompt from your terminal:

$ sudo mysql

Next, check which authentication method each of your MySQL user accounts use with the following command:

mysql> SELECT user,authentication_string,plugin,host FROM mysql.user;

							Output
							+------------------+-------------------------------------------+-----------------------+-----------+
							| user             | authentication_string                     | plugin                | host      |
							+------------------+-------------------------------------------+-----------------------+-----------+
							| root             |                                           | auth_socket           | localhost |
							| mysql.session    | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |
							| mysql.sys        | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |
							| debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |
							+------------------+-------------------------------------------+-----------------------+-----------+
                            4 rows in set (0.00 sec)

In this example, you can see that the root user does in fact authenticate using the auth_socket plugin. To configure the root account to authenticate with a password, run the following ALTER USER command. Be sure to change password to a strong password of your choosing:

mysql> ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';

Then, run FLUSH PRIVILEGES which tells the server to reload the grant tables and put your new changes into effect:

mysql> FLUSH PRIVILEGES;

Check the authentication methods employed by each of your users again to confirm that root no longer authenticates using the auth_socket plugin:

mysql> SELECT user,authentication_string,plugin,host FROM mysql.user;

							Output
							+------------------+-------------------------------------------+-----------------------+-----------+
							| user             | authentication_string                     | plugin                | host      |
							+------------------+-------------------------------------------+-----------------------+-----------+
							| root             | *3636DACC8616D997782ADD0839F92C1571D6D78F | mysql_native_password | localhost |
							| mysql.session    | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |
							| mysql.sys        | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |
							| debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |
							+------------------+-------------------------------------------+-----------------------+-----------+
                            4 rows in set (0.00 sec)

You can see in this example output that the root MySQL user now authenticates using a password. Once you confirm this on your own server, you can exit the MySQL shell:

mysql> exit

							Note: After configuring your root MySQL user to authenticate with a password, you’ll no longer be able to access MySQL with the sudo mysql command used previously. Instead, you must run the following:
							$ mysql -u root -p
                            After entering the password you just set, you will see the MySQL prompt.

At this point, your database system is now set up and you can move on to installing PHP.

Step 3 – Installing PHP and Configuring Nginx to Use the PHP Processor

You now have Nginx installed to serve your pages and MySQL installed to store and manage your data. However, you still don’t have anything that can generate dynamic content. This is where PHP comes into play.

Since Nginx does not contain native PHP processing like some other web servers, you will need to install php-fpm, which stands for “fastCGI process manager”. We will tell Nginx to pass PHP requests to this software for processing.

$ sudo add-apt-repository universe

Install the php-fpm module along with an additional helper package, php-mysql, which will allow PHP to communicate with your database backend. The installation will pull in the necessary PHP core files. Do this by typing:

$ sudo apt install php-fpm php-mysql

You now have all of the required LEMP stack components installed, but you still need to make a few configuration changes in order to tell Nginx to use the PHP processor for dynamic content.

This is done on the server block level (server blocks are similar to Apache’s virtual hosts). To do this, open a new server block configuration file within the /etc/nginx/sites-available/ directory. In this example, the new server block configuration file is named example.com, which you need to replace with your domain name of your choice.

$ sudo nano /etc/nginx/sites-available/example.com

By editing a new server block configuration file, rather than editing the default one, you’ll be able to easily restore the default configuration if you ever need to.

Add the following content, which was taken and slightly modified from the default server block configuration file, to your new server block configuration file:

							server {
									listen 80;
									root /var/www/html;
									index index.php index.html index.htm index.nginx-debian.html;
									server_name example.com www.example.com;
									location / {
										try_files $uri $uri/ /index.php?/$request_uri;
								}
								location ~ \.php$ {
											include snippets/fastcgi-php.conf;
											fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
								}
								location ~ /\.ht {
											deny all;
								}
                            }

Please use the correct PHP Version number above based on your operating system on teh server. For example for Ubuntu 20.04 PHP version should be 7.4 instead of 7.2 in the file above.

Here’s what each of these directives and location blocks do:

After adding this content, save and close the file. Enable your new server block by creating a symbolic link from your new server block configuration file (in the /etc/nginx/sites-available/ directory) to the /etc/nginx/sites-enabled/ directory:

$ sudo ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/

Then, unlink the default configuration file from the /sites-enabled/ directory:

$ sudo unlink /etc/nginx/sites-enabled/default

$ sudo ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/

Test your new configuration file for syntax errors by typing:

$ sudo nginx -t

If any errors are reported, go back and recheck your file before continuing.

When you are ready, reload Nginx to make the necessary changes:

$ sudo systemctl reload nginx

This concludes the installation and configuration of your LEMP stack. However, it’s prudent to confirm that all of the components can communicate with one another.

Step 4 – Creating a PHP File to Test Configuration

Your LEMP stack should now be completely set up. You can test it to validate that Nginx can correctly hand .php files off to the PHP processor.

To do this, use your text editor to create a test PHP file called info.php in your document root:

$ sudo nano /var/www/html/info.php

Enter the following lines into the new file. This is valid PHP code that will return information about your server:

                            ?php
                            phpinfo();
                            

When you are finished, save and close the file.

Now, you can visit this page in your web browser by visiting your server’s domain name or public IP address followed by /info.php:

http://your_server_domain_or_IP/info.php

You should see a web page that has been generated by PHP with information about your server:

If you see a page that looks like this, you’ve set up PHP processing with Nginx successfully.

After verifying that Nginx renders the page correctly, it’s best to remove the file you created as it can actually give unauthorized users some hints about your configuration that may help them try to break in. You can always regenerate this file if you need it later.

For now, remove the file by typing:

$ sudo rm /var/www/html/info.php

With that, you now have a fully-configured and functioning LEMP stack on your Ubuntu 18.04 server.

Conclusion

A LEMP stack is a powerful platform that will allow you to set up and serve nearly any website or application from your server.

There are a number of next steps you could take from here. For example, you should ensure that connections to your server are secured. To this end, you could secure your Nginx installation with Let’s Encrypt. By following this guide, you will acquire a free TLS/SSL certificate for your server, allowing it to serve content over HTTPS.

Using Free Let’s Encrypt SSL/TLS Certificates with NGINX

It’s well known that SSL/TLS encryption of your website leads to higher search rankings and better security for your users. However, there are a number of barriers that have prevented website owners from adopting SSL.

Two of the biggest barriers have been the cost and the manual processes involved in getting a certificate. But now, with Let’s Encrypt, they are no longer a concern. Let’s Encrypt makes SSL/TLS encryption freely available to everyone.

Let’s Encrypt is a free, automated, and open certificate authority (CA). Yes, that’s right: SSL/TLS certificates for free. Certificates issued by Let’s Encrypt are trusted by most browsers today, including older browsers such as Internet Explorer on Windows XP SP3. In addition, Let’s Encrypt fully automates both issuing and renewing of certificates.

In this blog post, we cover how to use the Let’s Encrypt client to generate certificates and how to automatically configure NGINX Open Source and NGINX Plus to use them.

How Let’s Encrypt Works

Before issuing a certificate, Let’s Encrypt validates ownership of your domain. The Let’s Encrypt client, running on your host, creates a temporary file (a token) with the required information in it. The Let’s Encrypt validation server then makes an HTTP request to retrieve the file and validates the token, which verifies that the DNS record for your domain resolves to the server running the Let’s Encrypt client.

Prerequisites

Before starting with Let’s Encrypt, you need to:

Now you can easily set up Let’s Encrypt with NGINX Open Source or NGINX Plus (for ease of reading, from now on we’ll refer simply to NGINX).

Note: We tested the procedure outlined in this blog post on Ubuntu 16.04 (Xenial).

Step 1 - Download the Let’s Encrypt Client

First, download the Let’s Encrypt client, certbot:

                            $ apt-get update

                            //Command for Ubuntu 18.x
                            $ sudo apt-get install certbot
                            $ apt-get install python-certbot-nginx

                            //Command for Ubuntu 20.x
                            $ sudo apt install certbot python3-certbot-nginx
                        

Step 2 - Set Up NGINX

certbot can automatically configure NGINX for SSL/TLS. It looks for and modifies the server block in your NGINX configuration that contains a server_name directive with the domain name you’re requesting a certificate for. In our example, the domain is www.example.com.

1. Assuming you’re starting with a fresh NGINX install, use a text editor to create a file in the /etc/nginx/conf.d directory named domain‑name.conf (so in our example, www.example.com.conf).

2. Specify your domain name (and variants, if any) with the server_name directive:

3. Save the file, then run this command to verify the syntax of your configuration and restart NGINX:

$ nginx -t && nginx -s reload

Step 3 - Obtain the SSL/TLS Certificate

The NGINX plug‑in for certbot takes care of reconfiguring NGINX and reloading its configuration whenever necessary.

1. Run the following command to generate certificates with the NGINX plug‑in:

                            $ sudo certbot --nginx -d example.com -d www.example.com

2. Respond to prompts from certbot to configure your HTTPS settings, which involves entering your email address and agreeing to the Let’s Encrypt terms of service.

When certificate generation completes, NGINX reloads with the new settings. certbot generates a message indicating that certificate generation was successful and specifying the location of the certificate on your server.

                            Congratulations! You have successfully enabled https://example.com and https://www.example.com

                            -------------------------------------------------------------------------------------
                            IMPORTANT NOTES:

                            Congratulations! Your certificate and chain have been saved at:
                            /etc/letsencrypt/live/example.com/fullchain.pem
                            Your key file has been saved at:
                            /etc/letsencrypt/live/example.com//privkey.pem
                            Your cert will expire on 2017-12-12.

Note: Let’s Encrypt certificates expire after 90 days (on 2017-12-12 in the example). For information about automatically renenwing certificates, see Automatic Renewal of Let’s Encrypt Certificates below.

If you look at domain‑name.conf, you see that certbot has modified it:

                            server {
                                listen 80 default_server;
                                listen [::]:80 default_server;
                                root /var/www/html;
                                server_name  example.com www.example.com;

                                listen 443 ssl; # managed by Certbot

                                # RSA certificate
                                ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
                                ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot

                                include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot

                                # Redirect non-https traffic to https
                                if ($scheme != "https") {
                                    return 301 https://$host$request_uri;
                                } # managed by Certbot
                            }

Step 4 - Automatically Renew Let’s Encrypt Certificates

Let’s Encrypt certificates expire after 90 days. We encourage you to renew your certificates automatically. Here we add a cron job to an existing crontab file to do this.

1. Open the crontab file. Use the nano editor if prompted. Generally its option 1

$ crontab -e 

2. Add the certbot command to run daily. In this example, we run the command every day at noon. The command checks to see if the certificate on the server will expire within the next 30 days, and renews it if so. The --quiet directive tells certbot not to generate output.

0 12 * * * /usr/bin/certbot renew --quiet

3. Save and close the file. All installed certificates will be automatically renewed and reloaded.

Summary

We’ve installed the Let’s Encrypt agent to generate SSL/TLS certificates for a registered domain name. We’ve configured NGINX to use the certificates and set up automatic certificate renewals. With Let’s Encrypt certificates for NGINX and NGINX Plus, you can have a simple, secure website up and running within minutes.

Robust Database designs explained

Installing PHP MYADMIN

sudo apt update // to update your packages
sudo apt install phpmyadmin // to install phpmyadmin
apache2 // (direct press enter)
sudo ln -s /usr/share/phpmyadmin /var/www/html // to create shortcut key for phpmyadmin at /var/www/html/
Now open phpmyadmin in the browser // You can login by username and password, which you set before.

Next step is to create a database and name it as you like. Then select the database and import the data .sql file using the file included in your folder.

1. Login to your FTP using Filezilla or other FTP you have.

2. Based on the kind of hosting, you may need to use SFTP or normal FTP Connection. If you use a cloud server + Filezilla, select SFTP & enter the same SSH credentials which you use to login in the terminal.

3. The website code is built on codeigniter which uses PHP as their base framework.

4. Now upload this folder in your ftp public folder. For Cloud hosting it is generally /var/www/html and for shared hosting or cpanel hosting it is public_html ( you can make folder with name like Admin and upload the content of the public-html and not the folder ).

5. Once uploading is finished below are the parameters to change,

1. Open Application -> Config -> config.php. This is the file where you need to change all settings.

2. Change the database credentials in database.php file located under application > config

3. Change below items

- System is integrated with stripe, please login to stripe.com and create yours account with your valid credentials and that will get you a publishable key and secret key. Please replace the above parameter.

- System is integrated with pusher (https://pusher.com) to make sounds and alerts when a new order is received in the backend admin. For more details on how to generate the Pusher App ID, App Key and App Secret, please refer to their website.

- System is integrated with onesignal, https://onesignal.com for more details for pricing , up to 10,000 push messages you can send for free every month, which is humble enough for startup restaurants. Please replace your ids in below code once you have configured the Appstore and Firebase Projects to generate your app keys and push certificates. The admin key is for the owner app and user key is for the customers app.

- For sending emails you need to change the below parameters. To begin with you can use Gmail account and it looks like this:

- You can use any SMTP server of your choice. Amazon also offers SES (Amazon Simple Email services) which is cheaper and can be used to send large amounts of emails.

- Google key is used to measure distance of delivery location from your deliverable limit. Open https://developers.google.com/ and create google key. Please enable below permission to the key.

Some important items before setting up

In case you face problem uploading images please give permission by typing below command

                        cd ~
                        web_folder='/var/www/html/'
                        chown www-data:www-data $web_folder -R; find $web_folder -type f -print0 |xargs -0 chmod 644;

                        find $web_folder -type d -print0 |xargs -0 chmod 755;

                        sudo chown -R root:root  /var/www/html
                        systemctl restart php7.3-fpm.service

                        Edit php.ini

                        sudo nano /etc/php/7.3/fpm/php.ini
                        Please change below items
                        memory_limit = 256M
                        Post_max_size = 200M
                        upload_max_filesize = 100M
                        max_execution_time = 3600

                        Edits in NGINX

                        sudo nano /etc/nginx/nginx.conf
                        (Copy the following line below http parenthesis)

                        client_max_body_size 100M;
                        Restart Nginx
                        sudo service nginx reload

Language Translations
To change the language translations, please look for the relevant language file you wish to edit in the application > language folder

$ xcode-select --install

                       $ npm install -g ios-sim
                       $ brew install ios-deploy

$ adb devices

Setting up Order Center Mobile App for Admin

---

Below are the edit's required in the project.

Open Src ->environments > environment.prod.ts & environment.ts both in Visual Code Editor environment.prod.ts has all produciton deployment configuration and environment.ts has all development configuration.

                                baseurl: 'https://website.co.uk/',
                                imagepath: 'https://website.co.uk/uploads/',
                                onesignalkey: 'xxxxxxxxxxxxxxxxx', // For user push notification
                                firebasekey: 'xxxxxxxxxxxxxxxxx', // For user push notification

                                                   

c. Now let's run the command to install all dependencies.

3. npm install

Connecting a receipt printer

---

Configured a 58mm or 80mm Thermal Receipt Printer

The app is configured to use a 58mm or 80mmm thermal printer receipt printing from the admin backend. Everytime you receive an order, you will hear an alert with the order summary. Once you click on the order summary, it should automatically print the receipt for you. The printer must be installed for this to happen.

You would need to buy a suitable 58mm or 80mm thermal printer if you wish to print receipts for all your orders. You can also buy a 80mm receipt printer but you would need to edit the design slightly to adjust the printing margins so the receipt prints perfectly.

You can do this by editing the file order.php located in \application\views\admin path. (Line number 53 onwards)

We can also customise the receipts for you if you wish, this will cost an additional support and customisation fee. Please get in touch with us should you wish to take our paid services for customisation and support.

How the printer works

First you would need to install the printer on your laptop or desktop computer which you will use for the admin backend.
You need to be on the orders tab for you to hear the ringer alert and print the receipt.

There is a print icon next to all orders which when pressed will print the receipt. You can also automate this by enabling "kiosk printing" ( print automatically ) for Google Chrome on Windows

You can find help online on how to enable kiosk printing on google and test it with your printer.

Here is a Real Demo of the printer in action.

Installing the Driver Plugin (Sold Seperately)

---

**Please note you need to purchase the Driver Plugin Seperately.

The driver login demo can be seen on the Order Center App. Please select the Driver Login button and use the following details to login as a driver:
Username: 01234567890
Password: 123456

Once you have purchased the Driver Plugin, simply replace the Order Center App folder with the files provided with your Driver Plugin Purchase. If you have made changes to the order center app, and do not wish to replace the whole folder, you can simply replace these 3 files from the driver plugin in the below path in Order Center Owner App:
Files to replace: login.page.html, login.page.scss, login.page.ts
Copy files from: Driver Plugin Foler > src > app > login >
Paste files to: Order Center Project Folder > src > app > login >
That's you done!

Now you can create drivers from the admin and drivers can login to the order center app for the following features:

• - View All Orders or Only the Orders Assigned to the Driver
• - Call Customer if needed
• - Get Directions and Navigate to Customer Address
• - Mark the Order as Delivered once done.

Support Desk

---

Please remember you have purchased a very affordable Mobile App with backend and you have not paid for a full-time web design agency. Occasionally we will help with small tweaks, but these requests will be put on a lower priority due to their nature. Support is also 100% optional and we provide it for your connivence, so please be patient, polite and respectful.

Please visit our profile page or ask question @v1technologies

Support for my items includes:

• * Responding to questions or problems regarding the item and its features
• * Fixing bugs and reported issues
• * Providing updates to ensure compatibility with new software versions

Item support does not include:

• * Customization and installation services
• * Support for third party software and plug-ins

Before seeking support, please...

• * Make sure your question is a valid Apps Issue and not a customization request.
• * Make sure you have read through the documentation and any related guides before asking support on how to accomplish a task.
• * Try disabling any active plugins to make sure there isn't a conflict with a plugin. And if there is this way you can let us know.
• * If you have customized your theme and now have an issue, back-track to make sure you didn't make a mistake. If you have made changes and can't find the issue, please provide us with your changelog.
• * Almost 80% of the time we find that the solution to people's issues can be solved with a simple "Google Search". You might want to try that before seeking support. You might be able to fix the issue yourself much quicker than we can respond to your request.
• * Make sure to state the name of the App you are having issues with when requesting support via codecanyon.

Files & Sources

---

Included in V1Tech-My Restaurant -Kitchen Mobile App User

These is the primary ionic project source code

• 1. src folder - Source code, themes & Controller with all business logic
• 2. resources folder - static assets, Kindly replace this for your branding.
• 3. package.json - All modueles required to set up this project are included here.

Included in Web and Admin Folder

These is the primary Backend Code-Ignitor PHP Project.

• 1. application -> controller -> RestAPI.php has list of all API's End-point.
• 2. application -> views -> GUI for Admin panel.
• 3. application -> config -> All required configuration's options.

Included in V1Tech-My Restaurant - Kitchen Mobile App Admin

These is the primary ionic project source code

• 1. src folder - Source code, themes & Controller with all business logic
• 2. resources folder - static assets, Kindly replace this for your branding.
• 3. package.json - All modueles required to set up this project are included here.

Included in V1Tech-My Restaurant - Database Folder & Database with Sample Data Entry

This are 2 Database

• Database Folder - This is emepty database, you can use this for production.
• Database with Sample Data Entry - We have shipped sample items and their images for you to demo your investors or client's.

Troubleshooting & FAQs

---

Overview

As with any other development project, it is likely that you may find errors or compatibility issues based on various factors like version of ionic, version of xcode, third party plugin updates, version of android studio, other compatibility issues.

Most of these issues can be resolved by simple google search because the components we have used are very generic. We have listed below some issues that have been reported and resolved

---

Can this be installed on a SHared Hosting with and without Cpanel access?

Yes, the product is designed to work with Shared Hosting too.

The way to do this is to copy the source codes to the public_html folder. Then create a database and import the database and connect it to the files using the steps above.
Follow the steps above to make any changes and edits in the environments file. Thats you done!

---

Black Screen when running the iOs App

We have been informed that this is usually because the "GoogleService-Info.plist" is required in some instances to run the ios app.

This can be resolved by creating the ios app and then importing this file from Google Firebase into the following path

platform > ios > ProjectName > Resources

---

Not hearing the alert sound in Admin Orders Tab

This is most commonly because the Pusher Service is not configured properly.

Since this is a Third Party Tool, please follow their latest guidelines on how to create and generate the API Keys.

Remember to use the correct API keys in the config file as mentioned above.

---

Inner Pages on Website or Admin Not Working

The above documentation is based on nginx, and as you may be aware, ".htaccess" does not work very well with nginx.

You may need to tweak the location / { parameter in your block configuration file as appropriate based on your server settings.
Dont forget to reload the nginx after making the changes.

On shared hosting (cpanel hosting): If you are able to open the home page but not able to open the inner pages, this is most commonly an issue with your .htaccess file in your root folder. Please try the RewriteBase / in your .htaccess file located in the main root folder. See example below:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]

---

Changes not visible even after uploading the files.

if you are using any DNS management service like "Cloudflare", you may not see the changes because of the cache issues.

You may need to Purge Cache from your Cloudflare dashboard for your domain.

Remember to purge everything before you refresh the page to see the changes.

---

Loader takes time to hide (Please wait loader). Can I hide the "Please wait" loader on the home screen?

The app is designed to load settings and products data in real-time from the server. This real time data loading can be disabled

You may wish to Disable Real Time Data Load from your apps home screen.

This will make the "Please Wait Loader" disappear and will not appear everytime.

---

Product Variations and Extra Options Feature (example extra cheese)

The app supports unlimited item variations and addon customisations

You may add variations to a product like Small Medium Large or Extra options like Extra cheese, onions etc.

These can be paid or free. You can set a price or set 0.00 as a price.

---

Data takes time to load

That is a good news actually :)

Data load times depend on how many users are using the app at the same time and what kind of server your app is hosted on.
Our app is hosted on a demo server and there are many users testing the demo app at any given time, hence the slight delay.

Please note Shared Server Hosting is generally slower than dedicated servers.

---

Does the app have any thermal receipt print feature?

Yes, the product is designed to work with any 58mm or 80mm thermal receipt printer. You can always change the design to other receipt roll size.

The way the receipt printer works is everytime you have an order, it will ring an alert in teh admin system.
Once you click on OK for the order, it will print the receipt automatically using the printer you have installed.

---

How to change the Category Names and links on the website home page?

To change the category images or names or links on the home page, please edit the index.php file located in application/views/web

Does not allow to select delivery address on website during checkout

This problem arises if you do not use a proper Google API Key of if the address entered does not fetch the Lattitude and Longitude properly using Google API

Please ensure you have used a working API key and enabled Google Geolocation and Geocoding in your API Keys (With billing entered in the Google Console)

Also please ensure you change the service postcode in the Contact Us section in admin settings. This is used as the point from where distance is calculated.

You will also need to add the delivery charges, because unless you have a delivery charge setup, it may show "Too Far"

---

How to add a sub-category?

To add a subcategory, please add a category first, then click on the category and you will see an option of adding a sub-category on the top green button

---

Version History (Changelog)

---

You can find the version history (changelog.txt) file on V1Tech-My Restaurant My Delivery App.zip folder or you can check changelog on theme sale page.

Once again, thank you so much for purchasing this theme. As I said at the beginning, I'd be glad to help you if you have any questions relating to this theme. No guarantees, but I'll do my best to assist. If you have a more general question relating to the themes on codecanyon, you might consider visiting the forums and asking your question in the "Item Discussion" section.

---

Changelog

                                -----------------------------------------------------------------------------------------
                                Version 5.0 - 24 Mar 2021
                                -----------------------------------------------------------------------------------------

                                - SQUARE payment gateway added on public demand
                                - Offers are now be time based too. You can add Date + Time Validity
                                - Website Collection / Pickup Service bug fix
                                - If Google API is not enabled, it will now show an alert "Unable to calculate distance"
                                - Sub-Category System Added. Now you can add subcategories too.
                                - Variations and Extra Addon Options can be FREE or Paid
                                - Add more than 1 Admin Users


                                -----------------------------------------------------------------------------------------
                                Version 4.1 - 12 Mar 2021
                                -----------------------------------------------------------------------------------------

                                - Item Variations Feature (Example: Small, Medium, Large) when ordering from the customer app
                                - Extra Addons and Options (Example: Extra cheese or toppings) when ordering from the app
                                - Variations and Addoon Options on Order Center when adding an order
                                - Variations and Addoon Options on Backend Admin When Adding an Order
                                - Variations and Addoon Options on Website Orders
                                - Variations and Extra Addon Options can be FREE or Paid


                                -----------------------------------------------------------------------------------------
                                Version 3.0 - 10 Mar 2021
                                -----------------------------------------------------------------------------------------
                                - Collection Service Bug Fixed (Was not showing collection option even if enabled from admin)
                                - Sliding Banner Bug on Website Fixed (Banners were overlapping instead of sliding)


                                -----------------------------------------------------------------------------------------
                                Version 2.0 - 28 Feb 2021
                                -----------------------------------------------------------------------------------------

                                - Worldwide Currency Support in Settings Section
                                - Change to Miles or Kilometres in Settings Section
                                - Custom Push Notifications - Send custom notifications to boost your orders


                                -----------------------------------------------------------------------------------------
                                Version 1.4 - 05 Feb 2021
                                -----------------------------------------------------------------------------------------

                                - Delivery Times based on the opening days and opening hours
                                - Pre-Odrer Feature - Allow customers to pre-order for next working day


                                -----------------------------------------------------------------------------------------
                                Version 1.3 - 3 Jan 2021
                                -----------------------------------------------------------------------------------------

                                - Improvement Changes
                                - Bug Fixes
                                - Added Driver Commission Feature
                                - Added Auto update feature from backend which keep prompting users to update app.
                                - Added CMS Option


                                -----------------------------------------------------------------------------------------
                                Version 1.2 - 25 Dec 2020
                                -----------------------------------------------------------------------------------------

                                - Added Festival Effects in Admin.
                                - Finished first 1,000 Orders


                                -----------------------------------------------------------------------------------------
                                Version 1.1 - 20 Dec 2020
                                -----------------------------------------------------------------------------------------

                                - Implemented Kitchen App which notify Kitchen in realtime when order arrives.
                                - Implemented Realtime notifcation to customer with deals and offer's.
                                - Implemented Google API for restriction of bookings which are out of delivery area.
                                - Implemented Multiple address for users to select from the last available address.
                                - Backend API Performance tweaks

                                      

Migration / Update Guide

---

Please remember to Backup Your Project before you do anything else just in case things do not go as planned.

Since there has been quite a few updates in all sections of the website and app, the best way to update is to replace all the files if you have not done any customisation yourself.
Remember not to change or replace the Environment, Config and Database Files as that would make everything stop working.

We recommend you download / backup your database, then replace the files and sql file. Once replaced, upload the data again in the required tables. This is the easiest method to update the codes.

For Square Payment Gateway, please add the relevant API keys in the config file in Application > Config folder.

---

Copyright and license

---

Code released under the Single License use. Violation or Infringement of the licence and copyright may lead to disputes. For multiple uses, please buy additional copies of the software.

For more information about copyright and license check V1 Technologies.