<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SHA REEQ Blog]]></title><description><![CDATA[SHA REEQ Blog]]></description><link>https://shareeq.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:02:50 GMT</lastBuildDate><atom:link href="https://shareeq.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[7 Codecanyon Installation Mistakes That Break Laravel Apps and How to Avoid Them]]></title><description><![CDATA[Buying a Codecanyon script is easy. Getting it to run reliably on your server is where most projects go wrong. I am SHA REEQ, a full stack developer in…]]></description><link>https://shareeq.hashnode.dev/7-codecanyon-installation-mistakes-that-break-laravel-apps-and-how-to-avoid-them</link><guid isPermaLink="true">https://shareeq.hashnode.dev/7-codecanyon-installation-mistakes-that-break-laravel-apps-and-how-to-avoid-them</guid><dc:creator><![CDATA[SHA REEQ]]></dc:creator><pubDate>Mon, 26 Oct 2026 14:54:00 GMT</pubDate><content:encoded><![CDATA[<p>Buying a Codecanyon script is easy. Getting it to run reliably on your server is where most projects go wrong.</p>
<p>I am SHA REEQ, a full stack developer in Hyderabad. Over the last few years I have installed, repaired and customised dozens of Laravel, WordPress and Flutter scripts for clients. Most failures I see are not caused by bad code. They are caused by small setup decisions that look harmless at the beginning.</p>
<p>Here are seven mistakes that regularly break Laravel based Codecanyon applications, and the exact checks I run before I call an installation complete.</p>
<h2>1. Running the installation before checking the PHP version</h2>
<p>A script that asks for PHP 8.2 will often still open its installer on PHP 7.4. The installer then fails later, usually during dependency installation, with errors that look unrelated to the PHP version.</p>
<p><strong>What to check</strong></p>
<ul>
<li>Read the documentation for the minimum and maximum PHP version.</li>
<li>Confirm the CLI version and the version used by the web server. They are often different.</li>
<li>Check the required PHP extensions before you upload anything.</li>
</ul>
<p>On shared hosting, the CLI version is usually the one that matters for Composer. If they differ, you can end up with a vendor folder that works in the terminal and fails in the browser.</p>
<h2>2. Uploading the source code through FTP without excluding vendor and node_modules</h2>
<p>Most Codecanyon downloads include a vendor folder and sometimes a node_modules folder. Uploading thousands of small files over FTP is slow, and it often fails silently part way through.</p>
<p><strong>A better approach</strong></p>
<ul>
<li>Upload the compressed source archive.</li>
<li>Extract it on the server with SSH or cPanel file manager.</li>
<li>Run composer install on the server so dependencies match the server PHP version.</li>
<li>Run npm install and npm run build only if the script ships a frontend build step.</li>
</ul>
<p>This is faster and it removes a large class of missing file errors.</p>
<h2>3. Forgetting to create the .env file and generate the app key</h2>
<p>A fresh Laravel application will not boot without an environment file and an application key. The error is usually a missing APP_KEY message or a blank page.</p>
<p><strong>The correct order</strong></p>
<pre><code>cp .env.example .env
php artisan key:generate
</code></pre>
<p>Then update the database details, application URL, mail settings and any third party API keys. Generate the key after the .env file exists, otherwise the command has nothing to write to.</p>
<h2>4. Using the wrong database credentials or importing the wrong SQL file</h2>
<p>This is the most common cause of a failed installation. Many scripts ship several SQL files, for example a base schema, an optional module schema and a demo data file.</p>
<p><strong>Check these details</strong></p>
<ul>
<li>The database name, username, password and host in .env.</li>
<li>The database prefix required by the script. Some installers expect a custom prefix such as web_.</li>
<li>Whether the SQL file matches the version of the script you downloaded.</li>
<li>Whether the import finished without errors. A partial import often looks like a successful one.</li>
</ul>
<p>If the installer has its own setup wizard, let it create the tables instead of importing SQL manually. Doing both can create duplicate tables or missing relationships.</p>
<h2>5. Skipping the storage and cache permissions</h2>
<p>Laravel writes to storage and bootstrap/cache. When those folders are not writable, you get errors about the log file, the framework cache or the compiled views.</p>
<pre><code>chmod -R 775 storage bootstrap/cache
</code></pre>
<p>On shared hosting, the folders usually need to be writable by the web user. On a VPS, the ownership matters more than the permission number. Set the owner to the user that runs PHP, not to your root or FTP account.</p>
<h2>6. Not setting the application URL correctly</h2>
<p>The APP_URL value in .env should match the real domain, including https if the site uses SSL. A wrong value causes broken redirects, mixed content warnings and broken password reset links.</p>
<pre><code>APP_URL=https://example.com
</code></pre>
<p>After changing it, clear the caches:</p>
<pre><code>php artisan optimize:clear
</code></pre>
<h2>7. Testing the app only on the homepage</h2>
<p>The homepage working does not mean the installation is complete. Background jobs, email delivery, file uploads, payment webhooks and scheduled tasks often fail silently.</p>
<p><strong>A proper handover test should cover</strong></p>
<ul>
<li>Registration and login.</li>
<li>Creating and editing a record.</li>
<li>Uploading a file.</li>
<li>Sending an email with a real mailbox.</li>
<li>Running the queue worker.</li>
<li>Running the scheduler once.</li>
<li>Checking the log file for errors.</li>
</ul>
<h2>A short pre launch checklist</h2>
<p>Before I hand over any installed script, I run through this list:</p>
<ol>
<li>PHP version and required extensions confirmed.</li>
<li>.env created and app key generated.</li>
<li>Database imported or migrated cleanly.</li>
<li>Storage and cache permissions set correctly.</li>
<li>APP_URL matches the live domain.</li>
<li>Caches cleared.</li>
<li>Core flows tested on mobile and desktop.</li>
<li>Logs checked for errors.</li>
<li>SSL installed and forced.</li>
<li>Backup configured before any custom changes.</li>
</ol>
<h2>Why installation support is worth it</h2>
<p>A Codecanyon script is a starting point, not a finished product. The buyer still needs the server prepared, the database configured, the application tested and often the design or workflow adjusted to match the business.</p>
<p>If you want help with a specific script, I handle Laravel, WordPress, React and Flutter installations, including VPS setups, error fixing and custom modifications. You can see my installation service at <a href="https://mshariqq.github.io/codecanyon.html">SHA REEQ Codecanyon support</a> or view my full portfolio at <a href="https://mshariqq.github.io/">mshariqq.github.io</a>.</p>
<h2>About the author</h2>
<p>I am SHA REEQ, a full stack developer in Hyderabad, India with more than 10 years of experience. I build custom WordPress sites, Shopify stores, Laravel applications and Flutter apps, and I have delivered more than 50 projects for clients across India, the UK, the UAE and the US. You can find my work on <a href="https://github.com/mshariqq">GitHub</a>, my <a href="https://mshariqq.github.io/">portfolio</a> and my <a href="https://www.upwork.com/freelancers/~0142acdc12184086c7">Upwork profile</a>.</p>
]]></content:encoded></item><item><title><![CDATA[Buying a script on Codecanyon is easy. Getting it live without 500 errors, blank pages, and security holes is not.]]></title><description><![CDATA[I'm SHA REEQ, full-stack developer in Hyderabad. I've installed and fixed 100+ Codecanyon scripts, Laravel, WordPress, React, Flutter. This is the exact…]]></description><link>https://shareeq.hashnode.dev/buying-a-script-on-codecanyon-is-easy-getting-it-live-without-500-errors-blank-pages-and-security-holes-is-not</link><guid isPermaLink="true">https://shareeq.hashnode.dev/buying-a-script-on-codecanyon-is-easy-getting-it-live-without-500-errors-blank-pages-and-security-holes-is-not</guid><category><![CDATA[Codecanyon]]></category><dc:creator><![CDATA[SHA REEQ]]></dc:creator><pubDate>Sun, 25 Oct 2026 20:32:24 GMT</pubDate><content:encoded><![CDATA[<p>I'm SHA REEQ, full-stack developer in Hyderabad. I've installed and fixed 100+ Codecanyon scripts, Laravel, WordPress, React, Flutter. This is the exact checklist I use to go from download to production in <del>90 minutes.<br /><br />## Before you start<br /><br />- Server requirements: Read the item's requirements. Most Laravel apps need PHP 8.1+, Composer, MySQL 8, Redis optional.<br />- Backups: Snapshot files + DB before touching anything.<br />- Access: cPanel or VPS SSH, FTP/SFTP, DB user with privileges.<br /><br />## 1) Prepare the server<br /><br />- Create a subdomain or folder: <a href="http://app.yourdomain.com">app.yourdomain.com</a><br />- PHP selector to required version<br />- Enable required extensions: bcmath, intl, gd, zip, mbstring, openssl, pdo_mysql<br />- Set upload_max_filesize and post_max_size as per script<br />- For Laravel: set APP_ENV=production later, keep APP_DEBUG=false<br /><br />If you're on a tight budget, cPanel works fine for most scripts. For heavy apps, use a VPS.<br /><br />## 2) Upload &amp; extract<br /><br />- Upload zip via cPanel File Manager or scp<br />- Extract to public_html/app or public_html<br />- Set permissions: folders 755, files 644. Never 777.<br /><br />## 3) Database setup<br /><br />- Create new DB + user in cPanel &gt; MySQL Databases<br />- Import provided SQL if any, or run migrations<br />- Update .env with DB credentials, app URL, mail settings<br /><br />Common gotchas:<br />- Wrong DB host, some hosts use localhost, some use private IP<br />- Missing collation, use utf8mb4_unicode_ci<br /><br />## 4) Install &amp; migrate<br /><br />Laravel:<br />```bash<br />composer install --no-dev --optimize-autoloader<br />php artisan migrate --force<br />php artisan storage:link<br />php artisan config:cache<br />php artisan route:cache<br />```<br /><br />WordPress:<br />- Upload to public_html, create DB, run installer<br />- Replace default theme files with custom child theme if needed<br /><br />## 5) Fix the usual errors<br /><br />- 500 error: Check storage/logs/laravel.log, .env APP_KEY, permissions<br />- Blank page: Enable debug temporarily, check PHP error log<br />- CSRF token mismatch: Clear cookies, check APP_URL<br />- Missing vendor: Run composer install<br />- Imagick / GD missing: Install extension in cPanel<br /><br />## 6) Security hardening<br /><br />- Move .env out of public root if possible<br />- Disable directory listing<br />- Set strong admin passwords, 2FA<br />- Install SSL via Let's Encrypt<br />- Add basic firewall rules, limit login attempts<br />- Schedule daily backups<br /><br />## 7) Go live checklist<br /><br />- Test key flows: register, login, payment, email<br />- Speed test with Lighthouse, enable caching<br />- Set up error monitoring: Sentry or Bugsnag<br />- Document admin credentials securely<br /><br />## When to get help<br /><br />If you bought a script and it's stuck on a white screen, throwing SQL errors, or needs custom modules, I offer Codecanyon installation and fixes with 30-day support.<br /><br />See plans and order: <a href="https://mshariqq.github.io/codecanyon.html%5C">https://mshariqq.github.io/codecanyon.html\</a><br />Portfolio: <a href="https://mshariqq.github.io">https://mshariqq.github.io</a><br />Upwork: &lt;<a href="https://www.upwork.com/freelancers/">https://www.upwork.com/freelancers/</a></del>0142acdc12184086c7&gt;</p>
]]></content:encoded></item></channel></rss>