9 June, 2016 at 1:08 pm #18757
Yesterday prints stopped working.
In the log file I get repeated errors:
2016-02-03 16:13:06 : ERROR LOGIN: 2016-06-08 15:39:45 : ERROR LOGIN: 2016-06-08 16:40:28 : ERROR LOGIN: 2016-06-08 16:49:19 : ERROR LOGIN: etc...
After looking at the code, it seems the plugin isn’t getting a token from Google. I tried requesting a new token through the settings page, but upon return I get the following error:
Notice: Trying to get property of non-object in /var/www/clients/client791/web2441/web/staging/wp-content/plugins/wppizza-google-cloudprint/inc/oAuthRedirect.php on line 92
Did Google change something on their end?9 June, 2016 at 1:41 pm #18758
Finally was able to get a new token… Don’t know what the problem was. It didn’t work for over 24 hours.9 June, 2016 at 2:16 pm #18761
Aaaand now it’s not working again!
Error in log:
2016-06-09 12:55:55 : Could not get printers 2016-06-09 13:11:17 : Could not get printers9 June, 2016 at 2:24 pm #187629 June, 2016 at 4:55 pm #18763
all i can say is:
i did not change anything, so if it stopped working , find out what did ….wasn’t me 🙂10 June, 2016 at 5:32 pm #1879510 June, 2016 at 5:37 pm #18796This reply has been marked as private.10 June, 2016 at 5:46 pm #1879710 June, 2016 at 6:02 pm #18798This reply has been marked as private.10 June, 2016 at 6:04 pm #18799
i would also strongly suggest not to output debug, but just log it like so
https://www.wp-pizza.com/topic/how-to-enable-debug-in-wordpress/13 June, 2016 at 4:33 pm #18839
Makes me mad 😡 I spent HOURS trying to figure this out.
Turned out the hosting company was messing things up. According to them the firewall on the server was blocking the connection – though I find that doubtful – they were fiddling around last week to try to speed up the site at the request of the client.13 June, 2016 at 7:26 pm #18840
> though I find that doubtful
might well be that they fiddled round with the firewall to speed things up though…(or just some htaccess deny stuff)
anyway, glad it’s working again. will keep it in mind if someone else has that issue
- The topic ‘ERROR LOGIN and unable to get new token’ is closed to new replies.