Templately plugin review and common issues

Templately loads templates from its cloud API. If loading fails: (1) check your internet connection; (2) verify Templately.com is accessible from your server — some hosting firewalls block external API requests; (3) clear Elementor editor cache (Elementor → Tools → Regenerate CSS); (4) log out of Templately and log back in — authentication tokens can expire; (5) check if a security plugin is blocking the Templately API request; (6) try from a different browser to rule out local browser cache issues.

After saving a template to Templately cloud: (1) refresh the Templately library panel (close and reopen the template library modal); (2) if still missing, log out and log back in to force a fresh library sync; (3) verify you have sufficient cloud storage — if the save appeared to succeed but 200MB limit was reached, the template may not have been stored; (4) check the template save by visiting Templately.com directly and logging into your account to see the saved templates.

Template import issues typically occur when: (1) a required plugin or Elementor Pro feature is not active on the destination site; (2) the template uses custom fonts that are not loaded on the destination site; (3) the template was created with a different Elementor version and some deprecated features no longer work; (4) global fonts and colors in the template differ from the site’s Elementor global settings. After import, manually review each section and replace any missing assets (fonts, images) with local alternatives.

In the Elementor editor with the page design complete: (1) click the save icon or navigate to Elementor → Templates; (2) in the Templately panel, look for a “Save to Cloud” option; (3) name the template and select whether to save to personal My Cloud or a team workspace (if you have a Pro plan with team features); (4) the template is uploaded to Templately’s cloud and immediately available on any WordPress site with Templately installed and logged into the same account. Select specific sections or full pages to save.

Team template sharing requires Templately Pro with team workspace features. Create a team workspace in your Templately account settings and invite team members by email. Any template saved to the team workspace (rather than personal My Cloud) is accessible to all workspace members when they open Templately in their WordPress installations. Each team member must have a Templately account and the plugin installed. The team workspace approach standardizes template usage across an agency.

Templately and Starter Templates serve different primary use cases. Starter Templates provides complete website packages (all pages, settings, demo images) designed for getting a new site running quickly. Templately focuses on individual section and page templates with cloud storage for reuse and team sharing. For launching a new client site from scratch, Starter Templates is more efficient. For agencies with established design standards who want to share approved component templates across team members, Templately’s cloud model is more valuable.

If you cancel a Templately Pro subscription, your account reverts to the free tier. Templates stored in your personal My Cloud remain accessible up to the free tier’s 200MB storage limit. Templates exceeding the free limit may become inaccessible until storage is reduced or the subscription is renewed. Team workspace templates are accessible only while a Pro subscription is active. It is advisable to export or download important templates locally (as Elementor JSON exports) before canceling the subscription to ensure access regardless of Templately’s service.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.