Complete Product Guide
Complete Product Guide
Complete Product Guide
Operational guide for configuration, first test, daily use and support boundaries.
This complete guide closes the gap between sales page and real use: for every product it states what to install, what to configure, how to test and where included support ends.
Installation guide
- Install one product at a time.
- Back up before booking, payment, ticketing or form products.
- Save license and verify updates.
- Run a first test on a private page.
- Document cookies, privacy and personal data before launch.
Visual quick path
Configuration guide
| Product | Type | Platform | Configuration focus |
|---|---|---|---|
| El Savio | AI chatbot | Joomla | Provider, persona, widget pages, privacy text |
| CMS Free AI Joomla | Content AI | Joomla | Provider, model, editor roles, budget |
| CMS Free AI WordPress | Content AI | WordPress | Provider, model, editor roles, budget |
| GMCsitemap | SEO sitemap | Joomla | Content types, exclusions, hreflang, IndexNow |
| AI Ticketing | Helpdesk | Joomla | Support channels, roles, SLA, email, privacy |
| GMC Tours | Tour booking | Joomla/WordPress | Products, availability, payments, emails |
| GMC Booking | Direct booking | Joomla/WordPress | Units, rates, availability, payments |
| Stripe Tax Calculator | Tax preview | Joomla | Stripe keys, tax regions, display rules |
| Stripe Actionlog Purchases | Purchase log | Joomla | Webhook, audit, retention |
| Auto User Account | User automation | Joomla | Stripe event, user group, welcome email |
| Stripe Webhook Delivery | Digital delivery | Joomla | Webhook secret, products, files, license gate |
| YOOtheme MCP | Layout control | Joomla/YOOtheme | Access, MCP client, backup policy |
| GMC Licenses | Licensing server | Joomla | Products, ZIP path, update feeds, license rules |
| GMC Facebook Feed Gallery | Social gallery | Joomla/WordPress | Page URL, token if Graph, cache |
| GMC Instagram Feed Gallery | Social gallery | Joomla/WordPress | URLs or Graph account, token, cache |
| GMC YouTube Gallery / Video Hub | Video hub | Joomla/WordPress | Video/playlist/channel, API key, privacy mode |
| GMC Lead Capture | Lead form | Joomla/WordPress | Fields, recipient, consent, SMTP |
| CMS Suite / Agency packs | Bundle | Joomla | Install one product at a time, test each product |
First test
- Use staging or a private page.
- Run the smallest possible real workflow.
- Check mobile and cache.
- Open support only with exact evidence.
Legal and support boundary
The customer remains responsible for backups, credentials, published content, third parties, privacy/cookie compliance, hosting and use of AI or payment providers. Mandatory consumer rights remain unaffected. Support & Legal
Support & Legal
For support, use GMC Trouble Ticket. Do not send passwords, API keys or unnecessary personal data.
Installation guide
Use the Joomla or WordPress installation guide linked from the CMS documentation hub. Install the correct ZIP, keep a backup, save the license key when requested and test on a private page before publishing.
Configuration guide
Open the product settings in the CMS administrator area. Check license, roles, cache, privacy, notifications and provider keys only when that product uses an external provider.
User documentation
These notes are written for site owners and editors: first test, daily use, support limits, privacy duties and what to include in a support ticket. They do not require editing source code.
FAQ
Do I need developer access?
No for normal use. Administrator access to the CMS is enough for installation, configuration, updates and first tests.
Can I install Joomla and WordPress packages interchangeably?
No. Use the Joomla ZIP on Joomla and the WordPress ZIP on WordPress. If a product exists on both platforms, follow the guide for that CMS.
Where do I configure license and updates?
Use the product settings or update/licensing screen in the CMS. Paid downloads and private updates require the active FuerteventuraTV license/download key.
What should I send to support?
Send product name, version, CMS, site URL, screenshot, exact error and what you already tried. Do not send passwords, API keys or tokens in the ticket.
