Leaderboard

totally agree! right now it sometimes seems that the interest is measured by "who shouts loudest"... but we had several examples where users didn't show their interest because the feature has been on the roadmap for a while so nobody said anything about it and waited for a surprise in the next blogpost. just if it was requested this is great example of what robin is talking about. informations about upcoming features are spread over the forum (wishlist) and github... so i want to support robins request and maybe extend it a little bit towards "better community management". we had one occasion where @ryan implemented something that was already available as a module (image tagging). don't get me wrong, of course i prefer solid solutions built into the core over 3rd party modules (i was voting for the predefined-crop-in-the-core-feature for a long time), but i would love to see a little more discussion and community involvment here. i can imagine that this can eat up a lot of time if done wrong - but i think it can also save time if done right. for example the community could do some research (like in the github link above), bring in ideas or point ryan to already existing solutions like it was the case with image tagging. finally i want to thank everybody contributing to this project and helping me out in the forum. i had a great 2017 and it would not have been possible without this awesome product and community! happy and successful 2018 to everybody

Hi, I just want to thank to flydev and everyone else who has contributed to this wonderful module. For me, Duplicator It has worked flawlesly to make backups and bring those backups to my local machine to test new functionality. Sincerely a fellow Processwire developer.

That's an amazing list of 2017's features. Seeing them in a single place makes you appreciate how lucky we and our clients are. Thanks for another incredible year of updates. I imagine everyone's wish list is different. This is what I'd like to see natively in PW. I know some of these are already available as Modules so no offence if you're reading this and have already put tons of work into creating something similar. Processwire Multi-Admin A Processwire dashboard which allows me to monitor multiple installs across different servers. This dashboard would list my installs, version number, and display available upgrades (Module and Core) and allow me to update above from central place. It might show me logged in user(s), uptime etc. Media Manager A built in MM which acts as a single place to manage all uploads. Using the MM you can find, list and edit any uploaded file/image. and its versions. Add tags, crop, delete, rename, copy, bulk upload etc Furthermore the MM should work with user permissions so a MM for me might list different assets than an editor etc Importantly, the look of the MM would be consistent with what's already in place and the new UI Kit theme. SEO A native SEO Module that is maintained and updated as modern SEO evolves. Image Cropping Pre-set image crops and a way to define and manage them. That's it :-/

This is the commit where the feature was added: https://github.com/ryancramerdesign/ProcessWire/commit/e02fef088a555610ba7f8e25d1bf55cb1cd8f84e

Thanks to you Bernhard - you're an integral part of this community too - the stats tell us one of the top 5 for the year

yeah i also want to thank @flydev for the awesome work on this, massively appreciated!

I'm using mod_rewrite to link to files on the live system if they are not found on the development systems: # file: .htaccess <IfModule mod_rewrite.c> RewriteEngine On # Get all asset files from remote if localy not available RewriteCond %{REQUEST_FILENAME} !-f [NC] RewriteCond %{REQUEST_URI} ^/www/site/assets/files/ RewriteRule ^(.*)$ https://www.live.com/$1 [L] </IfModule>

You will need to use a repeating field type "Players" for the players. For me, the order of preference in terms of UI would be: 1. ProFields Table 2. Repeater 3. PageTable Within each item of Players you have two Page Reference fields - one for Player and one for Instrument. The safest thing would be to specify the instrument for every player in the Players field. But if the default instrument of a player is something that is fixed once selected (i.e. a player never changes their default instrument) then you could consider including the default instrument within the "Custom page label format" of the Player field. Then the instrument field could be named "Instrument override" and you only set it if the player is performing with something other than their default instrument. This would make it a quicker process to add players to a concert.

It sounds like one of the factors that determines which roadmap items get attention first is the level of interest within the community (makes sense). But it would be good to have a more accurate and transparent gauge of the interest in each roadmap item. A simple solution would be to have an official Roadmap sub-forum with a topic for each roadmap item (separate from the Wishlist sub-forum). The community could then indicate their interest in each item by "liking" it, and give feedback or ideas about implementation in topic replies. My vote for most desirable roadmap item: Add support for custom properties in file/image fields.

$pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if(!$page->id) return; // Page ID is 0 when page is first created // Your code here });

In this post, we take a look at all that was covered in 2017, and our roadmap for 2018, which includes plans for the year ahead. https://processwire.com/blog/posts/processwire-2018-roadmap/

I used to use that module, but these day I prefer AdminOnSteroids for that functionality.

It looks like a deliberate decision to get the original Pageimage if a variation name is given. See here. So I don't think it's a bug. Perhaps the expectation is that if you want a variation you will always get that from the original Pageimage with one of the resizing methods. For example: $pageimage = $page->filesManager->getFile("/path/to/filebasename.jpg"); $variation = $pageimage->size(400,400); This seems like the way to go because that way the variation is created in the event that it was somehow removed previously. Will this work for you?

@noelboss just posted a comment in this thread and the thread is just one of many examples of people looking for solutions of a proper staging/production strategy. we have some modules that try to close this gap, but imho this is an important part of a professional workflow and therefore should be part of the core. don't know how that could be implemented exactly, but at least it would be great to have a thought-out strategy and maybe some kind of standard/best practise guide of how to keep staging/production in sync, be safe while editing, integrate GIT in this process etc. while other features are nice to have for me, this is really one thing that makes me feel totally unprofessional and is a huge pain. i don't think that the options we have so far are as good as they could be. for example if i had to push a fix to a live system, i wished it would be possible to: pull the latest version from live to dev with one click (excluding a predefined list of files / db tables) work on that dev version locally (having all files on the local computer makes searching all files a lot easier) push the fix to git push the fix to production some parts of this workflow can be done with the migrations module, some with the quite new duplicator module, some could be implemented via githooks, but, hey... we are talking about ProcessWire and where PW really shines is making our lives as devs easier and in this special case i feel that this is not true maybe i'm just too inexperienced in this topic and there are proper solutions out there, but following the forum over the last years i didn't see a solution that felt "processwire-awesome". maybe a blog-post covering this topic could be a first step. and maybe i'm totally alone with this opinion... a feature request-voting system could also help a lot here [pub] that was the tracy-boost

wp-content?

I want to see a separate channel in the forum where everybody can upload graphics, banners, animations and video clips to promote processwire.

Oh, thats perfect and simple! Just change a $config var before rendering starts!

Would be amazing and one of the only missing parts from my point of view.

Hi @adrian, I got an error on line #186 in InputfieldPhone.module. Error comes up on a created phone field. Fixed it by using double underscore. Wrote an issue in github, too. Error (with single underscore): $f->description = _('Whether to ask for extension when entering phone numbers.', __FILE__); Fix (double underscore): $f->description = __('Whether to ask for extension when entering phone numbers.', __FILE__); I got two other issues, too, but can't figure it out how that works: The phone field is in a user template called "person" (have multiple user templates), and if I set a zero at the beginning of the area code, then this zero will not be saved, as long as I write another number to it (after or before the zero). Here some examples: Number 123 -> change to 0123 -> after save: 123 Number 123 -> change to 01123 -> after save: 01123 -> change to 0123 -> after save: 01123 Number 0123 -> change to 00123 -> after save: 0123 Number 0123 -> change to 10123 -> after save: 10123 Number 123 -> change to 0456 -> after save: 0456 -> change to 0123 -> after save: 0123 Best solution for now is to delete the field and set it new. Anther Solution is to change the numbers to something else then change it back. The output on the frontend wasn't changed after the profile update, I had to save/update(select output format) the phone field again, so the output was right again. That was no caching problem, or at least no normal one.

Put the code I have posted in your ready.php and replace $this with $wire. $wire->addHookBefore('PagefilesManager::path', function ($e) { $e->replace = true; $e->return = null; });

Thank you. I didnt know this. Now it works

You may know this already, but just to explain the reason... Guest users do not have direct access to repeater pages because they live under the Admin branch (guest users can only view repeater content via a repeater field). One solution is to add "check_access=0" to the selector if it is definitely the repeater pages themselves you want to find. Or instead you might want to find the pages that the repeater pages are contained within... $container_pages = $pages->find("Images_With_Variations.title|Images_With_Variations.keywords*=" . $search_term_string);

Maybe you are logged in to admin on Chrome but not in the other browsers?

This is a good suggestion, but the action code would need to be modified in order to work in this case. By default that action copies the unformatted value from one field to another, but in this case the formatted value is needed in order for the newlines/markdown to be converted to HTML.

if you don't want to add the textformatter to the field, you can also do something like this.. $markdown = $this->wire('modules')->get("TextformatterMarkdownExtra"); $htmlVersion = $markdown->markdown($page->textarea_field,2);

Hi @Juergen - it's all about output formatting. It is off by default when bootstrapping. So just do this: $p = $pages->get(n); $p->of(true); $p->fieldname->formattedNumber // OR $p->fieldname Remember that calling $p->fieldname will actually return a formatted version by default - you don't need to explicitly specify ->formattedNumber If you don't want to turn on output formatting for the entire response, you can also use PW's getFormatted like this: $p->getFormatted('fieldname');

There is a SEO module already. I guess it's not maintained anymore, but it can be a good base for extensions. What do you miss? Personally, I don't think a SEO module belongs to the core (if it's that what you have meant by "native"), because the core should keep it's clean and generic character. Keep in mind that ProcessWire is not just used for websites, and even a lot of websites don't need that much SEO.

FYI... There is also a discussion around focal point image cropping https://github.com/processwire/processwire-requests/issues/150 if anyone is interested.

Hi guys, as I would need your support. I state to be a beginner and I met the application the day before yesterday for the first time. I'm creating a manga reading site using wiremanga and I need to know how I can incorporate altervista advertising. (this is my site if you could serve http://dgtread.altervista.org/) I have also modified some elements of both the .css and php files but despite saving they are not updated.

If there is some renewed interest, I was thinking that it might also be a good if I extended the "Shared JSON Packages" import option in Migrator to also supportt zip packages which can then include template/css/js files and assets/files. Anyway, just throwing it out there as an option to see if there is any interest.

Hi @Antonio Iorio, Regarding where to place your ads, is dependant on the ad itself. For example, a creative with wide dimensions doesn't fit in a sidebar. When I wrote the ad manager plugin fo wp many years ago, I referenced the IAB Standards for ad sizes. In your screenshot you will notice a Leaderboard 728x90 type ad. This ad is designed to display in one of three locations (I used the term zone in my plugin). This banner should be placed in the header and or footer of your page, or even between two separate sections of body content. The <script> section of your screenshot is apparently how altervista wants you to include the ads. You would simply edit your PW templates and include that script at the location you want the ad to appear. You repeat that process for all the ads you want to present. One note of caution. While ads can be a good means to generate a small income, you should use them sparingly. No user wants to weed through a bunch of ads in order to continue reading your content. So I would keep with the old axiom, less is more. I hope this helps. Let us know if you have any further questions.

VS Code is in need of one too.

ProcessFileEdit is fantastic and I think ProcessFileManager has a useful role as well when you need to create/delete/move files around and don't have your dev machine with you. Also, here's a sneak peak for the new File Editor Panel in Tracy (coming soon!). This comes with: Test (changes don't affect other users) and Restore functionality (in case you save and made a major mistake) for all file types and even continues to work if you accidentally introduced a fatal error into the code you just saved - this allows you to recover without needing FTP access. Of course this doesn't replace the functionality of ProcessFileManager at all, but another tool in the arsenal.

https://polarartistit.fi/ https://bomba.fi/ Webstores (developed by Tuspe): https://sajt.fi/ https://kupilka.fi/ (shop is only for visitors from Finland) https://tommisoidinmakiproduction.com/ Events: https://osuuskaupparock.fi/ https://karhurock.com/ We have made almost 100 projects already.

Bernhard i wrote it and i repeat it you are really my hero - the admin/backend was always a ? to me since i was flashed about all the options on the frontendside with the API, creating some little modules or changing some or using small hooks to get some results are the level i was before i read your tutorials and examples...:) Wanna share a really cool example im playing with this responsive calendar plugin: https://tympanus.net/Development/Calendario/ in an easy process module i get some results like this (with some CSS tweaks): This is with the example data from but it works like a charm and is seemless responsive within the PW admin. Code i used on the PW side is really easy: now i'm getting hands dirty on trigger some booking data and some actionbuttons... Thank you for sharing your knowlegde! I wish you a healthy and successfull year - best regards mr-fan

Recently I am fixing this issue, again, and I find this post in google. There's another solution that I found in the ListerPro forum before. The created, modified, publish date format can be changed via language translation. The language support module has to be installed in this case. Go to Setting > Language > choose the language you use > Click Find Files to Translate button > click /wire\modules\Process\ProcessPageLister\ProcessPageLister.module and submit > translate "rel" field(should be listed on top) to wanted format like Y-m-d Reference: https://github.com/processwire/processwire/blob/57b297fd1d828961b20ef29782012f75957d6886/wire/modules/Process/ProcessPageLister/ProcessPageLister.module#L238

Amending the site/config.php file by inserting the following line of code immediately after the opening <?php appears to have resolved the issue: setlocale(LC_ALL, "en_GB.utf8"); Thanks for everyone's help.

Hi abdus, Current locale:\nstring(1) "C" \n\nAvailable locales:\nzu_ZA.utf8 Yes, that was the whole of the output. The long list shows the available locales that can presumably be set. I've no idea an apparently South African locale is only showing as available when there doesn't even seem to be any South African locale option available under View Available Locales in cPanel. It is very odd. Edit: I spotted the following under the cPanel Locales Documentation: Looks like php code does ot display the locale information correctly for cPanel/WHM users. Having downloaded the cPanel english (en) locale there doesn't appear to be anything included that should cause a problem for a UK localised installation of Processwire. Any ideas on how best to proceed.

ProcessWire has language alternate fields, which basically do what you describe out of the box. Unlike multi-language fields, language alternate fields can also be used with image fields.