LostKobrakai

The backend, which is shown in your linked post, is very much custom made. The styling comes from a admin theme, which you can find here in the forum or via the module search, but the information shown by the interface are served by a custom module. If you have the time to develop those, you can build the backend to be exactly what you want it to be, just search for "process modules" for more information. These are the ones used by admin pages. Even the core backend consists of those. So processwire can do, what you intend to build, but you need to build it by yourself or together with your coder.

I don't think it's about the admin theme, but how to create custom pages (process modules) and to cater a advanced backend for clients.

+1 for this. This would be super useful, as I tend to implement theme-related options for my frontend stuff, which would be nice in a seperate admin page.

I quite like the idea, how you implemented the theme-changing in a module. But I currently don't see how you intended to get the link between the backend fields and the frontend presentation. From my point of view a theme is always more or less tightly coupled with a predefined form of content, which needs more than just some required fields to be present.

Maybe just take a look at apeisa's thumbnail modules internals. The cropping is done on an extra page, so maybe you can refactor this for your needs.

Which values does "$img" hold? There's nothing pointing to a processwire image-field, at least in your posted part of the code.

While I'm still new to the module development, I would remind you about the great api of ProcessWire. So maybe it would be better to think about a great set of helperfunctions, which reside in your module and let the template files just use those functions. Maybe take a look at the form api of processwire.

I don't know what exactly you mean by security, but I much ruther see my data go encrypted through the wire instead of plaintext. There may be security holes, but at least the attacker has to do work, instead of just sniffing the traffic and reading it. From what I can remember from a recent talk at google io about ssl, the performance hit of it is mostly the handshake, so with http-keep-alive and some other improvements the difference in performance shouldn't matter that much.

There's the discussion around redactor: https://processwire.com/talk/topic/6839-redactor-wysiwyg-editor/

I just noticed that my current version of the module doesn't support multiple instances of itself on one page, as the current inputfield id is hardcoded. I'll investigate further but I wouldn't mind if someone could lead me to a way to use the core to provide the appropriate field id suffixes for the url inputfield, which appends a number or, in the case of repeaters, the repeaterid. Edit: Did a quick fix by just altering the id and name of the already existing upload input field, so it works now for multiple instances of the url upload on one page and with repeaters.

I think there's the problem which we're talking about. Not every developer is in a position to choose a CMS, just by providing a prove / examples of it's advantages to the client. Some companies want to make their own decision, no matter what the developer has to offer. So it can't hurt to offer information for such people, just so they see, that processwire can easily be as good as some of the big ones (typo3 and so on). If there is no information stating: "This can be used for big enterprise sites", they just move another cms, which tells them to be the right and big business-cms. This doesn't have to be a big marketing campain, but one simple microsite, or a part of the already existing page should be enough. The already existing "What's unique?" and "Why ProcessWire?" seem to be very much catered to be read by developers or quite techsavvy people. A marketing member doesn't care about jquery-like api, but if it's easy to maintain for them, if it's extendable, maybe if it's "enterprice", because it has to work for "such a big" company. Honestly I think some even just want to read that everything is possible, because a friend once told them a bad story where something just couldn't be done by the developer. So they want to be in control. With one page, catered to their need in information in a well-written form, they can evaluate ProcessWire against other CMSes, if a developer aims for ProcessWire. If they need to search the page for the tiny bits of information they need, between the developer talk, they do harder to compare or even stop trying. That's what I think is missing on the current website. Nothing more.

No, didn't need to update the module further, because there was only a temporary use for it in a current project.

Nothing would change as people, who are happy with a ready to install template, wouldn't even care if it's build on processwire or in wordpress or something other. Page-profiles already do install a shiny template, but they can be build more easily/powerful as the wordpress ones. The people, who try to alter it in a serious way, will be more than happy to face a great cms with talented people on the forums. Templates aren't more than a prepacked website like all the ones we build here, only that they'll be used by more than one client. The plug&play mentality of wordpress is another issue. I work with a client, who tried to install a members-only area + simple shop on their wordpress website with only little html/css knowledge. Didn't work out for him, but that's stuff that a client should not be able to even try.

I've done it this way. I started my experience with some clan/guild cms's, learned some php with copy&paste, moved to joomla, learned more php, build my first templates, moved to wordpress, build a more sofisticated template, moved to processwire and felt free. No education other than learning by doing. With some free themes everyone could get in easily. Maybe someday they want to move some box to another place and learn about the api behind the theme. If they get interested they'll continue digging around and maybe some day develope their own themes.

The point which I miss in the discussion is quite simple. As a non-developer user wordpress is very much a blogpost-and-pages management system, not a content management system. Everyone which has the knowledge to turn wordpress into something more, also has enough knowledge to use processwire efficiently. The author of the article seems not to be one of those and even named what he wants to get a "Publishing System" in the headline. So the comparison was flawed from the beginning. He wants something, that processwire doesn't want or claim to be. The added discussion about themes, in my opinion, is also not correct. A theme is a readymade frontend-design for a specific purpose. The only difference to, what everyone here is doing only for his client, is that a theme is purchaseable/downloadable by the masses. Maybe some added simple customisation options from the backend. Just like some wordpress themes come with special extra functionality over the blogpost-and-pages base, a processwire theme does deliver only the functionality needed for the chosen purpose. In both cases, if more functionality is needed, than provided, you need someone to code the rest on top.

You could circumvent the distortion of your images with css only. img{ max-width: 100%; height: auto; } This let's the images scale propotionally. See: http://jsbin.com/yokinuke/1/edit?html,css,output

OR Selectors are in the durrent dev version: https://processwire.com/talk/topic/3768-processwire-dev-branch/page-10#entry64049. I don't know if they work for field dependencies.

Do you use some kind of caching machanism on the page? After a quick look at the sitemap script I seems like "$page->httpUrl" still outputs the old url.

You don't need the if statement, as it doesn't matter on which page you are. The menuitems are in each case the same. <?php $alalehed = $pages->get("/andmebaas/"); $children = $alalehed->children; $children->prepend($alalehed); foreach($children as $child) { $class = $child === $page ? " active" : ''; echo "<li class='sidesub$class'><a href='{$child->url}'>{$child->title}</a></li>"; } ?>

The easiest way would be to hardcode the parents id. There's no real way around some form of hardcoding, as from some source the code has to know, which site should be your root page. If you want the menu to remain slightly more dynamic you could use a page-field, where you could change the parent page from the backend. If your mentioned parent page also is the homepage, then you could use this to get the page: $parent = $pages->get("/"); This always selects the root of the processwire pagetree.

You could try "RewriteBase /" as your side is accessable via ""http://www.josbeerepoot.nl/www/". Edit: Should have read more closely. You need to have ModRewrite installed before you check this

I think hellomoto is trying to get a url structure like in wordpress (/2014/07/page-title), without creating folders for 2014 and 07. That would work, if you deligate all posts from the homepage template with three url segments.

Another way to do this would be to pack all the infos in one template and use url-segments. Could be sorted in four tabs (main / review / comments / actor) with a checkbox to enable comments and/or actors. The code would be quite similar to nico's switch example. So you don't need to check, that there aren't duplicates, because it's all one page in the backend. <?php switch($input->urlSegment(1)) { case 'review': include 'page-apage.php'; break; case 'comments': if($page->comments_enabled) include 'page-anotherpage.php'; break; case 'actors': if($page->actors_enabled) include 'gallery.php'; break; }

$mp3->$file->description should be $mp3->description

I've read this a few days ago. While of course you could implement this behavior, this is what I missed in ProcessWire for a long time. A field like this matrix thing, where one could freely combine different preselected content-types. In the current dev version you could mimic this with PageTables, but it's still not quite as convenient, as it's in Craft, because most of the information is hidden in the page-lightboxes. Also you do have the hassle to always provide a pagename for each contentblock. I use PageTables on my own website at kobrakai.de/sense/, where I can freely arrange video-, image or issuu-content. But it seems so overkill to have a page / lightbox for only an image or a video-/issuuid, just to be able to freely change the order of the apperance. To me the shown matrix-field is kinda like the perfect mixture of repeaters and PageTables.