HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: PHP Warning: Bad input encountered
Hello @R_J, Before doing anything else, I created an Admin only category and tested it by posting some discussions, and it's working fine and I'm able to post instantly. So what's next? might it be the advanced notifications? might be the notification check boxes are ticked by default and they remain checked even after… -
Re: PHP Warning: Bad input encountered
Ok, I'll try to use a different SMTP server and see if that helps. And I couldn't understand what do you mean by "it has something to do with notifications". if you mean the pop up notifications, I have tried that as well, I just enabled the popup notification in the advanced notification settings and it was working fine,… -
Re: PHP Warning: Bad input encountered
Ok, here is the result- I have enabled the advanced notifications for moderators and used two moderator's accounts to get the email and popup notifications for that category. And I guess this is the root cause of the problem, because without enabling the notifications, I was able to post instantly, but it took 3-4 seconds… -
Re: PHP Warning: Bad input encountered
I gave the advanced notification permission to the moderators to test it in the test category (There are two accounts), it slows down a bit (2-3 seconds) when they subscribe to the email notifications, and works fine when unsubscribe. Now I revoked the permission for everyone except the admin (Just 1 account) and even the… -
Re: PHP Warning: Bad input encountered
No, it's working fine with the other SMTP provider, so I guess it is still sending the notification emails somehow for those who subscribed while they have permission, because when I posted a test discussion and removed it as soon as it appeared, there was a user already viewing it (I saw it in the analytics Realtime… -
Re: PHP Warning: Bad input encountered
but if you have withdrawn that right again, than it doesn't matter. I'm just curious if it doesn't matter after disabling, then why it is still taking too long to post? It should work like the test category I had used to test which was working fine when I unchecked the notification options. I didn't give the advance… -
Re: PHP Warning: Bad input encountered
From what I know of Vanilla, it would have been my first guess, but assuming that an Amazon service is a bottleneck is not what I would have thought of... You asked the question how to find out who is using the advanced notifications. That's not simple, but if you have withdrawn that right again, than it doesn't matter.… -
Re: PHP Warning: Bad input encountered
Thanks for your response @R_J, The Discussion ID 778 has just a link to a product. I'm not getting any other error or warning in the logs when posting a new discussion, but it is very slow to post. But based on one of your other questions: do you have a mail notification when new discussions are created? I could not… -
Re: PHP Warning: Bad input encountered
Quite a lot plugins and I do not know the purpose of all of them. I only see that you have enabled the Advanced Editor and the Rich Editor. There should never be a need to have more than one active editor. So I would still suggest that you create an admin-only category, ensure that you no notifications will be sent for…
9 results