Search the Community
Showing results for tags 'log'.
Found 7 results
-
Logs JSON Viewer Formats JSON data in ProcessLogger for improved readability. Because log files can only contain strings, it's a common practice to use json_encode() to convert an array to a string when you want to save the data to a log file. But the resulting JSON is not as readable as it could be when viewing the log in ProcessLogger. The Logs JSON Viewer module uses the json-viewer library to improve the readability of JSON data in ProcessLogger and add some useful features. Before: After: Configuration You can set the config options for json-viewer in a textarea field. See the json-viewer readme for information about the options. There is also an option to set the width of the column that contains the JSON data. This setting exists because otherwise the column jumps around in an inconsistent and distracting way when changing from log to log or between paginations. Features You can switch the view of the JSON data between formatted and unformatted using the toggle button at the bottom of the data. The viewer has a number of useful features such as: Progressively expand or collapse levels in the data. View the count of child items and the data type of each item. Search for a string within the data. Copy all or part of the data to the clipboard (requires the HTTPS protocol). https://github.com/Toutouwai/LogsJsonViewer https://processwire.com/modules/logs-json-viewer/
-
Custom Logs When you use the core $log->save() method you can only save a single string of text. When you view the log in the core ProcessLogger the columns and their header labels are predetermined. The Custom Logs module is different in that it lets you write and view log files with the number of columns and the column header labels you specify in the module configuration. Configuration In the "Custom logs" textarea field, enter custom logs, one per line, in the format... name: column label, column label, column label ...with as many comma-separated column labels as needed. The log name must be a word consisting of only [-._a-z0-9] and no extension. If you prefix a URL column label with {url} then the value in the column will be rendered as a link in the log viewer. The date/time will automatically be added as the first column so you do not need to specify it here. Writing to a custom log Use the CustomLogs::save($name, $data, $options) method to save data to a custom log file. $cl = $modules->get('CustomLogs'); $cl->save('my-log', $my_data); Arguments $name Name of log to save to (word consisting of only [-._a-z0-9] and no extension). $data An array of strings to save to the log. The number and order of items in the array should match the columns that are configured for the log. $options (optional) Options for FileLog::save(). Normally you won't need to use this argument. Example of use Custom log definition in the module configuration: visits: {url}URL, IP Address, User Agent, {url}Referrer Saving data to the log: $cl = $modules->get('CustomLogs'); $data = [ $_SERVER['REQUEST_URI'] ?? '', $_SERVER['REMOTE_ADDR'] ?? '', $_SERVER['HTTP_USER_AGENT'] ?? '', $_SERVER['HTTP_REFERER'] ?? '', ]; $cl->save('visits', $data); Viewing the resulting log in Setup > Logs > visits: https://github.com/Toutouwai/CustomLogs https://processwire.com/modules/custom-logs/
-
Hi all, with $config->adminEmail it's possible to send out an email for fatal errors (for example a syntax-error). It would be nice to get also an email in case of an unhandled exception. There could be a situation of an wrong upload and exceptions on the live-page. Is this possible? Also it could be a very handy feature to be able to choose specific logs which are sent our via email automatically. Thanks for your feedback, Dennis
-
Hey there, A friend's server (php, to be exact) is now going down rather frequently (still irregular but almost every week), and I am trying to get to the bottom of it. It's a serverpilot configured small to middle tier DO Ubuntu server, running php 7 on nginx, https only, (with a letsencrypt certificate added manually by me, not via serverpilot) When looking through the various log files I found a couple of things I couldn't place, can you guys make anything of this? This happens multiple times a day (form different IPs) and goes on for 40-50 pings: 200.8.223.47 - - [07/Mar/2017:01:02:27 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:03:13 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:03:59 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:04:45 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:05:32 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:06:19 +0100] "POST / HTTP/1.0" 301 229 200.8.223.47 - - [07/Mar/2017:01:07:05 +0100] "POST / HTTP/1.0" 301 229 .... Is this suspicious? (nobody was editing the site at this time) And these here come in 2-10 sec intervals, usually in 2-3 minute bursts, from different IPs, sometimes multiple times a day, sometimes followed by 30-40 "POST" commands 86.106.157.213 - - [06/Mar/2017:16:40:53 +0100] "GET /wp-login.php HTTP/1.0" 301 245 86.106.157.213 - - [06/Mar/2017:16:40:58 +0100] "GET /wp-login.php HTTP/1.0" 301 245 86.106.157.213 - - [06/Mar/2017:16:41:03 +0100] "GET / HTTP/1.0" 301 233 While this should by no means get the server to it's knees (or should it?) this is not normal, right? Cheers folks!
-
I'm working on a website for a client using Processwire. The client had some questions concerning security that i'm not able to answer so i hope you guys can help me out. In general I was wondering if there are any logs about bug fixes and security updates. Has Processwire ever been hacked? And how will the security be guaranteed in the future? Since the platform is growing I might imagine so will the amount of attacks. For instance one thing I noticed that the .HTACCES file changed between 2.7 and 2.6 was this because of security leaks or because of other reasons.
-
Hello. I've been hanging out in Google Analytics a bit these days enjoying the real-time activity view of my site's traffic. It has prompted me to wonder if there is a way to record the terms people search for using the built-in PW search engine to a log file of some sort on the server so I can review it from time to time to get a sense of user needs.
-
Hey all, Since launching a site about a week ago we've been getting an error within the pw logs. It occurs about once a day and I was wondering if anyone could shed some light on what it is: 2013-10-07 14:19:00 ? http://www.google.com/?/ Error: Exception: DB connect error 1045 - Access denied for user 'abc'@'localhost' (using password: YES) (in /var/www/html/wire/core/ProcessWire.php line 96) 2013-10-08 08:05:05 ? http://www.baidu.com/?/ Error: Exception: DB connect error 1045 - Access denied for user 'abc'@'localhost' (using password: YES) (in /var/www/html/wire/core/ProcessWire.php line 96) 2013-10-09 08:41:06 ? http://www.google.com.tw/?/ Error: Exception: DB connect error 1045 - Access denied for user 'abc'@'localhost' (using password: YES) (in /var/www/html/wire/core/ProcessWire.php line 96) I assume their SE spiders trying to index the site but can't see why they'd be throwing an error like this...
