Support email: . Please avoid sending passwords, API keys or customer data in your first message.
Helpful details in a report
The LIO plugin name and its exact build/version.
Your WordPress, WooCommerce and PHP versions where relevant.
Expected vs. actual behavior and steps to reproduce it.
Whether the issue occurs on a staging copy or a live site.
Please do not send passwords, API keys, customer records or production backups through an initial contact message.
Common questions
Are there public stable plugin releases?
Product Units Free 1.1.0 is a public LIOSFERA ZIP; Schema Diagnostics Free 0.5.2 is ready to submit, while LIOSFERA Order Diagnostics 0.1.0 is publicly available on WordPress.org.
Do the plugins require LIO CMS?
No. LIO Plugins are independent WordPress/WooCommerce products.
Is LIOSFERA Cloud collecting site data?
Cloud is not launched or attached to these public plugin offerings. Core functionality is intended to operate locally.
Can I get installation assistance?
Yes. Email and include the plugin name and environment versions. Any custom integration or support agreement is discussed separately.
LIOSFERA Product Units Free 1.1.0 is a vendor-hosted download. LIOSFERA Schema Diagnostics Free 0.5.2 is published on WordPress.org; LIOSFERA Order Diagnostics 0.1.0 is published on WordPress.org.
ORDER DIAGNOSTICS / USER FEEDBACK
Found a bug or have an idea?
Help us make the WordPress.org release more reliable. Feedback is voluntary and no store data is sent automatically.
Public support forum
Questions, reproducible bugs, compatibility with WooCommerce, and suggestions that can be discussed publicly.
Do not publish customer data, screenshots of orders with personal details, API tokens or credentials.
For issues that should start as a private conversation, or ideas you would rather send by email.
The email opens in your own mail app. No in-site submission form is used.
What makes a report actionable?
Plugin version and WordPress, WooCommerce and PHP versions.
Expected behavior, actual behavior, and repeatable steps.
Whether it happens on a staging site or a live store, and whether HPOS is enabled.
An error code or a redacted screenshot, only if available.
Please do not send credentials, Telegram bot tokens, full customer orders, payment information, database dumps or unredacted logs. If more evidence is required, we will arrange a safer channel separately.
Reports are reviewed and categorized as bugs, compatibility issues, documentation problems or feature suggestions. We cannot guarantee a fix date or individual implementation.