marcus

Oh sorry, I misread. Maybe apeisa could tell if this is possible and what frontend JS dependencies (for example) this would have.

This sounds like a case for Apeisas Thumbnail module: http://modules.processwire.com/modules/fieldtype-crop-image/ - especially for #2. Otherwise, and without a dependency for a contributed module, $image->size(400, 600); will work.

I experienced the same and had the very same $page vs. $pages situations just not long ago By the way, my code example was a bit verbose for explaining reasons, so you could shorten it to... foreach ($pages->find("template=blog-post") as $b) { ... ...as well. Same thing goes for the thumbnail example in your other topic. If you feeling save enough you can write it like so from now on - but the main thing is the understanding of its concept.

Content of $page is always the page you are currently on. In the case of visiting the home page, the fields blog_images and blog_summary do not exist, since its another template ("home", I guess). But there's a solution: $pages, the entirety of your, well, pages. In this case you "just" have to filter by template blog-post: $blogposts = $pages->find("template=blog-post"); and then: foreach ($blogposts as $b) { echo "<img src={$b->blog_images->first()->url} />"; echo "<p>{$b->blog_summary}</p>"; }

This is easy as: <ul class="thumbs"> <?php $images = $page->blog_images; foreach ($images as $image) { $thumb = $image->size(106, 106); // or whatever your thumb dimensions are echo "<li><a href='$image->url' class='fancybox'><img src='$thumb->url' alt='$image->description'></a></li>"; }?> </ul> Assumptions for this code snippet: You will be styling .thumbs via CSS to get the grid style output You are using $(".fancybox").fancybox(); as a trigger

Can you give us some context - what are you trying to achive - and why are you modifying the database directly?

Update: Apertus is abandoned in favor of a fork of the far more advanced Admin Theme Reno, "SuperReno". Download the current version on GitHub: https://github.com/marcus-herrmann/AdminThemeSuperReno An AdminTheme meant for developers Still en route to an enhanced version of the Knowledge Base Site Profile I'm now releasing an AdminTheme suited for said profile, sharing its design. This is, as usual, an early, not yet heavily tested release. It is intended to be activated for superusers only, since other themes such as Modesta or the default one are much more apt to customers and editors. Requirements Current ProcessWire 2.4.X Developement version A modern browser (but I think that's the last thing a developer is missing) Download | Project on GitHub Features Some of us work on a large number of ProcessWire installations at once. The following options aim to customize your backends to that extent that you can tell them apart within miliseconds and without looking at the URL. Therefore, within the theme's configuration (meaning: the module's settings), you can change the following: Environment indicator When using a development, staging and production version of a project, use this little switch in the theme's setting to indicate which installation you're currently on. Set main color In order to not confuse installations using Apertus, "color brand" them. Use hex, rgb(a), hsl(a), or named CSS values to your liking, but remember to apply a relatively dark color to prevail contrast. Set project name Lastly, name project backends. Shortcuts Search the forums from within every page of your ProcessWire backend Have all the important API documentation links at hand Check for new modules from every page using the tools upper right (refresh icon) Installation Copy all files from the ZIP archive to your /site/modules/ApertusAdminTheme/ directory. Click "Check for new modules" in ProcessWire Admin Modules screen. Click install for the module labeled: "Apertus Admin Theme". Background The design of this Admin Theme is based on my Knowledge Base Site Profile. Also, it is created to accompany a newer version of said Site Profile. This is the first version of Apertus, not yet heavily tested and therefore bleeding edge. Please use with caution. I named it "Apertus" (latin for open, uncovered) because of the default state of the main navigation (Page, Modules, Access,...). This is a pre-release (0.0.1) needing current dev version of PW to prepare for ProcessWire 2.5. Please help me improving the theme by reporting bugs on GitHub. Thanks! Roadmap Things I intend to implement/change in future versions: Making useful links configurable Proper responsive behaviour Refactoring JS Remove Compass dependency when compiling theme's CSS /edit: Added screenshots clarifying where to find theme's settings

Thank you for this, much more elegant approach! Unfortunately, my dev version of the module stopped working, since the install() method is not being fired anymore since, well, install. Neither field creation nor messaging via $this->message("Module is installed") works - while uninstall() goes smoothly everytime. Is this a common module beginners error caused by something else? The - inoperable - source code of this is here https://gist.github.com/marcus-herrmann/9664626db17524fa7338 - if anyone would be so nice to have a look Thanks! Nevermind Used in in new version. By the way: That this module and the Like Fieldtype share some functionality was never intended. I'm not aiming to substitute a commercial module at all. Even if, I would fail badly. It was only an existing functionality of the Knowledge Base Site Profile that needed a proper module wrapper.

So possibly "Enterprise CMS" is the wrong choice of words, since this term obviously has the notion of closed source Java monster or platinum 24/7 support. But that possible communicational opening towards decision makers (sub-large-public-company!) as well as developers, as mentioned by LostKobrakai, that's exactly what I meant. "How can PW help empowering my business website" vs. "Look no further - this CMS is able to even clean your company cars, daily!"

Also necessary, browser support for this: http://caniuse.com/#feat=multibackgrounds

No, of course not. The intention of this thread was to think about how one could emphasize PWs aptitude for business websites - as it is able to stand the test of being extandable, reliable and user friendly, to chose a few of the aspects TYPO3 advertises with. Emphasizing this alongside the other advantages already communicated, aimed at developers. No microsite, and no business model. Way too big.

In the famous "30 minutes" thread MadeMyDay somehow made a point by putting ProcessWire into context with TYPO3. Recently, I got an inquery for a multilingual website for a speaker agency. A customer looking for an Open Source solution. These speakers had meta data attached (topics, languages, speaking areas, gender) and this database would be the most essential part of the website. Also, a password protected area was needed where speakers could supply materials such as slides to an exclusive user group. Sounded like the perfect job for ProcessWire, unfortunately, after a while of internal consulting and decision-making, the customer chose TYPO3 instead. PW was totally new for them, they admitted to be fascinated by it, but went with the system they knew in the end. That, and Marc's above mentioned comment made me think. ProcessWire does a good job catering developers but still has room for improvement, in my opinion. Throughout the 30 Minutes / WP Tavern article I often read, "once the developers are on board, the rest will follow". I'm not so sure. It would not hurt to emphasize PW's abilities to serve as a business/enterprise CMS right now. Take the benefit teaser on typo3.org for example, a perfect intro. It states: Open Source Enterprise CMS Scalable Web Application Framework Large, active global community User friendly with unlimited extendability Integrated Development and Editing Workflows I guess most of these advantages do fit to ProcessWire as well or, in the case of continuous integration, are on the doorstep (at least that's how I read "Integrated Development"). And PW's community may not be large yet, but is damn active. Apart from that, the home page is full of, hm, let's say: trigger words that work on some business business owners: "enterprise", "professional", "web solutions" and "certificates". I'm not proposing to copy all this. But I have an idea: Since both TYPO3 and ProcessWire are relatively big here in Germany (each on their own scale) one could emphasize the "also a perfect business CMS" aspect on http://de.processwire.com. I guess this won't hurt "the brand" at all, but, possibly, create some insights on if and how such a communication strategy could work. /edit: These automated capitalized words in the thread title are really annoying :-/

I totally agree. Especially in Germany, TYPO3 has that weird reputation of being the best and most professional CMS/F in the room, although I perceived it on the editor/usability- and templating-side as unnecessarily complex (I tend to think that the service ecosystem that developed around this complexity tries to keep it that way). Since both TYPO3 and ProcessWire are relatively big here in Germany (each on their own scale) one could emphasize the "also a perfect business CMS" aspect on http://de.processwire.com even more Communication-wise, there's plenty to learn from the big fishes. /edit: I started a new thread on this topic since it's not really related to the WP tavern article: https://processwire.com/talk/topic/7184-lets-highlight-processwires-ability-to-be-an-enterprise-cms/