Leaderboard

Hi folks! tonight i searched a tool for create an UML directly from the source code of PW. The result is a 9MB of PNG Enjoy it http://zoom.it/hT0q

Nienburg Mittelweser is a Region in Lower Saxony/Germany. Our Job was to create an official campaign that engages young familys and skilled workers to settle down in Nienburg. The campaign tries to communicate the benefits of deceleration and living in an rural region in a sympathetic way. Apart from developing the whole Logo/CD/Imagery/Text our job was to create a Microsite that gives interested people a brief overview of the benefits of living in this region. The microsite is (of course/as usual) powered by processwire. http://einfach-lebenswert.net/ For those who don't speak german ( ) here are the 3 keyvisuals headlines translated in english: --> GROSSBAUSTELLE = Large construction site [in Nienburg-Mittelweser] --> KONSUMTERROR = pressures of a materialistic society [in Nienburg-Mittelweser] --> RUSH HOUR = Rush Hour

Sorry, the login page has its own page... I was too quickly! Please change the other value back to '10'. The page we want has pages_id=23. The right Process has ID=10 So this should work: 1) Make a backup of current DB! 2) In table pages: Entry with id=23 must have templates_id=2 3) In table field_process: Add new entry => pages_id=23, data=10

@Sanyaissues You have to loop through the lines of your csv and for each line check whether the page for your current product has already been created. If so, just add a new brand item to its repeater and save it. If the page hasn't been created yet, add the page, populate its fields and first brand item and save it. That's it.

Hi icreation Actually, this should not be a problem at all. The PW resizing actually creates a new image, it does not just change it with CSS, so you do not end up with any css conflicts. However, with Bootstrap 3, for the image to be responsive you need to add the class img-responsive to the img tag - unlike Bootstrap 2, it is not responsive by default. If you are just allowing them to upload an image, then you can simply add this to the image output on the template. If, you are allowing them to add an image via one of the RTEs then you can still add this using a bit of jquery to add the class.

did you tried a new installation or a update? With clean new installation (actual 2.3.15) you get the classic color scheme preselected as default. Also the radio button is checked in the modules settings.

Just as a sidenote regarding clients uploading tremendous large images: Also wanted to mention that you can set a max image dimension in the image field input settings. This allows to for xample say 1280 x 1280 is max and any image uploaded that exceeds the max with or height gets resized to 1280. This is one of the best settings cause it helps keeping images in a reasonable size when uploaded. If you combine it with the ImageMinSize module you could even have a min size.

Have hard time understanding your namings and relations and some of the code doesnt make sense to me imediately. I dont know google maps marker module as i never used it yet but looking at the description of the markup module i think you have to specify the fields name in the option array and not a value like you do with $feature->url ... It would have to be the name of the field like 'url'. See https://github.com/ryancramerdesign/FieldtypeMapMarker/blob/master/MarkupGoogleMap.module#L73 you seem to misunderstand this, same as with the rss feed markup module. As you dont give a field name the but a the url of the last item in your foreach loop i can imagine the markup module doesnt find it and gives url of the page. Since i think you dont want the url of the page that you give to the markers via your page array but from one of your relation to another page, you would need a simple property hook to set that url to a new property (=field) for each page, that you can then give the name to the options array. Or since you already loop and add your pages to the markers page array you could set it right there. So bfd_events_places_id_list is now what exactly? A page field? If its a single page field... The id in the name is confusing to me as it would be a Page object actually and not an id. Anyway. If it is a page field you could try using it to add a url to it on the fly. $myentry = $feature->bfd_events_places_id_list; $myentry->markerUrl = $feature->url; // or whatever url $markers->add($myentry); Then use that 'markerUrl' we added to the marker page in the options array... 'markerLinkField' = 'markerUrl'

Thanks apeisa! All the content is actually linkable. Every content has it's own "physical" deeplink which is loaded via ajax on click. So if javascript is inactive the link will open a normal content page. The second benefit (apart from the site beeing accessible without js and less overhead) is SEO: All contents can be indexed individually. Take this link for example: http://einfach-lebenswert.net/naeher-dran-leben/erzeuger-und-maerkte/ - If you open it you'll be redirected to the homepage (this was a customer request :/) if you've got JS enabled. Otherwise you'll be seeing just a normal details page of the article.

More links for you... http://processwire.com/talk/topic/3619-updating-repeaters-via-api-without-removeall/ http://processwire.com/talk/topic/3969-problem-repeaters-why-u-no-save/?p=38938 Seems you may have to save repeaters individually as well...and not just the page? Maybe that's just for editing? But if adding a second item to a repeater, maybe that is editing? Try and see Edit: Just to reiterate what's on the other thread and in above posts. Repeaters are themselves "hidden" pages. So, You have to iterate through the repeaters and treat them one by one as if they were normal pages.

Hi Sanyaissues, slkwrm already gave you correct answer, but it looks to me that there is a little misunderstandig (not sure, but could be). I think slkwrm suggested that you have organized your csv-file something like that: Product one, /category/xxx/, /brands/zz1/, "This is the brand one" Product one, /category/xxx/, /brands/zz2/, "This is the brand two" Product two, /category/yyy/, /brands/zz3/, "This is the brand three" Product two, /category/yyy/, /brands/zz4/, "This is the brand four" Product three, /category/zzz/, /brands/zz5/, "This is the brand five" But seems it is bit different: Product one, /category/xxx/, /brands/zz1/, "This is the brand one", /brands/zz3/, "Description 3" Product two, /category/yyy/, /brands/zz2/, "This is the brand two", /brands/zz4/, "Description 4", /brands/zz5/, "Description 5" Product three, /category/nnn/, /brands/zz7/, "Custom description 7" You have to iterate over the lines of your csv file add a new page, add title and category and when coming to the brands you can add the first repeater-item as you showed above. If you have more than one (looks like it can differ), you should save the page! and after that iterate over the brands and foreach you have to add it and to save the page, (I think) $productPage->title = $title; $productPage->category = $categoryName; $repeater = $productPage->items->getNew(); $repeater->brand = $brandName; $repeater->description = $description; $productPage->save(); // check / get your brands foreach($myBrands as $brand) { $repeater = $productPage->items->getNew(); $repeater->brand = $brand['name']; $repeater->description = $brand['description']; $productPage->save(); } Don't know if this is an elegant way, but should work (haven't tested) . >> Please refer to the api: http://processwire.com/api/fieldtypes/repeaters/ look after "Using the API to add or remove repeater items"

Very beautiful and functions very well! Also superb implementation for mobile also (I was very surprised when viewed it with desktop after using mobile version). What I see as a drawback is that site has too much content for single page website. Lot's of big sections, that are not linkable.

Yep, I just ran that command on my server without rsvg compiled in and that's exactly the same output I get. Hopefully they are willing to fix it for you. Let us know how you go.

I should have added, "ugly" is relative . You are right, I wouldn't lose sleep over the dotted lines

Thanks a lot! Concerning the Issues: - Scrolling: I will discuss this with my coworkers. But I think that's a pretty good idea. - We usually don't remove outlines for the sake of keeping keyboard navigation functional. As there already is hiliting in the navigation this propably isn't necessary but I don't think it's that "ugly". Thanks for the hint. I fixed the images (just forgot to do that before going live). They should be A LOT smaller now

hihi, this is a funny translation, isn't it? the site is great, congratulations. i love sites with big visuals. though i also experience loading times when scrolling (10 mbit dsl). and a map could have been an advantage, not everybody knows where to find nienburg-weser-region ... ;-)

Hi Felix - nice looking site. Just a quick comment though - those images are nearly 500KB, so when I first started scrolling down, the images weren't showing. A quick look in Photoshop suggests that they could easily be half the size without any loss of quality.

Felix, this is a very beautiful site! One of the best I've seen showcased here! Two issues: - Jumping to sections is a bit too fast for me. - There's an issue with the way menus hovering over each other (can't describe it well) but will edit this post and try again - OK, let me try again: The menus at the top allow the visitor to quickly jump through sections. Once one has jumped to a section, that section's menu is displayed at the bottom of the screen. One would expect that clicking on them the page would scroll down to view the content. That doesn't happen..one has to scroll manually. E.g., If I click on "in balance", I am taken to the right section. However, (and this comes naturally), when I click on Sport und Freizit, I would expect the page to scroll ... Hope I make sense. But very nice site, cheers! Edit: Third issue: - In Firefox, one sees the ugly dotted outlines around the section menu links.Maybe needs a -moz-focus-inner border:0, unless this is intentional, of course

Sublimevideo does look pretty good actually. I was initially put off with the need to register. Also, I can see the advantages to their tracking of video views etc, but some users might not like that. I do think the CDN approach is great though - one less thing to have to keep updated and of course means no need to include any extra files with this module, so I think it might actually make for a nice default setup. I'll work on the module config to allow you to enter your personal token and provide a video_field->render() method that uses their player. Of course you could still always use your own player using the various components like I outlined in the first post. Will be back with something implementing this soon.

$arr = $page->images->getArray(); $arr2 = array_chunk($arr,2); foreach($arr2 as $key => $chunk){ $content .= "chunk$key<br>"; foreach($chunk as $c){ $content .= "$c->url<br>"; } } Though not sure if getArray() really is optimal, but I guess so. But like the idea of chunk() for WireArrays maybe.

Don't be afraid of PW and its modules, hooks etc. They're worth learning and not really complicated if you grasp the concept, really. Compared to other systems this is fairly simple. I showed you an example of a property hook in the RSS markup thread remember? Also there's some infos on the forum or other resources that would help you understand (I think teppo's write up here is also good). And of course the HelloWorld.module that comes with default install shows exactly those simple hooks. Play around with it and be in awe!

what about sublimevideo?

jacmaes, Sorry for the delay on this, but I have finally pushed a new version to GitHub and also submitted it to the modules directory. The modules configuration settings now allows you to specify a variety of image quality settings for JPG and PNG outputs, but please note that for this to function as expected you need PW 2.4 or a late 2.3 dev version that supports field dependencies. Please test and let me know if you have any suggestions. I'd also like to reiterate how important it is to have imagemagick compiled with rsvg - I was testing this for the first time on a server without it and the quality was not great. Added new screenshots and details to the first post above too.

Hello, I want to tell the other children something: The "Green Monster" is really just a young man! I am 8 years old and also know ProcessWire. My father writes a lot on ProcessWire.

Nobody? I don't have a testcase setup handy but I think you just need to stop home (id:1) from the entering the dropdown-toggle code, maybe: // first level items need additional attr if($item->numChildren(true) && count($item->parents) < 2 && !$item->id=1){ $title = $item->get("title|name"); $event->return = '<a href="#" class="dropdown-toggle" data-toggle="dropdown">' . $title . ' <b class="caret"></b></a>'; } ... I'm not sure I understand what you mean by the "and make it href link work just for that parent?" Yes you can. 'parent_class' => 'active', // string (default 'parent') overwrite class name for current parent levels

You could definitely use PW to build Facebook (feature wise). There is absolutely no reason to worry about being biggest and most active website of all, before you haven't written a line of code for the project. I have build websites for over 15 years (8 of them professionally) and there have been very few scalability issues. But oh boy I have worried. The very same question that epreston asked: does it scale? After these 15 years I am pretty sure it is much harder to build service that will be so popular that actually needs to be scaled - than the actual scaling.

there is also a short way to write it in PHP. Maybe you know it from JS: $image = $page->images->first(); $img = ($image->width >= $image->height) ? $image->width(900) : $image->height(900); echo "<img src='{$img->url}' alt=''>";

Something like this? $image = $page->images->first(); $img = null; if ($image->width >= $image->height) { // Lancscape $img = $image->width(900); } else { // Portrait $img = $image->height(900); } echo "<img src='{$img->url}' alt=''>";

$config->minify = new FilenameArray(); $config->minify->add("test.js"); $config->minify->add("test2.js");

At least in ProcessWire, the tree is far more scalable than a linear bucket system like in EE. If it helps to conceptualize, think of ProcessWire as having a tree of buckets. This is the natural way the web works. If a single-level linear bucket system suits your needs, then you can do this in ProcessWire. But there's a good chance you can do much better. So I would argue that your statement about buckets vs. trees is backwards. In terms of scalability, a tree will take you much farther. But it does require that each branch in that tree have the ability to function as an unlimited bucket. This is exactly what ProcessWire does. Also consider that websites have hierarchy by nature, need and design. That hierarchy is extremely useful and powerful, and should be embraced. Websites lacking hierarchy would be limited, for obvious reasons. When working with a linear bucket system, you are always mapping a hierarchal system to buckets. This has always struck me as completely unnecessary, complicated and unfortunate. This mapping and conversion is ultimately a side effect of having to reduce a powerful system of tree hierarchy (upon which the web is based) to a less powerful bucket system. But if the system embraces the natural hierarchy of the web, then no mapping or conversion is necessary. You are working with the tree either way. The question is whether the system is embracing and using it (like ProcessWire), or mapping it to a more limited system of linear buckets. I don't have enough experience with MODX to know what the "resource tree shortcoming is", but am guessing it's something to do with pagination that others have mentioned before? I know that MODX has a reputation for being quite scalable, so would guess that they just have a different approach to managing that scale. But once you have worked with trees, and really experienced the benefits, it's very difficult to go back to buckets, IMO. The words "tree" and "shortcoming" simply do not go together. As for keeping more than one CMS in your toolbox, I think that's always a good idea. It sounds like MODX and ProcessWire have common ground in terms of philosophy, and these two would be good to have in your toolbox. I don't think I would bother with keeping a bucket-based system in your toolbox, except for perhaps WordPress, which can be handy in the right situations (like one-off blogs when client has very limited budget). ProcessWire is pretty much infinitely scalable, within the boundaries of a server, SQL database and file system. As scale increases, you do have to practice care in how you use the API. ProcessWire gives you a lot of power, and will fill up your memory if you tell it to. So you have to use common sense when using the API at the large scale. For example, an API call like $page->children(); might be referring to a million pages. Do you really want to load and display links to a million pages at once? (probably not). Does the server have enough RAM to keep a million pages in memory at once? (not likely). So you accommodate scale by specifying limits and using pagination, like $page->children("limit=50"); This is something you don't necessarily have to consider at the smaller scale. But I think it's a good practice to design and develop every site as if it could grow infinitely. Do you need to learn PHP? Not any more than you would need to learn the {tags} from another system, like EE. The time investment and scope of what you'd have to learn would be about the same, maybe even less with ProcessWire. In fact, you can do almost anything in ProcessWire by simply learning how to use just two API variables: $page and $pages, and knowing what a PageArray is. There are a few bonuses you get from learning PHP vs. a tag system though: Whatever you learn about PHP is something you can take with you, beyond ProcessWire. The more you learn about PHP, the more you can do, both inside and outside ProcessWire. Meaning, the environment can grow with you, when and if you want it to. Whereas, at some point, you'll start hitting your head on the ceiling in a {tag} environment. ProcessWire's API is identical regardless of context. You can be in a template file, command line script, plugin/module, etc., and everything works the same. In a {tag} environment, if you want to grow and learn plugin/module development, you'll be starting from scratch. In ProcessWire, everything you learn applies throughout the system in any context. It's only a small step to go from building templates to building modules. In {tag} systems, it's a canyon. In fairness, while you don't need to know much about PHP to effectively use ProcessWire, you may indeed need to learn more PHP to accomplish some of the things you've set out to do: paid membership and access, member signup forms, etc. ProcessWire is a tool more than a turn-key solution for these particular needs. While they aren't difficult to accomplish, you might find yourself doing more on the code side than you would with a system that has turn-key solutions for membership sites. If your project budget/timeline doesn't give you the room to learn and build these things, you would want to investigate more ready-to-use solutions for these. But I think you would do well to make friends with and use ProcessWire either way.

I had to give back the nice mention on Joss's song

Okay this was very short notice so it is incredibly rough! But this is for Diogo and all those others wedded to PW http://21stcenturyblues.co.uk/pwdream1.mp3 (Organized, try listening at less than 120db!)