Mente Clara Portal

Mente Clara Portal is part of the original Mente Clara project maintained by Wilder Espinoza at Lideratec Academy. It extends Mente Clara Core, which is already published in the WordPress.org Plugin Directory by the same contributor, wespinozab: https://wordpress.org/plugins/mente-clara-core/

The portal provides a responsive front-end account experience for service practices that use Mente Clara Core. Patients can register, manage their profile, request appointments, review their own bookings, and access their own WooCommerce orders without entering wp-admin.

The default Mente Clara architecture reserves wp-admin for administrators. Other authenticated roles are routed to public-facing account experiences. Administrators can disable that policy from the plugin settings if another role must use wp-admin.

Features include:

• Responsive front-end sign-in and optional patient registration.
• Patient profile and password controls.
• Basic appointment requests when a compatible booking extension is unavailable.
• Booking integration hooks for a separate specialist agenda.
• WooCommerce order history and pending-payment links when WooCommerce is active.
• Ownership checks so users access only records linked to their WordPress user ID.
• Administrator-only wp-admin mode, configurable by the administrator.
• Nonces, input validation, escaped output, rate limiting, and a registration honeypot.
• Automatic noindex, noarchive, no-cache headers, and sitemap exclusion for portal pages.
• WordPress personal-data exporter, eraser, and privacy-policy guidance.
• No clinical-history fields, telemetry, or external tracking.

Page creation is not performed automatically on activation. An administrator must review the settings and explicitly create or repair the portal pages.

This plugin handles administrative and logistical information. It is not an electronic health record and must not be used to store diagnoses, clinical histories, therapy notes, or other sensitive clinical information.

Privacy

The plugin may store standard WordPress account data, profile fields, a consent timestamp, logistical appointment preferences, and references to records owned by the current user. When WooCommerce is active, the portal reads orders linked to the current WordPress customer ID.

The plugin does not store card numbers or CVV values. It does not add diagnosis or clinical-history fields, and it does not transmit data to external services by itself. WordPress may send administrative email notifications through the site’s configured mail system.

The plugin registers information for the WordPress personal-data exporter and removes its own portal consent metadata through the personal-data eraser. WordPress accounts, WooCommerce data, and appointment records remain subject to their respective retention and legal requirements and must be reviewed separately by the site administrator.

Developer Notes

• mente_clara_portal_user_can_access_admin customizes wp-admin access for a user.
• mente_clara_portal_professional_url supplies a front-end specialist agenda URL.
• mente_clara_portal_is_professional_user customizes specialist detection.
• mente_clara_portal_allow_legacy_email_lookup enables legacy email-only appointment lookup; it is disabled by default.
• mente_clara_portal_appointment_requested runs after a basic portal request is saved.
• Post-type filters are available for current or legacy services, specialists, and inquiries.

Copyright

Mente Clara Portal, Copyright 2026 Wilder Espinoza.
Distributed under the GNU General Public License, version 2 or later.

1. Install and activate Mente Clara Core.
2. Upload and activate Mente Clara Portal.
3. Open Mente Clara > Portal de pacientes.
4. Review the access, registration, email, and privacy settings.
5. Select Create or repair pages.
6. Keep the contextual navigation enabled, or add the generated access page to your theme menu manually.
7. Test patient registration, login, appointments, profile changes, logout, and mobile navigation in a private browser window.
8. If WooCommerce or a compatible booking extension is active, test those integrations with a non-administrator account.

Who develops the Mente Clara project?

Mente Clara is an original project maintained by Wilder Espinoza at Lideratec Academy. Mente Clara Portal and its required dependency, Mente Clara Core, are maintained under the same WordPress.org contributor account, wespinozab.

Who can access wp-admin?

By default, only users with the manage_options capability can enter wp-admin. Other authenticated users are routed to a public-facing experience. An administrator can disable this policy in the Portal settings, and developers can customize it with the mente_clara_portal_user_can_access_admin filter.

Where are specialists redirected?

Accounts recognized as specialists can be routed to a dedicated professional agenda by a compatible booking extension. Without that integration, the portal uses the standard front-end account destination.

Does the plugin create pages automatically?

No. Page creation requires an explicit administrator action from the Portal settings screen.

Is WooCommerce required?

No. WooCommerce order information appears only when WooCommerce is active.

Does this plugin store clinical records?

No. The built-in fields are limited to account, contact, payment-reference, and logistical appointment information. Do not enter diagnoses, symptoms, histories, or therapy notes in logistical fields.

Why are legacy appointments linked only by email not displayed?

Version 1.4.0 and later use the WordPress user ID as the default ownership key. This prevents a newly created account from claiming historical records based only on an email match. Sites with verified legacy data can temporarily enable the mente_clara_portal_allow_legacy_email_lookup filter while they migrate those records to user IDs.

1.4.2

• Clarified original project ownership and the relationship with the existing Mente Clara Core plugin maintained by the same contributor.
• Aligned the author URL with the project domain and the contributor’s official email domain.
• Added explicit user-capability checks to profile updates, password changes, and appointment requests.
• Enforced registration, profile, and password field limits on the server.

1.4.1

• Updated the tested WordPress version to 7.1.
• Removed the unused translation directory header so WordPress.org can manage language packs automatically.
• Documented why password values must remain unmodified before secure WordPress authentication and hashing.
• Reorganized bounded ownership queries and documented their required metadata conditions.
• Replaced dynamically constructed hook names with explicit, prefixed integration filters.
• Documented the bounded two-page exclusion used by the native WordPress sitemap.

1.4.0

• Formalized the administrator-only wp-admin model and added an administrator setting to disable it when another role requires dashboard access.
• Added a developer filter for controlled exceptions to the wp-admin policy.
• Added noindex, noarchive, no-cache headers, and native sitemap exclusion for access and account pages.
• Strengthened registration passwords and replaced account-enumerating email messages with a neutral response.
• Added a direct link to the configured WordPress privacy policy during registration.
• Restricted appointment ownership lookups to WordPress user IDs by default and added an opt-in legacy email lookup filter.
• Added server-side validation for published services, specialists, future dates, phone length, and note length.
• Reduced personal information in appointment notification emails by keeping the logistical note in the private record.
• Added translated appointment status labels and an integration action after basic appointment requests.
• Improved profile-update error handling and clarified frontend role behavior in administration.
• Improved the create-or-repair action so it restores missing shortcodes and republishes configured portal pages.
• Localized the form processing state and improved accented-name avatars and localized date display.
• Consolidated duplicate readme sections and version entries.

1.3.2

• Renamed the existing mc_patient role label to Paciente Mente Clara without removing user assignments.
• Clarified patient and specialist roles in the Portal administration.
• Preserved separate public-facing experiences for patients and specialists.

1.3.0

• Expanded the responsive customer portal and contextual account navigation.
• Added integration filters for specialist routing.
• Added current and legacy Mente Clara Core post-type detection.
• Improved administration page health and role information.

1.2.2

• Fixed the activation callback and stopped creating public pages automatically.
• Improved Plugin Check compatibility and translator comments.

1.2.1

• Prepared WordPress.org metadata, privacy documentation, and dependency declarations.

1.2.0

• Improved compatibility across the Mente Clara ecosystem.

1.1.0

• Added account security, password changes, payment links, accessibility, and responsive improvements.