L.S.
Also hackers go a error-hunting, folks, for the info it potentially may reveal. 
We just elaborate on this x-hacker scheme via a test PHP page.
Should never be allowed to enter the client, nor even seen in production code.
But to explain potentially suspicious and insecure code it serves a purpose 
We stumbled upon it here, this just in coincidence,
see: -https://pglawyers.wordpress.com/test/
Not enough data about -pglawyers.wordpress.com was found to be able to run tests.
Parent domain ‘wordpress.com’ was found for the tested domain.
Server info proliferation here: https://www.shodan.io/host/192.0.78.13
Moreover uMatrix has prevented the following page from loading:
-https://c0.pubmine.com/2.14.01591698572968/ata.js
Re: Results from scanning URL: -https://c0.pubmine.com/2.14.01591698572968/ata.js
Number of sources found: 42
Number of sinks found: 20
with an external link, resulting in scanning URL: -https://login.proxy.uwec.edu/public/templateApplication.js
(tracking reloads code)
Number of sources found: 43
Number of sinks found: 19
Consider that PHP-error-test code should never be tolerated as production code,
as it could reveal to an attacker how internal PHP may tick.
Another example provides this error-code.
See this example:
<?php
error_reporting(E_ALL); @ini_set(‘display_errors’, true);
$pages = array(
‘0’ => array(‘id’ => ‘1’, ‘alias’ => ‘#home’, ‘file’ => ‘1.php’,‘controllers’ => array())
);
$forms = array();</blockquote> where 1.php schould be considered as suspicious. (info credits go to: luntrus)Also read on here on weak and suspicious PHP-code: https://stackoverflow.com/questions/25644235/suspicious-php-code
PHP in PHP-based CMS could really mean entering a code-minefield, when things spill over from server to client-side. :opolonus (volunteer 3rd party cold recon website security analyst and website error-hunter)