version : 5.6.1
Laravel 12 Compatibility Improved: Resolved compatibility issues to ensure the Active Matrimonial Flutter App runs smoothly with Laravel 12.
Package Renewal Logic Fixed: When a member renews a package after it expires, the new package now activates from the purchase date instead of the previous expiration date.
Interest System Improved: Members can now express interest in another member’s profile only once, preventing duplicate interest requests.
Phone Login Issue Resolved: Fixed the phone number login conflict related to Laravel 12, ensuring a stable and seamless login experience.
version : 5.6
Improvements & New Features:
- Upgraded Active Matrimonial CMS and all add-ons to Laravel 12 for improved performance, security, and long-term framework support.
- Introduced Auto Horoscope Matching, automatically showing compatible profiles based on users’ horoscope details.
- Added a new member type Basic Member, allowing users to register without purchasing a package. Basic Members can later activate a free package or upgrade to a premium plan.
- Fixed an issue where the Login button did not work properly with phone number input in mobile view.
- Improved OTP delivery via Fast2SMS SMS Gateway.
(Users of the OTP Add-on must update the add-on to version 1.6 to ensure compatibility.)
Important Notices:
*During the update process, a temporary error may appear due to the Laravel framework upgrade. If this occurs, simply run the update again; it will complete successfully on the next attempt.
*The AmarPay Payment Gateway currently has a compatibility conflict with Laravel 12. A fix will be provided in an upcoming update.
Fixes & Improvements:
- Birthdate field now displays correctly and remains editable from both Admin and Member panels, even when male/female age limits are configured.
- Resolved issues with Google Login, ensuring a smooth authentication process.
- reCAPTCHA v3 on the Contact Us page is now functioning properly to enhance spam protection.
*ATTENTION*
PhonePe requires the package ID for security reasons. It is necessary to have your package ID whitelisted in order to run PhonePe in your app. Please contact PhonePe customer support and confirm whether your package ID has been whitelisted.