Forum Replies Created
-
Posts
-
I can understand your frustration. Let me share my notes in the first instance and then summarize our take on this.
- The ManageWP’s worker plugin (MWP) runs a piece of code during the admin_init action (when the admin environment initializes)
- This piece of code – MMB_Core::send_email_to_admin() – checks to see if a field called support_mwp_message has been submitted via a form
- If that field is present but completely empty it then returns an error message via MMB_Core::mwp_send_ajax_response() and this ultimately generates precisely the same piece of JSON you referenced in your initial post and kills execution of the request (so MWP is indeed the source of this)
- Why that is happening during import of Facebook events I have no idea – but I can reassure you our own plugin has no knowledge of the above functions, nor is the field support_mwp_message ever generated by them
So it’s a strange problem, but not one where there is an obvious cause in terms of our own code. So, one possibility is that this is being compounded by the presence of some other component (another plugin/theme). With that in mind you could try our usual troubleshooting steps, with the difference that you would also keep ManageWP Worker active:
- Ensure The Events Calendar, Facebook Importer and ManageWP Worker are up to date
- Deactivate all other plugins
- Switch to a default and unmodified theme
- Now see if the same problem happens
If on following those steps you found that the problem did not occur then that suggests something else is at work here (perhaps another plugin or theme is triggering form submissions inappropriately, or something of that order).
Since the root of this doesn’t appear to be in our code and nor could ManageWP’s own support team actually replicate the problem in their own test environment (had they been able to and it looked like a generally reproducible problem then of course we’d have taken this further) I don’t think we’re really going to be able to assist on this one.
I’m sorry for the inconvenience and disruption this causes for you, but I equally hope you understand our position on this.
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
Hi Oliver:
Unfortunately, the way things work, using string representations of array keys isn’t going to work (in a sense, you are asking the system to look for a submitted field called array[key] rather than the presence of element key within array).
It’s still possible to check for the presence of these fields and throw an error – but not via the same mechanism, I’m afraid – you’d need to take a slightly more roundabout approach for this one and figure out some custom method of doing this.
Sorry we can’t do more on this one.
Unfortunately we weren’t able to squeeze this one into our 3.5 release but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
Unfortunately we weren’t able to squeeze this one into our 3.5 release but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
Unfortunately we weren’t able to squeeze this one into our 3.5 release but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
Unfortunately we weren’t able to squeeze this one into our 3.5 release 3.5 but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
Unfortunately we weren’t able to squeeze this one into our 3.5 release 3.5 but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
Unfortunately we weren’t able to squeeze this one into our next upcoming release (3.5) but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!
