Leaderboard
Popular Content
Showing content with the highest reputation on 06/15/2018 in all areas
-
LogMaintenance A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large. LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis. Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime. Lines: keeps logs to a certain number of lines Days: keeps the log to a certain number of days Bytes: keeps the log to a certain amount of bytes Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank. Per Log Settings There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is: logname:[archive]:[lines]:[days]:[bytes] errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines The module can be found on github for you to check out. It's still fresh and I'm currently testing. https://github.com/somatonic/LogMaintenance10 points
-
Several core updates this week including a new way to perform $pages->find() searches by using Field tags, a new Field tag manager, new methods added to our $input API variable, new Inputfield traversal methods, and more… https://processwire.com/blog/posts/pw-3.0.106/7 points
-
I certainly agree that the EU is once again trying to go from one extreme to the other which is quite probably not a good idea at all. If I understand this correctly it's about copyright, right of moneytization and licensing. All those things are mostly well defined in the non-digital world, while on the internet people just didn't care much up until now mostly because of anonymity and lack of ways to prevention or prosecution, while the impact of sharing unlicensed content is easily greater than in the analog world. I certainly see that reform critically for anything, where people want to get payed for or limit access to their work, because it would probably restrict many good cases of quotation/linkage as well. But the internet imho is great for the things, which are willingly shared and licensed to be usable/shareable/editable by other people. Most of my open source work is licensed under MIT or Apache just because of that. It just seems people just don't want to be bothered with the question of: Am I allowed to use a piece of information elsewhere. Sadly the EU just seems to be fully driven by publishing corporations trying to get their share of money from their content being shared instead of dealing with the issue in a sensible way.4 points
-
That's right, field names have precedence, and it also warns you if you try to create a tag that collides with a field.2 points
-
Hey @Robin S - I have been experiencing this again too. I though it was solved in some Tracy core updates, but apparently not ? I tend to agree with you that there really isn't a need to move the bar, so I think a fixed option is probably a good idea, so I have added it in the latest version - the option is called: "Fixed Position". You might need a hard reload after changing this to see the effects. This version also includes some more MySQL info in the Diagnostics panel. It's all about the current number of connections etc:2 points
-
There is no connection between the pages table and the fieldgroups and templates tables. You can name your page identically to a template and there shouldn't be any conflict. However, fieldgroups and templates are twins. Creating a template creates a fieldgroup with the same name. Maybe you already had a template called nav, hence the conflict. Alternatively, you may have had a fieldgroup called nav that was not deleted when a similarly named template was deleted?2 points
-
I put together my very first website about 22 years ago. It was all <tr><td> and images but I could only concentrate on the visual aspects, no one really cared about anything else than that (except for file size of course...). Yep, those were the golden days for sure.2 points
-
I get the feeling that I should have started with websites 15 years ago when the internet was still open and free. Anyone else share this feeling ?2 points
-
Why push these proprietary and closed source slacks and discords, when we have an IRC channel? https://kiwiirc.com/nextclient/#irc://irc.freenode.net/processwire We will soon see some very cool announcements from the Kiwi IRC camp. IRC is stepping up its game. Also, if you use Vue.js, it is easy to get on board and contribute to Kiwi IRC.2 points
-
Released: https://modules.processwire.com/modules/process-documentation/ https://github.com/outflux3/ProcessDocumentation This is a new module that will be released soon - the purpose is to allow you to create help pages in the admin. This differs from the Admin Help module in the approach, and will be kept totally separate. The Admin Help modules provides the ability to make a help tab on any page edit screen (and optionally make that pop up in a lightbox), as well as a single process page showing all of the help pages in a single accordion. This module's workflow is different - first you can create your help pages any way you want using any template and any field for the body text. You can create unlimited admin help pages, using ProcessDocumentation, select the page to display, and then users can click on that in your menu to access the help page. You can create a folder structure by creating a top level menu item using ProcessList, and then various help pages under that parent using ProcessDocumentation. The module comes with 2 internally used textformatters, one of them adds classes needed to the markup for some elements to allow styling within the content and not conflict with admin theme rules (e.g. ol, ul, blockquote, table etc.). The other textformatter allows you to implement jQueryUI tabs within your help page, using a simple shortcode/token format. The styling for the jQueryTabs widget matches that of the standard processwire admin theme tabs, so that users will feel familiar with the interface. Instructions: 1) Install the ProcessDocumentation module. It will also install the 2 textformatters. You don't need to apply those textformatters to any field, they are just used internally by the module and called in the correct order to make them work. 2) Select the field to use for the content display (e.g. body). 3) Create your content. If you want to use tabs, this is the syntax: {tab=My First Tab} Some content {tab=My 2nd Tab} Some more content {/tabs} Make sure to close the tabs or the page will break... you need 2 or more tabs for it to work. You can only currently have 1 set of tabs per page. You should be able to safely use lists and tables. 4) Create the process page under the admin. Select ProcessDocumentation as the process and then select the page to show from the tree. 5) Now you should have the menu item in your menu if you are using Reno it will be on the left, and under a parent if you setup a parent in the tree. Clicking on that will render the help page. This example uses 7 tabs. If you are superuser, you will see the edit process settings. Other users will see the edit content only, which allows them to edit the content of the help doc, make corrections or additions. If you need to prevent access to any documentation pages by any role, you just add the name of the process page to the permissions and then don't check it for that role. The module has a defined permissionMethod that checks to see if that permission is defined, and then if the user has it. Not defining individual help page permissions means they are visible to anyone with the documentation permission. There is more work to be done on CSS, and other small details.1 point
-
Thanks for the new features Ryan! Just one question though regarding the new $pages->find tag search feature: what happens if there is a field and a tag having the same name (ie name collision)? Does field name take precedence?1 point
-
We want to install ProcessWire in 2 server layers In the first layer of servers is only to deliver the static content (css, js, image, html "ProCache"), without php installation the apache would be initialized in worker mode In the second layer of servers, php will be available, the work will be done to process all the requests of the pages that are not in ProCache and of the services that require php execution. The servers of the first layer would reach the servers of the second layer through a ProxyBalancer. My questions are: How can I take the configuration of .htaccess to virtualhost? The setting RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] can be changed for RewriteRule ^(.*)$ proxybalancer://secondservers/index.php?it=$1 [L,QSA]1 point
-
Well, you didn't tell us what you have tried. Did you try any of the suggestions of the a.m. thread? safe_mode, mod_security, increasing memory limit, check if GD library is installed, maybe upgrade PHP, what do you see in /site/assets/logs/errors.txt? etc.1 point
-
Crazy! They are receiving free backlinks, better SEO positioning, more free traffic because the marketing effort is made by the page that publish the RSS content, all that translates to them in money per click on advertising, leads and sales. Maybe we should create Link-Tax-Back to receive a payment for sending our users.1 point
-
Well, sort of. Let's look at the example of Artisjus which is the official authority in Hungary dealing with licensing music. Over here, popular artists profit from this system while not so popular artists suffer from the bureaucracy, not profiting from it at all. Taking this a step further into just "quoting bits of text with proper credits included" is just ridiculous. Also, forcing content providers to implement software and hardware to automatically filter content which might probably need licensing is short sighted and arrogant. Also, who is going to pay for the implementation and maintenance of such "system-add-ons"? It is just so easy to come up with new taxes but seeing the consequences is a different matter.1 point
-
1 point
-
Hi @adrian, I'm still experiencing the issue below in the latest Tracy: I can fix it with the CSS I mentioned earlier... ...but it would be handy to have that as an option built into the module so no custom CSS is needed. Thanks!1 point
-
To avoid the notice "Trying to get property 'type' of non-object" and possible issues later it's better to check wether the field is really a Field: $f = $fields->get('myfield'); if ($f instanceof Field && $f->type instanceof FieldtypeLanguageInterface) { // do something }1 point
-
Try to clean your browser cache and check that all .js and .css files were loaded in the admin backend. I've seen this issue several times on a super cheap shared hosting plan I use. Either files (.js and .css) time out or just need lots of time to get loaded. I even got incomplete files I had to delete from cache in order to get a fully loaded backend.1 point
-
You might want to use the functions API (just literally discovered it myself seconds ago...) https://processwire.com/blog/posts/processwire-3.0.39-core-updates/#new-functions-api1 point
-
I guess that a chat channel would simply mean too much distraction. imho, there's nothing wrong with using a forum as the main place of communication, even in 2018. The general expectation with chat is that there's always someone around within 3 seconds with a useful reply / solution / answer. IRL it doesn't always work like that, if you have a day-job and have to focus on your daily work at hand. This may sound like I'm all against having a PW Slack channel - I'm not. But I'm simply afraid that infos / tips would be even more fragmented that way. (just my 2 cents)1 point
-
"waiting for table level lock" would suggest that something is odd on the server side and/or mySQL. Maybe mySQL doesn't have enough memory, or is being re-booted every now and then, and can't handle the queries fast enough. Perhaps switching from myISAM to InnoDB would help already. Or maybe this is being caused by a large mysqldump process https://superuser.com/questions/1093610/mysql-5-7-stuck-forever-waiting-for-table-level-lock1 point
-
Is your module autoload property set to true ? if not, then set 'autoload' => true in the module info or if you want your module to be an autoload only on the admin area, then set autoload to : 'autoload' => function () { return (wire('page')->template == 'admin'); }1 point
-
Getting just the folder means $file is actually not a file (Pagefile), but a Pagefiles object. File fields are internally always handled as list of files, so you might need to use the following or alike: $file = $upload->file->first();1 point