Ivan Gretsky

You still could go the frontend way and make use of Form Builder to implement cource publishing feature and maybe profile upgrades as well. If you want to go the backend way follow kongondo's googling advice in this topic or +1 on the tutorial request in there .

I am sure that it is not a simple task to produce a tutorial like that. Maybe the screencast of a backend system of a complex site would be an easier starting point. Sometimes it is nice to actually see something done (not just know it can be) and then do it yourself.

In tutorials section of the site we are encouraged to request tutorials. This topic is such a request. ProcessWire is advertised to be great in not only building unique frontend features, but also custom backends. I would be very much interested in tutorial on building a custom backend for a site. I put some questions that could be covered in such a tutorial in a list below: How to create custom backend pages How to change the default starting page for admin users How to serve different backends to different users depending on roles How to style the page tree (I have seen it styled in some Soma's video tutorials, so it is a request for a best practice or an advice) Anything else you think appropriate here))) If someone could generously provide a screencast of a custom backend workflow it would be great tutorial in itself.

The thread starts with WP and Drupal screenshots. I just wanted to point out that the menu components of those systems may differ greatly from what you and kongondo intend to implement as a module. And those coming from those systems may be confused. I know that as I came from Joomla and it took some time to start to understand why is there no menu system in PW by default. In fact there is, but it is built in the page-tree. Personally I try to use as many default features as possible while working with ProcessWire. It makes me feel safer and pushes me to learn more of it's API and PHP in general. Thats why I think that "virtual page-tree branch" is preferable approach. But in no way do I deny the possible need for a menu builder module and even can imagine using it myself in some cases.

I think, you are right - you will have to rebuild everything in the front-end. Maybe not from scratch, but from some UI library like JQuery UI or YUI. And if you are new to ProcessWire and PHP it might be some hard way to take. Though it is possible to do, I would advise to take a look at some out-of-the-box systems like Moodle before making a decision.

I guess the main reason for menu system components in many CMS's (Joomla! for example) is that it helps build URL structure of the site. So in those systems you create pages (articles, nodes and so on) with no relations to other pages. And after that, with the help of menu system you apply structure to those pages (define what page is child to another and so on). That structure shows itself in the URLs (and causes duplicate URLs, by the way). In PW you just can't create a page out of the page-tree. And that page-tree is a structure in itself. So in most cases there is no need for a separate menu system. If you do not need the URL structure change, a "virtual" page-tree branch seems to provide custom menu functuanality without a module. But if you need to build a URL structure different from the page-tree structure, the modules proposed will not help, at least as I can understand them. URL segments are probably the advised way to do custom URL structure. So menu builder modules could somehow trick the user, who has experience in other CMS's, instead of helping him to understand how PW works.

I just went to redactor official site and the big red buy button is kind of making a call not to include it in a GPL system . And the FAQ section just makes you sure about that. Though it surelly could be done (after purchasing, of cource), as other wysiwygs already made their way into PW. Just see those: http://modules.processwire.com/modules/inputfield-ace-editor/ http://modules.processwire.com/modules/inputfield-trumbowyg/ I think Nico even made his own one, but can find it right now. But I guess the best part of a built in editor is its integration into the system (like image inserts). And it is done quite right in PW. More to that, it is quite easy in PW to make adjustments to the editor options from the admin, which is really cool. I did not know those options even exist untill I started with PW. So I would stick to the default one most of the times. Really cool that CKE is now the default. Just to mention, TinyMCE 4 has a great looking skin now and works fine.

The forum is alright, but the main PW site should make a switch )))

PHP is default on most shared hosting servers nowadays. It is much easier and cheeper to get a site running than with NodeJS, for example. So it seems like a better choice for SMB and therefore developers that just start their career as freelancers.

I would agree with #4. It would be really usefull to have all the valuable forum answeres structured somehow and easy to search. Tutorials are great but they tend to cover basic questions and are not structured in any order. Wiki could be the place, but it does not seem to evolve. Cheatsheet is api reference, a more low-level stuff. We should produce a nice learning curve for the newcomers, so after the 30 minutes with PW they still would learn only a bit, but not turn away. Rather the should find a shining perspective in front of them . I thought about managing some sort of a forum guide (actually started it for myself following valuable topics) which could be a forum topic of it's own, a wiki page or a page in the DOCs section. Those, who are only on the stage of combining plugins will never switch to PW. But those, who understand the need for a customizible solution could have used some kind of a manual or guide.

I got download buttons in the API section not showing right in Firefox. Chrome and IE got them right. Please check if it is not my browser cache or something.

I have not found any topic to report issues on the processwire site and forum and/or make suggestions about them, so I made this one. If such a topic or branch already exists, it should be there. On PW site there is now Docs menu item instead of the API (as it used to be). But on the forum it is still API. They even lead to different pages. I guess this should be fixed.

Yep, this one looks great and more detailes would be appreciated. Maybe a little case study?

How about this? Starter - $page Newbie - $page->name Jr Member - $pages-get("postCount > 10") Full Member - $config->urls->root sr Member - $config->urls->core Hero Members - $page->created <= 1292025599

Actially I figured most of it out before starting this topic. So it is my +2 for now to become Senior . The thing I could not get is Destinguished (@diogo: I got profields, but it's not enough). But most of all I am intrigued by the newly formed pw-moderators group (which got more modest blue font since the middle of this conversation). It seems that community gets more organized. There are some improvements on the PW site (the news on the frontpage, the tutorials) also. So It will be really interesting to find out about it. A couple of times I reported spam on the forum. Maybe now you should just PM mr. Joss the Graduate?

All the cool kids got the new badges. Personally I feel kinda motivated to progress through the ladder of those member titles and groups. At least, sometimes I look at those little info blocks under the avatar pictures and compare the contribution made by the post author to the good of all PW community to my own negligible achievements. This gamification is there in place for a reason )) So please could someone open the rules of the game! What should you do to become "Distinguished" and so on. What groups are there? And is there anything beyound the 33 degree?

I was thinking about starting an e-commerse skeleton profile myself, but I am really happy someone with more experience is already doing the job so expected and timely! If there is a way to take part in this great endeavour (like testing or just pushing that "like this" button) please let us know.

Couln't we get those dimensions from the image-file itself? After loading? I guess getting those from the attributes is not even reliable. And what is that nosize variable doing there? It is populated from "data-nosize" attribute which we should somehow be able to set... I am not so good at this yet to figure this out, but it seems like this can and should be done here, not via the module. But diogo is surely "the man" that moves PW to be more responsive-ready. Did not see Soma's reply. Нe is "the other man" .

Maybe they just hacked your site but not domain? Ping the url and see, where this page lives. Maybe it is on your server.

Nailed it! It is not in the TinyMCE but in the pwimage plugin to it (in the PW core - editor_plugin.js). You can comment out 2 strings and it will work like you want it. There is even a check on some flag "nosize" which should do the work without a hack. I just can't find a place to define it in the admin. (something else is going on here). I guess, we could ask to add an option to leave widths but no heights to the images inserted in TInyMCE fields.

In TinyMCE 4 you can just add image_dimensions: false and it will solve the issue. Just tried it out on 3.5.11 and it does not seem to work, so the module is a solution until version 4+ of MCE will be integrated into PW. Did not try on CKEditor - maybe it has it already.

Was thinking about the possible implementations of this outside your KB site profile... Could it be used in online-stores for something like "wishlist" or "to see later"?

@kongondo But not everyone will be here long enough to find that out. I never went to joomla forums doing sites with it. When I first came to PW site, I was not even sure it is alive. But I think it is our common interest to make PW more widely known. And placing that profile in the directory can help that just a little bit

@marcus: I think profiles can really push PW forward. For the developers starting their way with the CMS (like me) it is a good way to learn by reading someone else's code. For the non-coders it is certainly easier to start with a profile. I found out about this one only due to Teppo's flamingruby blog, while having visited site profiles page several times. If it is not as polished as it could be, you can mark it as "early beta" (but as everything good in modules directory seems to be in beta it probably won't stop anyone) . I think some communities shall grow around those profiles. Reading that PW vs WP article I started thinking that Processwire is the tool for building Wordpress-like systems (and Ryan's blog profile is the proof to that). But not only Wordpress-like. We should have both examples of the capability of PW and easy to use systems (read "profiles") build on it. Your profile is both. If I got it right you used Pure css framework, which is not demonstrated in other profiles. So only that is worth looking at.

Could not find this profile in the modules directory. Please do post there, because it is worth sharing for sure!