GovReady / GovReady-WordPress-Agent

Plugin for WordPress to assist with compliance
GNU Affero General Public License v3.0
5 stars 2 forks source link

Fatal error on line 12 when trying install #32

Open gregelin opened 8 years ago

gregelin commented 8 years ago

Received a fatal error. WordPress 4.5.2 running Divi Child Theme theme.

Downloaded version from commit # 09ce92bd7ed8f20a86b4269e6a4089eee46cd50a

screenshot

screen shot 2016-05-15 at 4 21 23 pm

php info from server:

root@gitmachines:/home/handcraftedhealth# php -v
PHP 5.2.4-2ubuntu5.27 with Suhosin-Patch 0.9.6.2 (cli) (built: Mar 11 2013 14:14:48) 
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies

root@gitmachines:/home/handcraftedhealth# curl --version
curl 7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.1
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps 
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz 

root@gitmachines:/home/handcraftedhealth# php -i | grep curl
additional .ini files parsed => /etc/php5/cli/conf.d/curl.ini,
curl
cURL Information => libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.1
jlyon commented 8 years ago

Thanks, we'll look at this today. We were working on some refactoring on Friday to merge in some changes to the JS client and probably messed something up.

Are you actively promoting the WP plugin? If so, we should probably start a branching system to avoid similar problems in the future (and we'll be extra cautious about changes we push to the API server). We were thinking that active pushing wouldn't happen until after some of the hardening happening during next week's sprint. Sorry for the miscommunication!

gregelin commented 8 years ago

I am not actively promoting. Was just testing on Lucrezia's blog, my better half.

We should probably start Dev branch management anyway though.

Sent from my iPhone

On May 16, 2016, at 7:39 PM, Jeff Lyon notifications@github.com wrote:

Thanks, we'll look at this today. We were working on some refactoring on Friday to merge in some changes to the JS client and probably messed something up.

Are you actively promoting the WP plugin? If so, we should probably start a branching system to avoid similar problems in the future (and we'll be extra cautious about changes we push to the API server). We were thinking that active pushing wouldn't happen until after some of the hardening happening during next week's sprint. Sorry for the miscommunication!

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub

jlyon commented 8 years ago

Sounds good, will do. Thanks.