Mayosis 5.4.7 – Digital Marketplace WordPress Theme

Mayosis is a marketplace-style WordPress theme for selling digital products. I reach for it when the core is Easy Digital Downloads (EDD): downloads, licensing, discounts, purchase history, and a storefront that feels closer to Envato/CreativeMarket than a generic shop.

It shines when you need “catalog + product pages + filters + author/vendor feel”.
It’s not the cleanest choice for content-heavy sites, and I don’t treat it like a lightweight blog theme. It’s a shop front with opinions.

How it works internally (the parts that actually matter)

Mayosis is a theme layer on top of an eCommerce engine. In most real installs that engine is EDD (sometimes WooCommerce appears in demos, but the “digital marketplace” mechanics are usually EDD-first).

What lives where:

• Digital products are EDD “Downloads” (download post type). Pricing, files, licensing fields = stored as post meta.
• Checkout / cart logic is plugin territory. The theme mostly styles it and overrides templates.
• Theme templates sit in /wp-content/themes/mayosis/.
  If the theme overrides EDD views, you’ll typically see an edd_templates/ folder (or similar). That’s where “why does my download page look different?” is decided.
• Settings split:
  • EDD settings: Downloads → Settings
  • Theme settings: usually Customizer or a theme options panel (commonly Redux-based). Those values are in wp_options.
• Page builder content (if your demo uses WPBakery/Elementor): stored in the page content in the DB. That’s why demo pages can look “half imported” when the builder plugin is missing.

Assets and performance reality:

• Mayosis storefront pages run heavier queries (tax filters, author/vendor blocks, “featured” sliders). That’s fine, but it means object cache and proper image sizing matter more than on a brochure site.

Where it breaks in the wild (root cause → fastest fix)

Checkout doesn’t update / buttons do nothing

Root cause: optimization plugins breaking EDD’s AJAX flow or jQuery order.

What I check:

• DevTools → Network: requests hitting admin-ajax.php during add-to-cart / checkout.
• DevTools → Console: jQuery is not defined, blocked scripts, or gateway JS errors.

Fixes that work fast:

• Disable “Delay JS” for EDD-related scripts (exclude by URL/handle you see in Network), commonly:
  • edd-ajax.js (or any easy-digital-downloads front script)
  • payment gateway scripts (Stripe/PayPal) that must execute immediately
• Don’t cache checkout pages. Exclude URLs like:
  • /checkout/
  • purchase confirmation / success page
  • account pages if they show dynamic purchase data

Demo import looks wrong: missing sections, odd homepage, broken sliders

Root cause: the required builder/plugin bundle isn’t fully active, or imported menus/widgets didn’t assign.

Fix:

• Activate the theme’s required plugins (builder + companion plugins).
• Re-assign menus: Appearance → Menus → Manage Locations
• If builder styling is off: regenerate builder CSS (Elementor: Elementor → Tools → Regenerate CSS & Data; WPBakery sites usually need a cache purge + re-save the page).

“Downloads” pages 404 after migration or enabling vendors

Root cause: rewrite rules not flushed for the download post type (or vendor endpoints if you’re using FES-style submissions).

Fix:

• Settings → Permalinks → Save Changes once.
• If you’re using vendor dashboards/endpoints, I also re-save EDD permalinks/settings and purge caches.

Store pages are slow even on decent hosting

Root cause: heavy WP_Query + unindexed meta queries (common with “filter by price/category/featured” blocks) and oversized images.

Two practical moves:

• Add object cache (Redis) if you have lots of downloads.
• In DevTools → Network: look for huge images loading on archive pages; fix by regenerating thumbnails and enforcing sensible sizes in theme blocks.

Activation, updates, and the boring truth

Mayosis will usually run without a key, but you lose the comfortable pipeline: one-click updates, demo import access, vendor support. My copy is activated and working (personally checked), so you’re not fighting the “locked demo” problem.

Updates:

• Best path: normal dashboard update (when connected).
• Manual path: upload the new theme ZIP via Appearance → Themes → Add New → Upload, or replace via SFTP.
  Any edits inside the parent theme get overwritten. Real fix: child theme for template overrides and functions.php changes.

You can find detailed instructions on how to update a theme or plugin on this page.

Practical FAQ (things devs actually ask)