MadeMyDay

Why not use a page field and select the origin entry?

Well, a lot in parallel atm. Until the end of the year there will be some more Thank you

Stroke upon stroke... Another one online: http://aureliusinvest.com/en/ (english) and http://aureliusinvest.de (german) German Investment Company. Porting old website from MODX to PW (by hand mostly), added some more emotional imagery and a bit more what they actually do and how they work. Nothing special to say about the used modules, it is mainly content and images which has to be managed by PW.

I just merged the two PRs, don't see any side effects. But decided to turn off of after rendering just in case... (btw: I think I didn't procede the PRs correctly, merged a lot in circles, sorry for that )

I'd gladly accept the pull request. But I totally don't understand why output formatting is off in the first place. Some general admin thing? Would make sense, but then I think it wouldn't be the best idea to simply turn it on. Perhaps there is a reason for setting it to off? Does anyone know why? Btw: I am thinking of building a version where the rows get rendered in an Iframe (pretty much like Form Builder does), so we have a more sandboxed solution. Not quite sure about the additional work needed though.

Sure. This is the structure, nothing special so far ("Zubehör" is "Accessoires", a hidden node). Under that node, the client can build accessoire categories and in that single items. These items can consist of several different item variations and multiple images. This is the UI for the accessoire items: You see the Pro Field Multiplier for the item variations (unfortunately I had to double/triple that because it is not yet multi language aware). Will try to extend the language field tabs for also tabbing alternate language fields. Each product has a page field for selecting either accessoire items or whole categories: In this accessoire template I then list the items and them into the accessoire tab. The product features are filled with the ProField textarea, in the template I only render the features that are filled. One special here: German is master data, for language variations they only have to edit the changed feature. If you have further questions, go ahead! Thanks, fixed. This is just a helper navigation item for mobile, I forgot to redirect it to the first child. sure, will tell the client to rename it. Thx again!

They had one corporate color, surprisingly orange ;-) Text is written by the client and also the pictures are taken by them. These images – although made by amateurs – were of such good (and authentic) quality I decided to give them prominent space. Interesting sidenote: My original first draft (http://rokamat.siebennull.com/) had standard slider, but they said: "well, we like that, but our application imagery is always in portrait mode because of the handling of those machines. So I went with something different ;-) Nothing special. It's a alphatransparent PNG which is placed on top of the images. A bit expensive because of the wall structure though (couldn't cut it below 170kb ). But the whole slider is not loaded at all on mobile, so I think it is okay. the height is calculated on load/resize with JS.

Another one out of the door: http://www.rokamat.com/ A very nice little family-driven company which mainly builds grinders. Focus on that site is the presentation of their products with their fields of application. There is a kind of complex logic behind the accessoires database. There are single items, families and so on. These can be added to each product individually (thanks to page selector ). For example: http://www.rokamat.com/en/produkte/grinders/rokamat-chameleon/#zubehoer Additionally there is a dealer section with offers only for dealers. Not yet online is the dealer search where customers can search by address and get nicely displayed map entries (will update the post when ready). First time I used the new Pro Fields (Multiplier and the Profield Table), very nice

Since the standard behaviour of the file field is to not overwrite files, I think yes. But I also think the language management should handle it different. What you can do is find the folder in assets/files/pages/ holding the files (while editing the language the id is shown in the address bar), delete all of it and reupload again. Not elegant but should work.

Seems legit. If you use a plain HTML5 solution it is sufficient to set the src of the file to "", the browser stops downloading it. When clicked again, you can set the src again and the browser starts downloading again. But I think this is no big benefit for your project (one less request), so I think your solution is fine.

Hi Joss, looks good. But I wouldn't empty() the loaded content, just hide it. And before loading (new) content first check if it already has been loaded, then prevent loading it again and just display it. Doesn't cost you a lot of rewriting but your users will thank you for not loading the same content more often as needed

fixed, thx. And I nominate PageTable itself, without that it wouldn't be possible But thank you very much

Pushed an update to the module: New settings: Path to TemplatesIf you use a delegated template approach, please provide your path to the templates (relative to templates directory). Collapse unpublished rowsIf checked, unpublished PageTable parts are rendered collapsed and can be opened on click. (hidden) CSS classes for PageTable page statusThe rendered parts (the div.renderedLayout) get the status of the page as CSS class: ".pte-hidden" for hidden pages ".pte-unpublished" for unpublished pages ".pte-locked" for locked pages @titanium: Could you please test the new version (0.2.0.) with your template delegate approach. I don't use it, so I can't test it quickly. But should work

Will make the path configurable. I have an idea, will implement it asap. How does this sound: Additional CSS classes for unpublished, hidden, locked. And additionally a setting if unpublished blocks should be rendered collapsed or if all blocks always should be open.

So this seems to be the safest way, thx Soma!

You have to define the title field globally as not required (field settings). Otherwise the page doesn't get published. What PageTable (and so also the extended version) does, is to display the autoformat title instead of the title field. The field itself remains required as long as you don't define it otherwise. Would you also can try to do (haven't tried it myself yet): Define the field as not global, so you don't need to add it to your PageTable templates.

didn't know that. Updated the version number. Thx!

I think we need an option "don't ever display children here" as a template setting. At least for editors. Even I am a bit confused when I accidentally open a folder in the tree where all this data crap is in

No problem. Just define an autoformat:

Try include("./inc/".$layout.".inc"); And your includes should return $layoutview; For example: foreach($products as $)} $layoutview. = "<div>{$p->title}</div>"; } As I said, totally untestet. If the button does nothing please provide console output.

No need for a form. <div class='myViews'> <a class='button switchLayout' href='#' data-view='list'>List view</a> <a class='button switchLayout' href='#' data-view='grid'>Grid view</a> </div> jQuery: $('myViews').on('click','.switchLayout',function(e){ e.preventDefault(); var whichView = $(this).attr('data-view'); $.get( document.URL, { layout: whichView }).done(function( data ) { $( ".myView" ).html( $(data).filter('.myView').html()); }); }) in your template: ... $layout = $sanitizer->text($input->layout); // is there a get variable from ajax? if($layout){ $session->layout = $layout; } else // or something in session? { if($session->layout){ $layout = $session->layout; } else { // standard view $layout = "grid"; } } include("./inc/{$layout}.inc"); // returns $layoutView ... html goes here ... <div class="myView"> <?= $layoutview ?> </div> ..... So basically: Fetch the click, identify the button, load the current page via Ajax and with a GET variable which tells the template which view to render. The response is filtered, so only the myView part is the replacement for the current .myView. Written in the browser, totally untested.

Nope, every visitor gets a session. Also guests. No need to log in.

I would store the selection in a $session variable and switch content with ajax. Schema: first view: - no session present - render standard view (grid) Click on list view button: - get list part per ajax - replace content with that - store selection in $session Next page: - selection is present in $session - render list view until $session ends or grid is selected again. Depending on layout you also could render the same html and change the view per switching a html class (body or so) and remember that class in $session for next render.

Perfect. Thank you Pete! /merged

Wasn't there from the beginning. But as owzim posted this: https://processwire.com/talk/topic/4189-flexibility-in-page-design/page-4#entry63924 I knew, this is the key to my always wanted flexible layout parts exactly. Of course they would be. But as I said: If there would be a solution for the frontend, it could easily be applied to this module. I think developing a solution only for this module would be out of scope. Will try to include Apeisa's Fredi. If that works without hazzle, any inline solution should work.