I’ve been experimenting by adding parameters ( cmd=start and pqchoice=local )
Now I’m getting this return message when using just processqueue&secret:
{"campaign":0,"num_users_for_message":0,"batch_count":0,"batch_total":0,"sendemail returned false total":0,"send blocked by domain throttle":0,"add attachment error":0,"sendemail returned false":0,"sentastest":0,"invalid":0,"failed_sent":0,"sent":0,"num_per_batch":0,"campaigns":0}
Edit: pqchoice is a setting. Once used, it’s saved. That’s what generates this essentially empty JSON. When I reset the pqchoice value (pqchoice=reset), I’m back to getting Error: Acess Denied
Adding the username and password to the query string does not change the message.
@michiel@justinputney Remote queue processing didn’t work for me either, I got a JSON result with zeroes too.
But I have found that the phplist_config table entry for pqchoice has to be set to “phplistdotcom”, otherwise the remote request is ignored. I have no idea how to get that value into the table other than using phpmyadmin. There seems to be an assumption that only phplist hosted will send the remote request.
The JSON response is the result of the queue having been processed. There’s no need for any other data, except that it has been done. But yes, I agree that the assumption that phpList.com is doing it is incorrect. If someone can report that in mantis, we can have a look at it for the next version.
@michiel@duncanc Now that I have that setting, the Process Queue page (in the UI) says my API key is wrong and is prompting me for a phplist.com API key in order process the queue.
It’s really hard to tell if things are successful or failing.
Yes, I guess I forgot about non-hosted remote queue processing. I will need to add another choice, being remote queue processing which is not operated by phpList.com. That should not be too hard, but it just needs adding. In the meantime, you can remove those lines, and it may work.
OK. Commented out those lines, removed the pqchoice setting and everything is back to working the way it was in 3.0.12 (plus the new features). Thanks @michiel and @duncanc!
Good day.
I’m having the same problem in sending messages in queue, via cron. I have mentioned the lines of code, but it keeps on not working.
Algem managed to solve the problem?
I’m using version 3.2.0