dotnetic

You can use a hook to redirect after "Save & Exit": // the hook in a location like _init.php or in a module's init function $this->addHookBefore('ProcessPageEdit::processSaveRedirect', $this, 'redirectAfterSave'); /** * redirects to the main ListerPro "Raumdatenblätter" after saving a page with template raum * @param HookEvent $event * @throws WireException * @throws WirePermissionException */ public function redirectAfterSave(HookEvent $event) { $url = $event->arguments(0); $page = $event->object->getPage(); if ($page->template == "raum" && !$page->isTrash()) { if ($url == "../") { $goto = wire("pages")->get('/raumdatenblatt/raumdatenblaetter/')->url; $event->arguments = array($goto); } } }

I think Bernhard's ideas are very good and intuitive. I would also think that a ->has method would return a boolean.

Same here ?

Awesome!!!

There was a problem with the modules directory. Now you can install the module from within ProcessWire. I am looking forward to your feedback.

Yes it works now for me also. Thanks Pete

@Pete It doesnt work for me?. Changed my name here in the forums to "dotnetic". Go to https://directory.processwire.com/login/ and entered my name "dotnetic" and my password (even tried with my old long name "Jens Martsch - dotnetic" before). Clicked submit Being redirected to "https://profile/" Even tried different browsers, clearing cookies and using private mode in Edge

@gebeer The non CSS version is included in the dist directory. You should ask such specific questions in the github issues: https://github.com/KIProtect/klaro/issues Besides of that, your command looks good. They expect the node environment variable SEPARATE_CSS to generate the script.

The newest version of Klaro gives you the option if the CSS is included or you provide your own CSS. This is based on my PR.

@Pete Anything new about this?

It works fine here with PW 3.0.148 (almost a fresh installation). No errors.

@elabx Don't give up. It also took me a long time to work on ModulesManager 2 because of client work and other stuff. Then I have taken some time just for developing the module and saying "not today" to clients, because I need to finish this important thing that I am developing. I wanted to have a base so others can give feedback and submit PR's to help me with the module. But that's only an option if you plan to release it as Open Source. I hope you find the time to work on this again.

@elabx and @joshuag, any news about the progress or your plans? I would love to see that great module.

module is also now in the modules directory at https://modules.processwire.com/modules/modules-manager2/ Still pending

added new videos to first post

version 2.0.101 released * sanitize all class names for better security * optimize delete function to catch and display errors * unify methods a little bit more (same vars, etc) * remove some debug messages

OMG. My IDE prevented adding the dist files to the repo, so you had to generate them yourself. This is fixed now. Enjoy.

I just released the beta version on github. Updated my first post with the download URL. A new video is coming soon, as many features have changed. For example panels are only being used for a module's settings. All other actions are executed via AJAX and show a notification on success. Happy testing, and have fun with it.

I think my answer solves the problem, that the topic poster wanted to solve. Sometimes you have to think outside the box, and I think he just wanted to know how to not show pages that have a publish date in the future. What first comes into mind is: Leave the page unpublished until the date is actual. That you can tackle this problem differently may not be obvious. But you are right @teppo that there might be other use cases, for example if the page url should not be reachable at all, then the published or unpublished status would be the right thing to do.

Hey Bernhard, labels above or in front of the fields would be a great UX enhancement and make it obvious what field is what.

You could also do this with a simple page selector, which would be the simplest solution: So all your pages have the status Published, but will not be shown, because the event_start field is lower than the today date. $events = $pages->find("template=event, sort=event_start, event_start>=today"); The hook from @elabx is really overkill and modifies the page, which is not needed.

Install from URL is implemented and almost working. Sadly the module can not be installed after the download, because I can't get the name of the module from the zip file. Maybe I can find a way, but later. Preview

I worked hard on the module the last days, and rewrote much of the core logic and added some more features. I wanted to record a screencast yesterday, but my recording software ignored my mic. So I show you some annotated screenshots instead. Since then, many things changed again. Right now I am working on downloading and installing a module via a URL, and also making a transition to modal dialogs instead of panels, if applicable. I moved the whole button logic from the PHP script to a vue component. So I am flexible how to display the buttons, and I can reuse them in the cards and in the table layout: I added a reduced card layout, which moves the description of a module into the "more information" accordion: Updated TODOs with much more features to come. I will work on the module in the next 2 days and hope to make so much progress, that I can finally release the first version on github.

A page autocomplete field would be even more userfriendly. As the selected value you have to get the ID, but the title and ID could be displayed in the input/select. Nice work anyways ?

Did the same some time ago, as PW 3 was released. Replaced the wire folder, and that was it.