How to Check Hosting Requirements for an Envato Script
Author: [TO BE CONFIRMED] · Published: October 25, 2026
Envato Market — including CodeCanyon for PHP scripts — sells thousands of ready-made applications: CRMs, job boards, chat systems, invoicing tools, and more. The listing page usually shows a “Software Version” line and a requirements section, and it is tempting to skim past them. Most failed installations trace back to exactly that moment: the server did not match what the script needed.
Checking requirements before you buy takes about fifteen minutes and saves hours of support tickets, refund requests, and rebuilds. Here is how to do it properly.
Start with the listing page, not the demo
Every CodeCanyon listing carries the same key facts, usually in the sidebar or near the bottom of the description:
Software version. The PHP and MySQL versions the script was built and tested against, for example “PHP 8.x, MySQL 8.x” or “PHP 7.x, MySQL 5.x”. Treat this as a range, not a suggestion.
Software framework. Laravel, CodeIgniter, or plain PHP. The framework matters because it brings its own requirements — Laravel, for instance, needs specific PHP extensions and a minimum PHP version of its own.
Files included. PHP, JavaScript, CSS, SQL. A SQL file usually means you will need to create a database and import it, or the installer will do it for you.
Last update. A script last updated years ago may list PHP 7.x as its current version. That does not mean it works on PHP 8.3; it may mean nobody has tested it there.
Item support. Most listings include six months of support from the author. Read what support covers: it typically includes answering technical questions and fixing reported bugs, but not customisation or installation services. If you need someone to install it, that is usually a separate arrangement.
If any of these fields is missing or vague, ask the author a question on the listing before buying. A clear answer before purchase is worth far more than a support ticket afterwards.
The five requirements to verify
1. PHP version
This is the most common mismatch. A script built for PHP 8.x may fail outright on PHP 7.4, and a script built for PHP 7.x may break on PHP 8.3 because of removed functions and stricter behaviour.
Check your hosting panel for the PHP version currently assigned to your domain, and whether you can change it. Good hosting lets you switch PHP versions per domain or per account. Then compare:
The script’s required version must be available on your hosting.
The version should still receive security fixes. As of October 2026, the PHP project supports PHP 8.2, 8.3, 8.4, and 8.5; PHP 8.2 security support ends 31 December 2026, and anything older is end of life. A script that requires PHP 7.4 is a script running on an unsupported language version, and that is a security decision, not just a compatibility one.
If the script needs an older PHP version than your other sites use, check whether your hosting supports different PHP versions per domain. If it does not, you may need a separate hosting account or a VPS for the script.
2. PHP extensions and functions
Beyond the version number, scripts commonly require extensions such as cURL, mbstring, OpenSSL, GD or Imagick, ZIP, and intl, and sometimes functions such as exec or file_get_contents on remote URLs. Some scripts need FFmpeg for video processing, or IonCube Loader for encoded files.
The listing’s documentation — usually inside the downloaded package, or linked from the listing — should name the required extensions. If it does not, check the author’s FAQ or ask directly. Then verify in your hosting panel (for example, cPanel’s “Select PHP Version” or “PHP Extensions” screen) that each extension is enabled. On shared hosting, some extensions can be enabled by the account holder; others need the provider. Confirm before buying, not after.
Also check for disabled functions. Some shared hosts disable functions a script relies on for security reasons. If a required function is on the host’s disabled list and cannot be enabled, the script will not work on that plan no matter what else matches.
3. Database: MySQL or MariaDB, and which version
Most PHP scripts need MySQL or MariaDB. Check:
Which database system the script expects, and the minimum version.
Whether your hosting provides it, and whether you can create databases and users yourself.
Whether the script needs specific database features, such as JSON columns (MySQL 5.7+), or a particular character set (utf8mb4 for full emoji and multilingual support).
MariaDB is generally compatible with MySQL for script purposes, but version numbers do not map one-to-one. If the script specifies MySQL 8.x and your host offers MariaDB 10.x, ask the author whether that combination is tested — do not assume.
4. Web server and URL rewriting
Most scripts expect Apache with mod_rewrite and .htaccess support, or Nginx with equivalent rewrite rules. If your hosting runs LiteSpeed, it generally honours .htaccess rules like Apache. If it runs Nginx, you may need to translate the rewrite rules yourself, and the author’s installer may not do it for you.
Check also for file upload limits and execution time limits. A script that imports large files or processes media may need higher upload_max_filesize, post_max_size, and max_execution_time values than a shared plan’s defaults. These are usually adjustable in the panel or via a php.ini / .user.ini file — confirm the mechanism exists before you need it.
5. Licence: Regular or Extended
Envato licences are per end product, and the distinction matters commercially:
Regular Licence: use by you or one client in a single end product which end users are not charged for.
Extended Licence: use in a single end product which end users can be charged for — for example, if visitors pay to access the script’s features.
A Regular Licence generally covers one website or domain; using the same purchase on multiple domains typically requires additional licences. If you charge users for access to the product itself, you need the Extended Licence. Read the licence terms on the listing and Envato’s licence FAQ before buying, and keep the purchase code safe — many scripts ask for it during installation to verify the licence, and authors may ask for it when you request support.
A pre-purchase checklist
Run through this before clicking Buy:
Note the script’s PHP version, framework, database, and extensions from the listing and its documentation.
Check your hosting panel: PHP version available, extensions enabled, database available, rewrite support.
Check the last update date and recent comments for reports of installation problems on current PHP versions.
Confirm the licence type you need (Regular vs Extended) for how you will charge users.
Confirm whether the author provides installation help, or whether you will do it yourself — and whether your hosting provider offers installation assistance for Envato scripts. [TO BE CONFIRMED: whether Offshore Hosting offers Envato script installation support.]
Make sure you have a backup of anything already on the target domain, and a staging or subdomain where you can test first.
If two or more requirements do not match, do not buy hoping it will work out. Either choose a different script, or choose hosting that matches — a shared hosting plan with selectable PHP versions and the extensions you need, or a VPS where you control the whole stack. Our guide to deploying a licensed PHP application safely walks through the installation itself once the requirements check out.
Red flags worth heeding
A listing that has not been updated in years but claims compatibility with the latest PHP. Unverified claims are not compatibility.
Requirements listed only inside the paid download. If you cannot verify requirements before purchase, ask the author first.
Comments full of “white screen” or “500 error” reports with no author response. That pattern usually means a PHP version or extension mismatch the author has not addressed.
A script that requires you to disable security features (such as turning off open_basedir or enabling dangerous functions) to work. That is a design problem, not a hosting problem.
Key takeaways
Read the listing’s software version, framework, and last update date before buying — not after.
Verify PHP version, extensions, database, rewrite support, and upload limits against your actual hosting panel.
PHP 8.1 and older are end of life; a script that requires them is a security risk, not just an inconvenience.
Choose the right Envato licence (Regular vs Extended) based on whether end users pay for the product.
If requirements do not match, change the hosting or change the script — do not buy and hope.
Sources
CodeCanyon, “Support Board — AI Chat and Chatbot and Ticket” (listing showing Regular/Extended licence terms and software versions) — https://codecanyon.net/item/support-board-chat-and-help-desk/20752085?s_rank=13
ServerAvatar, “Ultimate PHP Hosting Setup Checklist for Beginners” — https://serveravatar.com/php-hosting-setup-checklist/
SourceForest, “Stock Screener — System Requirements and Licence Notes” — https://www.sourceforest.net/codecanyon/item/stock-screener/18297488
Sources
{‘title’: ‘Support Board — AI Chat and Chatbot Ticket (CodeCanyon listing with requirements)’, ‘url’: ‘https://codecanyon.net/item/support-board-chat-and-help-desk/20752085?s_rank=13’}
Discovering your site has been hacked is a bad day that gets worse with the wrong first moves. This guide gives the order of operations: contain, preserve evidence, clean or rebuild, rotate every credential, and harden the site afterwards.
A 99.9% uptime claim allows about 43 minutes of downtime a month — but only if you know what counts, what is excluded, and how to claim. This guide decodes the SLA.
DDoS protection can absorb enormous attacks — and still leave your site down. This guide explains the attack types, the layers of defence, and the honest limits.