Ivan Gretsky

My best guess is that Germans support both David Hasselhoff and Ryan Cramer because both have German last names (and maybe origins - Hasselhoff does for sure). If Ryan's last name was Ivanov he could be much more popular in Russia. But your question @Robin S is pretty interesting marketing wise. Could this be part of the answer?

Looking at this It seems like I should be with you guys. But damn, who is David Hasselhoff? I read Wikipedia but still do not get it. Or should I believe the stats and ask @teppo? And PW is definitely at home at Germany.

Looking at the url we can easily see that there is more going on in the private area... Or where do those extra 945 come from? BTW I was scared for a moment that it is 14000 topics by you, @horst ))

Awesome idea and bad ass realization @adrian! (pardon my French) I did not install yet but will do soon and check it out. As @szabesz said collaboration is the baddest part. I can expect a load of wise stuff to learn from those actions contributed by PW gurus. It just might happen that there will be a lot of actions - maybe put them in a folder? And one question about the backup. It seems it is custom and not integrated with db backup module. Is there a reason for that?

Good day! You already listed two best ways to get started: going through tutorials and reading the code available. Nothing will get you any further but starting a project, facing questions and finding answers in the forum or asking for help. Everybody here has walked this way. So good luck on this one the most exciting journeys in your webdev career! Viam supervadet vadens.

@Pierre-Luc Thank you for your module! Please keep it going. Here are my wishes for the development roadmap. Make it possible to fully customize the markup. Maybe with some kind of template overrides or something. I think there is no need for anything default, rather an easy way to make it your own. Ajax would be a good option. A bit more docs would help. I did experience some bugs when using it with installation having users with multiple templates. It took some time to figure out that I should configure the passwordResetUser field to use multiple templates. And there should be a 1.0.0 version in the module directory, of course. I did check it on 3.x - seems to work fine.

Now you can do it even easier: wire()->addHookProperty('Page(template=basic-page)::hello', function($event)) { $event->return = 'hi'; });

Hey man! I do not know about a straight forward way to place template files in subfolders. I remember that I did struggle with it when I was new to the system. But know I do not think about it as a limitation. There are a lot of ways to organize the structure of your template folder, and none of them will limit you to include any kind of blocks from other folders. Just look at this and you'll have it figured out. If not - feel free to ask for details.

That is a great topic! Hope to find out about more of the cool stuff from you people, so please keep it coming! Here is my little addition to the list: Deployer - a deployment tool written in PHP. I am working with it deploying PW projects. Think of it a s Capistrano on PHP. The project is mostly a one man show similarly to ProcessWire. The author asked for support recently. I am the first and pitifully the only one on the bakers list yet. As I like the project a lot I encourage you to try it out in your deployment process and give it a little support if you can afford it and find it useful. ERPNext - an open source python+js based ERP from India. I like a lot playing with it but just do not have the courage to start using. It is configurable, said to have easy and powerfull API just like PW and looks good. And it is true opensource comparing to competitors. Zabbix - a powerful infrastructure monitoring service from Russia. Something like nagios but fully opensource. A thing to monitor your servers uptime and site availability.

It is better to deploy all the shared resources after the initial deploy with deployer script, as all the folders needed are already created then. I wrote a couple of tasks right there in deployer file to upload the resources. Something like: /** * Upload ProcessWire assets folder */ task('upload_assets', function () { upload('site/assets', '{{deploy_path}}/shared/site/assets'); }); You actually only have to run it once via cli when in production, but could be handy while developing or on a semi-static site. In the latter case you can even include this task in the main deploy task. P.S. I actually decided to include config.php and the wire folder to my version control as @Wanze once suggested. It makes it much easier to deploy (and a proper composer way probably will not come any time soon). So my configuration now is more defined comparing to these vague thought described here - I put everything but the assets folder and the compiled static assets (I use gulp workflow, so only frontend sources are version controlled) in git. As I (for now) always deploy from the local machine. I compile frontend assets locally as a part of deployment process and upload them to the server in a task similar to one presented above. I even managed to make tasks for database upgrade. But it is not really useful as I can't simply upgrade db on production this way. I hope to master @LostKobrakai's Migrations one of these days and include them to the workflow.

You 're on PW forums, man! We wouldn't be here if we didn't think that PW deserves all 10s . So do not count on us - try it. Seriously I think that PW could be the best choice for that what you are after. There are some large scale projects with millions of pages done with ProcessWire. And security is one of the first priorities of the development team.

Hey darkmesaia! (it is so enjoyable how you can welcome people with such names without a doubt on Internets ) Welcome to the forums! If you need a customizable CMS - ProcessWire is certainly one of the best. Go ahead and try it. You can change almost everything on the frontend and a lot in the admin area. Give it a try. ProcessWire is not based on any of the general purpose php frameworks. But it has a set of features built in you would expect from a framework. And you can always extend with community modules or composer packages. I would say ProcessWire would save quite some time comparing to building a CMS from scratch. Feel free to ask further. Or just dive in and try building something with the help of the tutorials.

@kongondo, did you have a chance to check if @Michael van Laar's pull request fixes the new version issue? A life without Menu Builder is not so bright for some of us)))

One might want to use regions to make them easier to pass around and not to conflict with existing variables. But anyone coming to project from outside of PW has to read the blog or the code to guess what that + means.

My opinion is that there always should be a verbose, but obvious way to do things. And a cool shortcut way like the +. The verbose obvious and native to PHP way would probably be the 3rd argument. With variables we just do .=, which is a language native construction and easy to understand by anybody, not only someone like @horst , me or anyone who loves PW and reads every blog post.

It is always important to eat your own dog food. It is interesting how coming to site design with PHPStorm at hands can change the whole API paradigm at once) As now we have at least 3 ways to call an API variable it would be incredibly important to have a detailed explanation about how to take a decision what to choose. Most of us used to use $page, but newcomers starting with demo profile will be using page(), and we are not even touching on wire() and $wire. It seems like @ryan is more into the function interface (you wouldn't be inventing it other way, would you). Please consider making an article about when to choose what, if you got time. I really like the regions functionality, but the + at the beginning and at the end seems magical and probably goes against the initial functional interface intention to have closer IDE integration. I do not think this could be advised by IDE (or am I missing something?) Is there or should there be other more convenient way to append and prepend to regions?

Ok, I think I got this figured out. When you call something like $map->render($page, 'map', array('id' => 'jsMap',)); with the id option the wrapper MarkupGoogleMap js object is created with the same name as id provided. The google maps object is accessible as its map property, like this: jsMap.map; with all the good stuff from the API at your disposal.

Cool! That immediately comes to mind is some wild wishes: add a generation script @LostKobrakai's Migrations and we got a nice GUI-based migrations for PW; add comparison to remote installation. Big thanks!

@bernhard Thanks for that. But the thing I do not understand is how to get the right map object in js. It should be instantiated already by that render method (hope I am using the right terms))

Good day! Really sorry if this has been answered - I really tried to read through 17 pages of this topic, but I could easily miss something. I need to implement map re-center on window resize. I found this tip among others, but I just do not know where to put the code). I generate markup in php the standard way like this: <?php echo $map->render($page, 'map', array('height' => '400px')); ?> Please point me to the place I can put all those event listeners from the Google maps API.

That is a nice question that has been risen a few times in a context of paid ryan's and apeisa's modules. I do not think there is a solution to this yet.

I think this one little upgrade is worth being mentioned in the blog post. If I get it right, we are finally able to address page save and field save events for the page in one hook! Wow!

I have large images on a site which I will be creating variations from. The customer wants to watermark-protect large images. That is possible to do with @horst's Page Image Manipulator. I will be also creating thumbnail images, which do not require watermark. The problem is it is quite easy to guess the url to the original image from the variation name. Is there a way I can restrict the access to original images?

I think that embedded goggle map object will auto scale to its container and will fit much better, than static image. I would do that if there were no restrictions on using it.

I can't remember where and if it is even true at all, but it seems to me I saw some helper functions in PW to do exactly that - summaries limited by words + ellipsis. Does anyone know what I am talking about?