hi clancimus,
Thank you for the question. About the responsive, could you let me know which version of wordpress, php version and site url you are using so that i can take a closer look at the problem. For the deactivate the plugin. In case you can not deactivate it in admin area because of conflict-based reasons, you can try removing the plugin via FTP.
Have you a good day,
Sincerely,
wr support team
Hi Tony,
I am using WordPress 4.0.1, I’m not sure what version of php I am using. Is there a way I can privately message/email the URL? I tried to sign up for your forums because of the private reply but was never sent my login information.
Hi clancimus,
Thank you for the reply, i am sorry for this unconvenience, have you tried checking the spam box? If you still get the login information, please let me know so that i can report it to the forum manager. Now, you can send the related-ftp and admin information to my working email: tungnbs@bravebits.vn
Have you a good day
Sincerely,
wr support team
I have the same problem too – cannot deactivate the plugin. To delete the files is not an option because that will leave unused data in database. Bad work. One star.
Hi Sergey,
Thank you very much for letting us know the problem. I am really sorry for this unconvenience.However, as you know, sometimes it could come from the conflict amongst plugins. Could you send me a private email related to admin login and FPT account in case i have to remove the file manually via our support forum so that i can directly help you deactivate the plugin. If you need to delete the file in SQL database. i am also pleased to do it for you
Have you a good time
Sincerely,
tony
Plugin Contributor
Adam
(@hieudm)
Hi Sergey,
You should I think ask for help in the Support page or Official Support Forum at http://www.woorockets.com/forum/product-support/wr-megamenu/ before posting a very low review score like this.
That gives the plugin author a chance help you with your specific problem.
You may also be mistaken if you focus on this happening since the last update – it may just be a coincidence or we did provide the solution for this problem.
Best regards,
Adam.
