What I have discovered with the new messages plugin:

If you have mass messaged your members in the past, with the old messaging system, your messages would have gone out to the members, but unless your members replied, your messages only showed up in each member's mailbox but not your own. 

With this new messages plugin, all those mass messages you sent out in the past now show up in your inbox as a "conversation". So you now have hundreds, even thousands of "conversations" in your inbox, thus loading down your inbox. 

If you just let it load (it will take a long time), they should eventually show up. And unfortunately, this new messaging plugin does not have a bulk delete feature, so you now have to delete those thousands of messages one by one. This will take weeks, if not months to do. Because after you have deleted one, it will take up to or over 1 minute for the next message to load, so that you can delete it. 

I ask the developers to PLEASE update this plugin to be able to bulk delete messages!

Ok thanks Jobee

Hi Jobee,

My account was suspended because of this Message plugin, i asked my hosting company to help and this is the reply :

Dear Hope alan,

I am a server administrator at your hosting company - SiteGround.com and this is in reference to your website myvirgo.info. We detected that your website myvirgo.info continuously consumes a higher than the reasonable percentage of the shared resources of the server it is hosted on. As a result, we had to temporarily put an upper limit to the shared server resources your account can use in order to maintain the stability of the server.

Please note that in case you exceed the current limit, it may result in occasional "Resource temporary unavailable" error messages shown on your website. Also, if this issue is not addressed within the next 7 days, we will be forced to take further action which will result in website downtime - we will do our best to avoid this, but we need your cooperation.

Since we believe you are not causing the high server load intentionally, we will do our best to assist you so that your site can be fully functional again as soon as possible. Below you will find some explanations on what might have caused the high resources consumption and several solutions on how to deal with it. We recommend that you review all enclosed information in order to get a better hold of the problem and help us resolve it as fast as possible without any further inconvenience to you.

Sincerely,
Marin Tashkov
System Administrator
SiteGround.com

REASON OF LIMITATION:

As you know, your account is hosted on a shared hosting server and thus is sharing its resources with other customers' accounts on the same server. The issue with shared servers is that regardless of how powerful or well optimized they are, as is the case with our machines, there's still the possibility that a single user, or even a single application takes up most of its resources and overloads the machine. This causes all accounts on the server to stop responding and become inaccessible.

In order to prevent server overload, as soon as we detect a source of high load, it has to be isolated so that it cannot affect the overall server performance. This is a common scenario with shared hosting servers. Unfortunately, most hosting providers fail to detect such sources in time or when they do it's already too late, so the most common course of action is to simply suspend the account in question without any notification to the client, with no detailed report for the suspension and without giving the site owner the option to fix the problem.

We, however, believe in early warning and allowing the client enough time to react and work towards resolving the issue. While trying to minimize the inconvenience for you as far as we can, we do have an obligation to keep the shared hosting service as stable and as fast as possible for the rest of the clients hosted on your server. That is why we were forced to temporarily limit your account in order to avoid thoroughly suspending it when the load becomes unmanageable.

CAUSE OF HIGH RESOURCE CONSUMPTION:

We have conducted a detailed investigation and it turned out that your site executes slow queries towards its database, which eventually hogs the server. The server tries to execute your slow queries while putting other processes in the queue until some memory is freed. While they are waiting however, they stack up and cause further problems. There can be many reasons for slow database queries, but the following 3 are the most common ones:

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Here are some of the database queries that are slow and consume a lot of server resources:

LIST OF QUERIES
Executed 6 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 6 min ago for 8 sec on Database --> myvirgo3_aw.
Executed 5 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 5 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 5 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 5 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 5 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 4 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 4 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 4 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 4 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 3 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 3 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 3 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 3 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 3 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 2 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 2 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 2 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 2 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 1 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 1 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 1 min ago for 7 sec on Database --> myvirgo3_aw.
Executed 1 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 1 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 0 min ago for 6 sec on Database --> myvirgo3_aw.
Executed 0 min ago for 6 sec on Database --> myvirgo3_aw.

SAMPLE QUERY:
Executed 0 min ago for 6 sec on Database --> myvirgo3_aw.
SELECT `id`, `conversationId`, `timeStamp`, `recipientId`, `senderId` FROM `ow_mailbox_message` as t1 JOIN (SELECT MAX(timestamp) as time FROM `ow_mailbox_message` GROUP BY `conversationId` ) as t2 ON (t1.timeStamp = t2.time) WHERE `senderId` IN ( '1','2','3','4','5','6','7','8','10','11','12','13','14','15','16','18','20','21','22','23','25','26','27','28','29','30','31','32','33','
SIZE OF DATABASE
DB: myvirgo3_aw size:277MB

From the queries above we can conclude that your issue is caused by a ***large database***.

RECOMMENDED SOLUTIONS:

1. Optimize or remove the problematic script

Having not well written scripts is a quite complex problem. It may be caused by an additionally installed extension/module that is not working properly, or it may be in the application itself.

If the reason is in an extension/module, the easiest solution would be to disable/remove it. This can usually be done from the application's admin area.

If the problem is in the application itself, solving it may take much more time and effort and will probably require advanced programming skills. In such cases it would be best to contact the application's developers and ask for further assistance. They should be able to examine the issue and offer a suitable solution for it.

2. Upgrading to a more suitable hosting solution for your account:

If you choose to upgrade to a higher plan, we recommend our Cloud and Dedicated servers:

- Premium Managed Dedicated Servers ( http://www.siteground.com/dedicated_solutions.htm )
- Cloud Hosting Designed for High Performance ( http://www.siteground.com/vps_hosting.htm )

In addition to the standard higher end service plans, we believe your site will fit well on our new cloud hosting platform. The new cloud is a next generation platform that is currently in beta testing stage and will shortly replace our current cloud infrastructure. You are welcome to join the beta test and get 2 months of FREE hosting service on it. You can learn more about the terms of the test here:

https://ua.siteground.com/new_cloud_beta.htm

Thank you in advance for your understanding and cooperation! If you need further clarification, advice or assistance, do not hesitate to get in touch with our support team.

------

I just disabled my Message Plugin now...will see how it goes !!!

I have a dedicated server with an intel i7 eight core processor, and 12GB memory. 

This is MORE than enough to handle the oxwall site. Yet after the 1.7 update, with the messages plugin activated, the site is slow, and sometimes crashes the browser, etc.

Disable the messages plugin, and the site works wonderfully. 

Seems like most of the people who have updated to 1.7 are having the same issues.

What is Oxwall doing about it? Haven't heard from them on this issue for days. 

The messages plugin is trying to load every sent message a user has ever sent since the birth of their account. This is the problem. Especially with admins who have mass-messaged over 1000 members 5 or 10 times in the past. EVERY sent message is now showing up in my inbox (after a nice loooooooong wait)

Hi Jobee,

I managed to fix it, well a temporary measure for now, i went into my Cpanel and went to MyPhpAdmin, under :

* ow_base_messages

and deleted everything that had to do with messages, last conversations, conversation message_id....Now my database is clean no messages. And it works beautifully i hope went people start sending messages i wont have this issue.

Yes, I would agree that if there isn't 100's or even 1000's of messages, the plugin as it is works fast and responsively. But if I go in and delete all the messages from the database, I might have some pretty upset members. I already had one member email me asking where is his inbox and messages (when I had the pitiful plugin deactivated). He said he had important messages saved and hope they're not gone. So I can't just go in and delete everyone's messages. 

Oxwall needs to fix this so that it actually works, and doesn't call in all sent messages as conversations.

Before the update, I had about 60 messages in my inbox. After the update, I had 5000+ messages, because this new plugin brought all the messages I ever sent since the beginning, right into my mailbox, thus bogging it down to the point of crashing. 

The plugin lacks the basics that pretty much any mailbox on the face of the planet and in the universe itself has;

Bulk delete, and the ability to make paragraphs. 

Looking back on the previous mailbox, which operated like a mailbox, with all the basic features, I can't help but wonder who tested this new version and thought it was as good as or better than the previous? 

It blows my mind. It is so bare-bones, ill-conceived, and ignorantly approved for release. You can only delete one message at a time, and when you write a lengthy message with block paragraphs, when you send it, all formatting is removed and it's sent as one big huge paragraph. 

They took a decent, functional messaging/mailbox plugin, and took 10 steps backwards and release this one.

The plugin is called "Messages"

But it would be more appropriate to just call it "Mess". 

I got blocked on Instagram by my ex girlfriend very recently. I forwarded her a link containing information on mesaje de Constantin si Elena and she just blocked me. Is what I did really something wrong?