Thomas

Hello,

If it is only related to WPCA, and if you managed to translate other plugins, I would first recommend you disable any plugin except WPCA and Loco Translate, and try again.

What are the results about this?

You might probably want to post the issue you are getting with Loco Translate on the Loco Translate support forum.

Did you ask anything to Loco Translate about an issue you are getting with their plugin? We are following WordPress practices for internationalisation and string translations. We’re not doing anything special. Just loading translation files with WP standard functions. So they might probably give a better help than us.

At last but not least, is Loco Translate actually giving you any information on the language file you are actually editing?

Our main plugin is actually including some language files, stored in wp-content/plugins/customer-area/languages, but they are NOT loaded by default (they are just there in case you want some default languages files, not already translated by the WP community, and start over). By default, the loaded languages files are being downloaded from WP.org, and will be located in wp-content/languages, so you might probably be editing some languages files that are not being loaded. I don’t know how Loco Translate works, but you have to translate WPCA languages files from the wp-content/languages directory. You can also copy WPCA languages files to wp-content/customer-area/languages, and those ones will be loaded instead, so you can make your own edits, without Loco Translate, but by using PoEdit for instance.
Also, downloading files from WP requires that you first select your main language in wp-admin > settings > general, and that you then download the languages files for your plugins. This can be done on wp-admin > Update > Update languages (button at the bottom of the page).

Regards.

Thank you for this feedback, this is appreciated.

The problem might simply comes from the fact we’re not review-hungry, and we do not aggresively push our customers to post some reviews.

Anyway, glad to hear this plugin fits your needs.

Regards.

Hello,

Many users reported that using Loco Translate works fine with WPCA. It should normally work.

You might probably want to post the issue you are getting with Loco Translate on the Loco Translate support forum.

If it is only related to WPCA, and if you managed to translate other plugins, I would first recommend you disable any plugin except WPCA and Loco Translate, and try again.

Also, are the strings you are actually trying to edit coming from one of the add-ons, or from the main free plugin ?

Regards.

Hello,

I am not sure I clearly understand your question.

WP Customer Area is compatible with sites on which Woo Commerce is installed, however, we do not offer integration with WooCommerce. You’ll get a WooCommerce dashboard, and a WP Customer Area Dashboard.

Regards.

Hello there,

Your installation is corrupted. The file wp-content/plugins/customer-area/src/php/core-addons/private-file/private-file-addon.class.php is missing from the plugin. Not sure why.

However, it is easy to resolve. You just need to reinstall the main plugin (and its addons, if you have some).

Simply delete WP Customer Area and its addons from your FTP. To do that, you could delete any folder for which the name starts by customer-area, in wp-content/plugins, from your FTP.

WARNING: DO NOT delete the folder wp-content/customer-area. This folder is where some data are stored such as the attachment files! Deleting this folder would cause data loss!

Then, go to your site > wp-admin > Plugins, click on the “Add a new plugin” button, search for WP Customer Area, install and activate it. Then, if you had any addons installed, connect to our main site, and from your account, download your addons again, upload them back from the plugins page (or from your FTP), and activate them. Check this documentation if you need any help about installing an addon.

Note: deleting a plugin from your FTP won’t cause any data loss.

Regards.

• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.

Hello there,

this was working very well but suddenly the page crashed and I get a CRITICAL ERROR… which led me to change the plugin names via FTP to see which one is causing the conflict and it only happens with the customer area…

First, changing the folder name of a plugin won’t help in any case. Depending on the way the plugin is made, the folder name of a given plugin can be dynamic. Changing its name wont have any incidence in some cases (except creating new bugs without deactivating it). However :

• Do not hesitate to check our plugin conflict guide to know how to find conflicting plugins from your site.
• You could also rename the folder wp-content/plugins to wp-content/plugins_old from your FTP, refresh the plugins page from your site, and then move any plugin located in wp-content/plugins_old, back to wp-content/plugins, activate it again, and see if it works.

I have already checked everything but when I activate it normally again, the page crashes again…

If the page crashes, of if you get a critical error, you should normally be able to find the related PHP “FATAL ERROR”, in your php-errors.log from your FTP or hosting panel control. This would be the best and fastest way to know when the error comes from.

Could you please try to find the relevant error so we can be able to help?

PS: do not post any sensitive information from your logs on those public forums. Consider removing any sensitive server paths from the logs, any domain name, or consider posting your question privately on our support forums from our main site.

Regards.

• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.
• This reply was modified 1 month, 1 week ago by Thomas.

Hello,

Sorry for the delay.

Thank you for the report.

You can fix this error by editing the file wp-content/plugins/customer-area-notifications/src/php/helpers/notifications-admin-interface.class.php, line 17:

Change this:

    /** @var CUAR_NotificationsAddOn */
    private $notifications_addon;

To this:

    /** @var CUAR_NotificationsAddOn */
    private $no_addon;

This will be fixed in the next updates.

Best regards.

Hello,

Sorry for the delay.

This is doable with one of our premium add-on. However, as per the WP.org’s policies, we’re not allowed to provide any detail about that on those forums.

Please post your question on our dedicated support forums from our site, in the support section, and we’ll guide you about that.

Best regards.

Hello,

Sorry for the delay.

I dont know it this is issue due incompatibility with other plugins

You could actually be right. There is probably a plugin or theme conflict. Could you first check that by following this guide ?

Also, could you open the dev tools panel (CTRL + SHIFT + i), open the console tab, and check if you see any red output error while clicking one of those menu items?

Is it possible to reinstall plugin without loss of data?

Deleting and reinstalling WP Customer Area or its addons won’t cause any data loss. However, I bet it won’t solve the issue.

Best regards.

Hello,

Sorry for the delay.

It looks like you are facing a Javascript issue.

Could you please open the dev-tools panel (CTRL + SHIFT + i) while browsing the page, click on the download button, and see if any red output appears?

Do not hesitate to also post your issue on our site, on our support forums, to be able to privately post screenshots showing your issue.

Best regards.

Hello,

Sorry for the delay.

This is doable with one of our premium add-on. However, as per the WP.org’s policies, we’re not allowed to provide any detail about that on those forums.

Please post your question on our dedicated support forums from our site, in the support section, and we’ll guide you about that.

Best regards.

Hi,

Then, I guess the issue might come from the way you configured Really Simple SSL.

WP Customer Area uses your domain and protocol, so it won’t use http at all if properly configured on your site, and should only rely on https. (you can verify that http vs https is the issue by opening the chrome console. You should probably see an error like mixed-http content)

In most common cases, sites administrators actually activate Really Simple SSL, but they do not change their Site / WP URL, in WP-admin > Settings > General, and they keep the http URL instead of changing it to https.

WP Customer Area actually grabs this URL sometimes, and Really Simple SSL might not always be able to catch and update it to https on the fly.

Regards.

Hello,

• Are you using a caching plugin? If yes, could you try to exclude any customer-area/* URL from caching?
• If this still doesn’t solve your issue, could you check for a plugin conflict?
• You might also consider reviewing your PHP config (memory limit for instance).

I hope that helps,

Regards.

Hello,

You can safely ignore this notice. We just forgot to update the “tested up to” version in the readme file, in the last release. We’ll update that in the next release coming soon.

About PHP, we tested 8.2 on our side and our customers never reported anything wrong with PHP 8.3.

Regards.

Hello there,

Sorry for the inconvenience.

WP Customer Area is actually a dynamically generated private area, which should only be accessed by logged-in users. Each page would be differrent, depending on the currently connected user.

It is recommended to not cache those kind of pages, like you do not cache your wp-admin area, or your my-account page from woocommerce.

Best and easiest way to resolve that would be to exclude any customer-area/* URLs from your caching system. I bet that, otherwise, you’ll face many other unexpected issues.

For performance reasons, you could still keep CSS compression activated, for instance, but I don’t see any specific reason to cache a whole user-page (keep in mind that all pages from WPCA are actually user-specific pages, not public pages. You shouldn’t see any benefit caching the whole page, since they are not public pages, and since they need to be computed again for each user).

—

However, I am not arguing your report is wrong.

If you only comment out this line, is this still working ?

//if (ini_get('zlib.output_compression')) ini_set('zlib.output_compression', 'Off');

Or, do you also need to comment out both ob_clean functions to let it works?

Regards.