Database Prefix Issue with ARMember Multilingual Add-on

Hello,

First, I want to thank you for your continuous updates and improvements to the ARMember plugin. It's an excellent tool, and I truly appreciate your efforts.

However, I encountered a bug while using the ARMember Multilingual add-on. The issue occurs when the add-on is installed. It does not correctly detect the custom database prefix and instead defaults to the WordPress standard prefix wp_.

This can cause conflicts or unexpected behavior for installations that use custom database prefixes for security or organizational purposes.

Steps to reproduce:

Use a WordPress setup with a custom database prefix.
Install the ARMember plugin and its Multilingual add-on.
Observe the database tables created or used by the add-on.

Expected behavior:
The add-on should automatically detect and use the custom database prefix defined in the WordPress configuration ($table_prefix in wp-config.php).

I hope this information is helpful in identifying and resolving the issue. If you need more details or further testing, feel free to reach out.

Thank you again for your hard work!

Best regards