Ivan Gretsky

Welcome to the forums, 3Dots! It seems like you got everything right. In PW you almost always deal with the API which creates pages, not with the database directly. This is the best post ever about the form api: https://processwire.com/talk/topic/2089-create-simple-forms-using-api/... ...Ahh, no need to write any further - horst got it all! Edit: But I'll add a link worth exploring: http://store.di.net/collections/software/products/processwire-form-builder. It is an easy form creation module from ryan himself. With it you can create pages from form submissions in no time.

Yep, that's clear to me now. Thanks to PW I know some OOP. But I was confused by User constructor accepting template as parameter, but not accepting parent.

...ok just do it as with a regular Page $u = new User(); $u->template = "custom-user-template"; $u->parent = "custom-user-parent"; $u->save(); Sometimes you need to spoil your forum karma to get your head working as it should)

I am using this wonderfull feature to create users with different templates and under different parents. Now I need to do it via API. Looking at the source code it seems like I can easilly create a user with alternative template. But is there a way to specify parent page? Certainly I can get still just create the users as pages like here, but that does not read as well and does not allow me to use addRole().

There is a lot of places this have been discussed in the forums. If you want to know what others are using you can check something like: https://processwire.com/talk/topic/1576-css-template-framework/ https://processwire.com/talk/topic/5948-dead-simple-grid/ ...or about anything here. On that materialize thing... Can't tell for sure, but it looks quite similar to bootstrap and is probably some kind of derivative. If use Sass anyway, I prefer Susy 2 as it is almost completely customiable.

I registered with my normal twitter account and voted +1. I do not know how they use those valuable bits of private info about me, but not sure they can do something worse than twitter itself)

Ii is kind of hard to answer such a broad question. Maybe we should narrow it down to something managable? And of course this "already have been asked and answered" a number of times. pwFoo seems to be persistent in building modules related to this problem.

I think PHP Trends gets its data from github. So if we get some significant grow in likes in the latter, we will get to PHP Trends mainpage.

This is great news! Forum integrations and in-house PW realizations have been discussed a few times: https://processwire.com/talk/topic/3536-forum-integration-module/ https://processwire.com/talk/topic/6468-symphony-forum-and-pw/ https://processwire.com/talk/topic/572-release-discussions/ https://processwire.com/talk/topic/9776-forum-software/ But I have not seen one done on a live site yet. If you could expand a bit about it, it would be really valuable. I could not find any login form. Why is that? Is that part of the forum managed elsewhere or is it just hidden from unauthorized? Is there any user integration between PW and PhpBB?

Good job! Starting to write modules is like a rebirth - a few lines and suddenly you are a programmer. Congrats! I also mentioned inconsistency in naming. Better pick one name and go with it.

I am really glad this topic is brought up in the community discussion. I think we all can benefit from PW being more known and used all around the world. It does not pay off to be good at something nobody else around want to use. It is not like karate secret move you can win the fight with. Your customer has to agree and preferably desire that you use PW. More like Kamasutra than martial arts. But those are common words you all understand those thing better than me. I said about "known" and "used" in the same sentence, but those are quite different things although connected. I do not think that we can or should expect PW to be as commonly used as Wordpress or Joomla, as it is obviously targeting a narrower target audience. But we definetely wish and can expect almost everyone in the web-dev world to at least be familiar with the name. And we want it to have a positive connotation. This is a task, and if we want to achieve it, we need to know, when it is achieved. I think that we need to set goals for 2016 and track the porogress. Site visits might not be the best parameter to evaluate for this particular purpose. I am well aware of Symfony 2 framework and I entertain my thought that once I will learn it and use, but I do not visit their site anywhere near often. What other measurable metrics can we track? Backlinks? Google trends? Maybe even conduct some kind of sociological survey now and in the end of 2016? I also suggest we organize ourselves in our effort. What about conducting a number of marketing campaigns with defined goals, timeframe, and summing up in the end? I can propose a few right now: Get PW more stars on Github. So we can be rated closer to the top in the searches like "PHP CMS" and so. If we do it in condensed period of time, we can even make it to trending, which can bring us quite a number of newcommers. Get PW more reviews with stars on bitnami, which will position PW closer to the top of the apps list. Get PW atop of syn.in on alternativeto.net. I think we deserve at least No. 4 . It could be beneficial to make a dedicated forum thread for the campaign to encourage forum members to participate. We also probably want to investigate the target resource's anti-spam policies if any and organize against them. What do you think?

I did a quick search and could not find one either. Guess you are lucky: You can make a new Language Pack and take all the fame. You can make it your own - all the translation errors will fit you taste. You can learn quite a lot about the system while making a translation. You can help the thing that helps you!

Come on! Martijn steps in and gets all the likes. But what about a man who did all the diagnosis . Just kidding, glad you got the question solved .

Well, I am in confusion. I cannot understand what are you trying to do Could you write a bit more about you case? 1) What fields does the $page we are writing output for have? I assume it does have a Page Field named pageField, is that right? 2) What pages are allowed to be selected for pageField? 3) Is that right that you can only select 1 page for pageField (as you stated before)? And so on... Please provide more details.

if ($page->page_field->id == 123) { echo $page->page_field->pageUrl; } Maybe something like this?

Sounds great. But I still can't get what a task is - is it a php script, an PW API call, a bash script... Maybe I should read some code) But if you could explain... I have a need to import a hell load of pages with multiple images on a regular basis via cron job. Images should be processed before the import. Can I use the module for this, or is it an overkill and I should do shell scripts or something else?

Really good work. Looks solid and corporate. Even with the team at the ping-pong table . Could you please write a little more about how is it done. Espesially the forums. What modules did you use for it and other functionality? I really like the multi-column layout here and there. The meny semi-transparent is not enough to make the white menu items visible on some background images on the frontpage. And the open source ERP platform from Belarus is something to know about.

Could you please pick one: a) You need to check whether the page field has ANY value or b) You need to check whether the page field has a specific value (a specific page) or c) You need to check whether the page field even exist on the page's template. If a) or b) please check the Details tab of you field to see how is the field presented in the API - as an array or single page.

Hey, mr. horst! Looks like something I could make great usage of... But not sure that I understand the thing right. Could you please write a few words on what it is, what and how it is supposed to do. Maybe a use case... I understand It as a way to add multiple pages through the api without the risk of running out of execution time. Am I close?

Thanks, your points are valid. Still they show that the two are pretty similar, so the comparaison would be a nice thing to have. Maybe with preferable use cases... I do not know why, but I have an impression that PageTable is more scalable than Repeater. Or is it only from the UI point of view? Are there any difference for the page rendering time, etc? @teppo: Is there any benefit in storing PageTable pages as children?

You can look here (search for ProcessLogin). I think afterLoginRedirect() can be the one that will suit your needs.

There is such a comaraison. But now it seems to become outdated. Ryan wrote then "But PageTable will scale much further in the admin UI than Repeaters will, so I would personally favor PageTable in more situations than Repeaters", but with upgrades to Repeaters UI and the introduction of the Matrix field I think it is no longer the case. At least I cannot find significant reasons to prefer PageTable over Repeaters anymore (well, exept the licence). So I also would also ask for an updated comparaison.

This topic has been brought up several times (a couple of them by myself ). This "little" thing could help so much in building variants of admin for different roles! I really hope that the extended permissions part of this plan will somehow deal with the issue.