elabx

This is very likely the reason! I've gone through this types of errors a lot! Images with AdobeRGB or sth alike.

Same story, different country haha. There is not a ListerPro "skin" . So assuming from the type of client yo you are dealing with, you'd be better off satisfying their UI/UX needs, or at least what they are used to. Because you're gonna end up fighting PW's markup and overriding it's styling. and end up with a bloated thing rather than the elegant solution ListerPro is meant to be. Customising the admin is easier now with the new UIKit based theme. But truly, here is where PW shines its brightest, leveraging the selector API makes building a lister pretty straightforward, I mean, the screen you post is basically a graphic description of what the selector API can do. So from what you mention about the project you are involved in, just build the thing and make people happy If you manage to reuse that frontend in the screenshot, it's basically just getting the data from the front to the back and let PW do the rest.

@Twitch Could it work to have the whole PW admin area as guest area (if it's in a private network, no problem I guess?) and just use the ListerPro out of the box. You would have to build the other admin pages (if in need of something customizable) as Process modules. The picture you show looks different but basically those are the type of options you are given when using ListerPro filters. I guess you could do something like this on the frontend but with the Process module involving ListerPro. (ProcessListerPro?). Though you would have to include js/css for the ListerPro to work (and it would LOOK like a PW ListerPro). Also don't really know how ListerPro internally checks permissions or any other gimmick involving routes in the pw admin.

Came to ask pretty please for this, I sometimes work in the harsh lands of Only FTP Access and Detrimental Server Features and oh boy, deleting the cache gets rough. I really miss just writing ClearCacheAdmin class on the module install :')

Oh!!! Thanks a lot for the heads up @szabesz !!

Working on a similar project, a kind of site parameterised site cloner. All in one PW install for maintenance commodity. Would love to see the outcome of this discussion

Something I couldn't find or notice in your code Adrian, is there a way to filter the child pages you want as CSV by a selector? I was looking to use the exportCsv method to export pages stored under a PageTable.

Man I love the last part of "small tips". Those kind of things take me to the haute couture of module making :D.

I'd certainly enjoy the series you describe!

Could this work? Seems like a good starting point: http://modules.processwire.com/modules/amazon-s3-cloudfront/

Try loggin in as superadmin while developing, though I am almost 100% sure that FileCompiler always checks for new versions of files. Are you getting anything at the FileCompiler log? Setup > Logs > FileCompiler

I think you would need to work with the "custom render" solution as described here.

My "uk-margin-almostlikeyouwantit" filled divs are looking at your comment and laughing at me haha.

Using it for website design, overriding styles all the time. I kind of have liked that you have must buzzword components right at hand, ready to integrate, so when a clients asks: oohhh those nice backgrounds that move around when you scroll, DONE, ohhhh I want all this animated like a disney movie, DONE and so on... I have found some things that I need to hack around but in a much less percentage than Bootstrap, at least in my experience. Though a fellow I am working with now has really spoiled me into noticing that writing your own CSS isn't that hard and just makes less work than reverse engineering a framework.

Wo, thanks a lot, just needed this! Gracias!

Is there a reason ProcessWire would be stripping a <form> html element when embedding code through this module?

Thanks for this very useful fork! It would be rad if it integrated @flydev 's fork too for hashtag search!

Just got my copy I hope this is safe! I'll trust random internet software with my servers haha

Could this be a serverpilot replacement??

Guess I just jumped to fast on the forum, thanks!

I want to render a repeater matrix repeater type with the following code: foreach($page->content_repeater_matrix as $content){ if($content->type == "hero"){ $content->render(); break; } } The field has its own field template asigned in fields/content_repeater_matrix/hero.php. Why shouldn't this work? It would seem to me to be "the processwire way" I got this one working in fields/content_repeater_matrix.php: <?php foreach($value as $item) { echo $item->render(); } Am I trying to call render in the wrong context?

Dude it was so much vanilla ProcessWire that it was like plain cheating, heads up to @joshuag who had the actual idea!

I did a "hotel review" app that sends emails to clients and catches responses nicely in a PageTable!! I also use PW fields to configure the survey page (add hotel logo, color styles, headlines). The users just have a list under root, each one representing a hotel, displaying the responses nicely inside brackets next to the title. New hotel for review? Just add a new page and configure! Happy clients with minimum effort and straightforward interface!

This looks really nice! I agree having the page as context is a smart move! Hadn't thought of the problems of having that represented at field level. I also REALLY like the idea of variations existing on its own as presets somewhere else. Something that I see solved nicely and horrible at the same time, is Shopify's very own variation editor is batch edition of prices and variation names. Eg. Select a variation by one of its properties and change the price in a batch table mode. This was done pretty nicely in an Excel like fashion, or multi checkbox select and command in menu. What I did suffered was making a soccer uniform shop with 10+ sizes and sometimes 20+ variations in color. An error in creating the names would imply to REDO all the variations, or go through a menu to edit EACH variations name. Always almost easier to recreate the whole thing. It seemed as if after creating the list of variations per property in a nice interface, they all lost the relationship amongst them. So if you had written Brgundy / Dark Blue, get ready to edit +50 fields in modals or just delete the whole thing. There goes your day! And the variations problem reveals a flaw in Shopify's service, no more than 100 product variations. Why I might guess won't be a problem for PW. I think variations images would also be quite the deal! Nothing more to add, just personal experiences of suffering from product variations. Hope to see this released!

Digging this from the grave, is this now easier to accomplish? Sometimes for mocking data with the few resources one might have it's useful to just repeat the same thing. Maybe add an icon to the repeater item toolbar through a hook. Came back to say I'm blind and crazy, I was already using latest dev -.- Time to make coffe