Installation - Grupo Chat

To get started, go to Codecanyon and download the latest version of the Grupo Chat Script. It should download a single ZIP file.

Decompress the contents of the zip file downloaded from CodeCanyon to a folder on your computer.
Decompress the contents of “fresh_installation.zip” file to a folder on your computer.
Create a database for Grupo on your web server, as well as a MySQL (or MariaDB) user who has all privileges for accessing and modifying it.
Upload the entire “chatscript” folder to the desired location on your web server:
1) If you want to integrate Grupo into the root of your domain (e.g. http://example.com/), move or upload all contents of the unzipped “chatscript” directory (excluding the “chatscript” directory itself) into the root directory of your web server.

2) If you want to have your Grupo installation in its own subdirectory on your website (e.g. http://example.com/chatroom/), create the chatroom directory on your server and upload the contents of the unzipped Grupo package to the directory.

Note: If you are using FTP client – FTP client has an option to convert file names to lower case, make sure it’s disabled.
Run the installation script by accessing the URL in a web browser. This should be the URL where you uploaded the Grupo files.
1) If you placed Grupo files in the root directory, you should visit: http://example.com/

2) If you placed Grupo files in its own subdirectory called chatroom, for example, you should visit: http://example.com/chatroom/
Follow the instructions & That’s it! Grupo Pro should now be installed.

Having trouble installing Grupo ?
Please feel free to contact us anytime. [email protected]. We are always here to help you out!

NGINX/Windows Server
If you are using Grupo with Nginx or Windows Server, you will need to setup Nginx specific rewrite rules or web.config file.

NGINX Rewrite rules

1) If you want to integrate Grupo into the root of your domain :

location / {
                try_files $uri $uri/ /index.php?$args;
            }
            location ~ /(fns|pages|include|layouts) {
              deny all;
              return 404;
        }
location ~* /(assets)/(.+)\.(jpg|jpeg|png|gif|svg|flv|mp3|jfif|wav|mp4|ogg|pdf|webm|bmp|webp|json|woff|woff2|ttf|eot|js|css|map)$ {
              allow all;
        }
location ~ /(fns|pages|include|layouts|assets)/(.+)\.[^\.]+$ {
            deny all;
        }

2) If you placed Grupo files in its own subdirectory

location /subfoldername/ {
               try_files $uri $uri/ /subfoldername/index.php?$args;
           }
location ~* /(subfoldername/assets)/(.+)\.(jpg|jpeg|png|gif|svg|flv|mp3|jfif|wav|mp4|ogg|pdf|webm|bmp|webp|json|woff|woff2|ttf|eot|js|css|map)$ {
             allow all;
       }
location ~ /(subfoldername/fns|subfoldername/pages|subfoldername/include|subfoldername/layouts|subfoldername/assets)/(.+)\.[^\.]+$ {
           deny all;
       }

Ensure that the location /subfoldername/ block is defined before the generic location / block in your Nginx configuration file. The order of location blocks matters, and Nginx will use the first matching location block.

Windows Server
Grupo, by default, uses an .htaccess file to manipulate how the web server serves files from your website. However, an .htaccess file cannot be read by a Windows server, so you will need what is called a “web.config” file to do the same things the .htaccess would on Linux servers. Upload the web.config file present in “ReadMe” folder.

Apache 2.2 or an earlier version : If your server is operating with Apache 2.2 or an earlier version and encountering a 500 internal error : 1) Download the “apache_older_version.zip” archive and extract its contents. 2) Upload and overwrite the “.htaccess” file located within the “Grupo” directory on your server. 3) Upload and replace the “.htaccess” file situated in the “assets” subfolder within the “Grupo” directory on your server.