Warrick

Since there has been no feedback on this for over a week we’ll assume this is resolved.

We apologise for the inconvenience.

That error is generic and provides no clues as to what the cause might be. No plugins should be required to resolve errors of this nature. In fact, when errors of this nature do occur we recommend deactivating as many plugins as possible to be sure they are not causing the error.

Another way to troubleshoot this would be to use a Javascript console to get more detail about the error. If you are using Chrome, when this error occurs go to View->Developer->Javascript console and take note of the details there. If possible paste those details in a reply here and that might help us determine the cause of the issue.

Hi,

MailCWP is an imap client. It connects to an imap mail server. Before configuring MailCWP you’ll need to configure the imap server and then use the relevant details from that server to setup the accounts in MailCWP.

If you are using an ISP for your email services then you can contact your ISP to provide the imap server details. You’ll need the server address and imap port, the account username (which may not match the email address) and password.

You’ll also need to know whether the server uses SSL and TLS for connections.

Once you have all that information you will be able to setup the account details in MailCWP.

Does that help?

This URE Pro issue was resolved in 1.97. Please start a new thread if you are still experiencing difficulties with URE Pro.

Also, please start a new thread for database corruption issues and post details there so we can investigate this.

BTW, best to do this outside of the MailCWP code to avoid losing your changes when the plugin is updated.

Of course you’re welcome to dig around in the source to discover how it all works and roll your own solution. Most account configuration information is stored as user meta data so if you inject the imap account settings into the user meta data when the user logs in that would solve your problem.

If you need us to do it we’ll look at putting this into a future release. If you need a specific delivery date we can prepare a quote for the work. Contact us directly at [email protected] to discuss that further if you are interested.

Original issue raised here has been resolved.

Excellent. Thank you for your patience and feedback.

What you are proposing is possible with some adjustment to the plugin.

Without any changes there is no automatic config but you can create accounts for each user in the admin back-end (Users). I’m guessing this will not suit your requirement.

We can look at including this sort of feature for an upcoming release but we can’t make any commitments regarding delivery time.

Is this urgent?

If you absolutely must comment publicly please elaborate.

Why do you say the plugin is broken? Over 400 active installs suggests it’s working for somebody. What exactly is the problem in your case?

Have you tried the standard troubleshooting steps? Have you deactivated all other plugins? Have you confirmed other plugins are not causing some sort of conflict?

Are you using the product with any form of competence? Have you set it up correctly? Do you know how to set up imap accounts? Perhaps a simple request for assistance would suffice?

The error specifically indicates that the accordion script has not loaded.

This is almost certainly caused by some Javascript issue – i.e. some javascript file that is loaded by the page is generating an error that causes all other javascript on the page to become invalid.

Alternative the accordion script is actually missing – but that would be odd because it ships with WordPress.

If there are any other plugins loading javascript for the page any of those javascript files could generate errors. It’s not clear how the nginx server could be contributing to this because it is at the JS/page level.

In the JS console check the resource list under Frames/…/script you should see accordion.min.js. If you don’t the script is not loading for some reason. MailCWP does add it so that would indicate it is not included in the WP install on the server.

If you do see accordion.min.js listed then there is some other javascript file interfering with the page load. Try deactivating plugins to see if that helps.

We do not know of any ongoing issues with URE Pro and MailCWP since the 1.97 release. We would have to investigate any issues you report.

We can also not make any assessment of the database crash/corruption issue without more detail. It’s not clear to us how MailCWP could possibly cause any database issues when it uses only internal WP functions to read and update the database.

If you can send us details of exactly which tables, rows and columns you found issues with we might be able to determine how MailCWP could have contributed.

The accordion jQuery UI script ships with WordPress. The MailCWP plugin definitely loads that script so it should be available.

One of the most common causes for this type of issue is some sort of JavaScript conflict, where a JavaScript error occurs many of the JS functions will be unavailable.

To confirm this check for any errors while the page is loading – before the above error. They should be reported in the console.

The MailCWP plugin is definitely loading the jQuery accordion script and no changes have been made in the last update so it’s not clear why that error would now occur.

The first thing to try, if you haven’t already, is to do a force refresh in the browser or use a different browser/computer to view the MailCWP page.

If that doesn’t work you may need to deactivate and reactivate the plugin. This could be destructive to MailCWP settings, etc so you may need to reconfigure all the accounts again after reactivating.

These errors appear to show that some parts of the jQuery UI have not loaded.

The jquery-ui accordion is built in to WordPress and it is used within MailCWP to display the account list.

If the accordion script is not loaded (and the first error above indicates it is not) then the MailCWP front-end won’t display correctly.

Since we have MailCWP running on several WordPress sites without this issue we suspect something else may have caused this error. Have you installed and activated any other plugins recently? Have any other changes or upgrades happened on the site?

The original issue raised here was definitely resolved so we should really be opening a new thread.

We are not aware of any database corruption issues and it’s difficult to imagine how the plugin could possibly corrupt any part of the database. We would need detail in order to troubleshoot this.

What problems have you been having? How was the database corrupted?