benbyf

101aandd.com New site mostly designed by the client and implemented in Processwire. Mostly concentrating on small subtle animations.

Amazing, thank you! Zuse wasn't on the list and is now

i believe you'll need to implement the module in your templates as per the README https://github.com/apeisa/PaymentStripe/

ended up with this, but be nice to get a best practice of tutorial on this as still don't really understand. public function ___uninstall() { // for each installed page delete on uninstall $pages = array('my_test_page'); foreach ($pages as $key => $value) { $page = $this->pages->get("name=$value, include=all"); $this->wire('log')->save('mm_log', $page->id); if($page->id){ // delete page and any children $page->delete(true); $page->trash(); } } // delete field groups used on system templates $f = $this->fields->get('my_repeater'); $userTemplate = $this->templates->get("user"); if($userTemplate->id) { // $userTemplate = $this->templates->get("user"); // $fg = $userTemplate->fieldgroup->remove($f); // $fg->save(); $userTemplate->fields->remove($f); $userTemplate->fields->save(); $this->wire('log')->save('mm_log', 'delete user field'); } // delete messages template $templates = array('my_template'); foreach ($templates as $key => $value) { $t = $this->templates->get($value); if($t->id){ $t->flags = Template::flagSystemOverride; $t->flags = 0; $this->templates->delete($t); } $fieldgroup = $this->fieldgroups->get($value); if($fieldgroup){ $this->fieldgroups->delete($fieldgroup); } } // for each installed field delete on uninstall $fields = array('my_field'); foreach ($fields as $value) { $f = $this->fields->get($value); if($f->id){ // if field exists, then delete $this->fields->delete($f); } } $this->modules->uninstall($moduleName); }

thanks, fingers crossed that works. was using fieldgroups before no template->fields

Never really got my head around field groups and it shows, In my module uninstall I think I figured out how to delete a page, then a template and it's fieldgroup so that nothing gets upset. But for fields that belong to templates that need to stoick around I'm still abit stuck to how you would remove the field and when I try I still get: Unable to delete field '[field name]' because it is in use by these fieldgroups: 'user' is there a tutorial or best method for removing added fields, pages and templates?

Hi @JeevanisM Thank you so much for your kind words! The art for Grace has been done but the amazing Joe https://www.tandc.games/news/team-spotlight-joe-blakeston/. Let me know if you have any other ideas for important people from CS history who should be included! And sign up to the news letter or socials if you wanna hear its progress etc. Cheers,

https://www.tandc.games/ New website for my games design company. We're currently working on Grace Hopper: Bug Rescue about computer science history, check it out and let me know if you have any suggestions for historic characters or topics/hardware. Built with PW, and is heavy built upon my other website https://www.ethicalby.design/ basically taking it as a base and building on it.

Thanks Ryan. This is something I had to deal with for a client a couple of years ago adding custom save buttons that then used lazyCron to publish the page later–this however is a much neater solution so i'll refactor at some point.

I have the messaging module ready to go if anyone is interested in Beta testing it (then please message me) and ill get the shop up and running to sell it from (unless the PW market place is willing to have it of course???).

Hi, just wondered if anyone had tackled a module to add a masonry effect to the image field in PW admin? I've got a front end effect by calculating all the hieghts of each new image and placing them in a column with the least current overal height (instead of doing the same in javascript), but be nice to see the same representation in the admin too.

Hi HI David, in PW any function in a module that has ___ at the start, like ___handleApiRequest() in the AppAPI module you can use as a hook in your own code. See https://processwire.com/docs/modules/hooks/

$order = wire('pages')->get($data->id); echo $order // {} somehow I'm getting this when expecting string "order". PW 3.0.148

Hi @Sebi I added the log to app-api (will create a PR somepoint soon), I wondered if you wanted a log message on each request and maybe a setting in the modules settings to turn on or off, or maybe something more granular? My use case is going to require lots of log messages in the api files but having a generic log message on each request I though might be nice. Also wondered if it was worth making a second log for failed (exception) based log messages? so successful requests get logged to one and exceptions to the other..... any thoughts would be cool

Thanks both @Sebi and @thomasaull I appreciate your time. Will look into the log bug as thats paramount to us using the module so would be great to clear up. The non-apikey endpoints is more of a nice to have really as you can set up informational endpoints that act like website frontends but without the visual code obviously. In terms of users, applications and version, they seem loosely connected. There seems little reason to fill out the apikey version when creating a new apikey if it doesnt actually relate to anything. But maybe i just havent seen how it does or could relate. Also the users are too loosely associated with the applications (slight tangent), but it would be nice to leverage the user and roles system byt associating a user/s with either key or applications, and then auth them against them on route. e.g. [..., [route_options_role_required = "delete-pages, update-pages, create uses" ]] as the folowing api might enable these things and you wanna be pretty damn sure that user is allowed to do it 🙂