Skip to Content
Updating Venom

Updating Venom

Use this guide when you already run Venom and receive a new package (for example 1.1.0). Always back up your site and database (or commit in Git) before replacing files.

1. Replace the theme folder

Copy the new themes/venom from your download over the existing folder in your Paymenter project:

paymenter/themes/venom/

Do not delete your theme.php custom values manually in the admin — Paymenter stores theme settings in the database; replacing files keeps those settings as long as setting keys stay compatible.

2. Core file: app/Classes/helpers.php

Venom 1.1+ relies on a small addition in the Paymenter core: the global helper landing_marketplace_href(), which powers marketplace CTAs on the landing page, footer, cart, and related widgets.

If your ZIP includes an app folder

Some packages ship:

app/
  Classes/
    helpers.php

Your Paymenter root (next to artisan and composer.json) already has app/Classes/helpers.php.

  • Recommended: open both files in a diff tool. Merge in the new landing_marketplace_href function (and anything else your release notes say) without discarding your local changes to helpers.php.
  • Not recommended: blindly overwrite the whole app directory — you may remove customizations or other extensions’ expectations.

If you choose to replace only app/Classes/helpers.php from the package, make a backup of your current file first, then copy the packaged file into:

paymenter/app/Classes/helpers.php

After merging, ensure you still have only one definition of marketplace_url() and one of landing_marketplace_href() (wrapped in function_exists as in the vendor file).

3. Build theme assets

From the Paymenter project root:

npm run build:venom

Deploy the updated public/venom/** output if your server does not build on deploy.

4. Clear Laravel caches

php artisan view:clear
php artisan cache:clear
php artisan config:clear

In production you may re-run php artisan config:cache / view:cache after checks.

5. Admin: new setting (1.1.0)

Under Venom theme settings: Landing — Marketplace link (optional override).

  • Leave empty → marketplace index when Vortexus is installed, otherwise /marketplace.
  • Fill in a path (e.g. /store) or full URL → all those CTAs use your value; navigation stays in the same tab.

6. Sanity checklist

  • Homepage: primary marketplace button goes to the URL you expect.
  • Login/register on a phone: form is near the top; no huge image before fields.
  • Logged-in dashboard: hero, widgets, sidebar look correct; no errors in storage/logs.

If login fails with a missing App\Actions\Auth\Login class, your core may be out of sync with the Paymenter version the theme was tested against — restore or add that class from the official Paymenter repository or your support channel.

For what changed in each version, see Changelog.

InstallationChangelog