Leaderboard

I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL. Some ideas to extend this: make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people ? Github Repo: https://github.com/thomasaull/CiTrigger

@Zeka if you find time it would be great if you could write a little showcase/tutorial of this panel in the tracy thread ? Maybe Adrian could also use it for the docs... Everything is there already: https://adrianbj.github.io/TracyDebugger/#/debug-bar?id=request-logger ? Thx for the great work @Adrian!

When go to your template (Blank-Page), you should see a yellow bar like this: So, did you follow the hints from the two other variants of this question? Reading the docs, creating a template file named "Blank-Page.php" in your site/templates folder and placed your code there?

Yes, I can't move it to ready as I need to change the output depending on an incoming request. Basically, I have to return {'code': 0} if I have a valid incoming request and on ready stage, I already have rendered 404 page. Maybe there is a better place for a hook? I have changed ProcessPageView::execute to ProcessPageView::ready and now everything works. Thank for the help, TracyDebugger and Logger panel!

Hello, We've been using Mailgun for several years now on ProcessWire developments, using a cURL implementation within a custom site development module/template site. I'm currently rewriting that and trying to use much more of the PW API as there's been a lot of handy things added in the past while. Part of that process is to use WireMailMailgun, so I installed @Macrura's fork and then began to see what could be improved/finished off from the todos. What I've ended up doing is a partial rewrite of the module: to use more ProcessWire conventions and the coding style guide implemented a few extra features removed what I though was unnecessary code. It requires 3.0.123 and above, as it uses the htmlToText() method from WireMail, which in turn uses WireTextTools. The module is here: https://github.com/chriswthomson/WireMailMailgun Please let me know your thoughts! Cheers, Chris

No i think these are very good examples of kind of application that you are looking for and Bernhard let us take a closer look into his building process and decissions...so many things to learn ? Welcome to Processwire! @jmartsch just like you - this forum its kind a like a save harbour for straightforward and friendly people getting their things done and help each other...

Input fields can be checked for correct email syntax. Would be nice if it additionally could check the email against a local database of disposable email address domains, e.g. https://github.com/FGRibreau/mailchecker/blob/master/list.json The disposable email domain database should be selfhosted to avoid any privacy issue (if a legit domain would be transmit to 3rd party). Ideally, Processwire would auto-pull database updates in intervals. Hot or not?

Hi @SamC, really nice project! I've just stumbled over your admin theme tutorial: https://www.pwtuts.com/processwire-tutorials/making-a-custom-admin-theme-using-uikit-3-and-the-included-build-tools/ This is not true any more ? Maybe you want to update this tutorial?

TemplateEngineMustache 2.0.0 are now supporting TemplateEngineFactory 2.0.0

OK guys, thanks for this. I have just realised I have been a bit lazy in not doing the tutorials first, more just finding something when I hit a road block. I've just had a look through the tutorial list. I've never seen a tutorial so organised and also right from the beginning. I'm going to learn some stuff so I can give you guys something harder to help me with. Thanks again Legends. JA.

Here is a good one which I recommend for @Steve_Stifler to get started: https://www.pwtuts.com/processwire-tutorials/alternate-template-strategy-using-a-single-output-file/ I linked to this one this time because it also explains a simple strategy to get organized right from the beginning. The only thing I would do differently is that using relative paths in PHP can be cumbersome for beginners, so for example instead of this: include("./views/{$page->template->name}" . ".php"); I would use: include $config->paths->templates . "/views/{$page->template->name}" . ".php";

Hi @adrian, A lot of the code is much the same, but tidied up with the the coding style guide implemented, so I'm not surprised the diff doesn't reveal much! The readme is pretty thorough and covers a lot, but here's the gist: addData() - add X-Mailgun-Variables - https://documentation.mailgun.com/en/latest/user_manual.html#attaching-data-to-messages - to be honest don't know what use cases there are for it but it's in the API and was easy to implement addTags() - add multiple tags as an array getHttpCode() - to get the response code from either send() or validateEmail() * Most methods now chainable (see the Advanced Example in the readme) Tracking only used if bodyHTML() is set (As this only works in HTML email) cc() and bcc() only used when batchMode is off - this seems to me to be the correct implementation WireMail::htmlToText() used for generating the text version if only HTML passed (as in WireMail now) The ASCII conversion for tags now uses $this->sanitizer->nameFilter($tag, [" "], "", false, 128); WireMail::replyTo() implemented - doesn't seem to have been before removed addAttachment(), now uses WireMail::attachment() - which adds the ability to set the filename Unixtime is now passed to setDeliveryTime() A bunch of other small tweaks like using $sanitizer->email() in validateEmail() * I'd wanted to use WireHttp for the requests, but it doesn't allow custom cURL options. I have done a pull request for this, but I don't think I'll be changing the module's cURL request implementation now anyway. Cheers, Chris

@bernhard nice! I'll update the tutorial (done now) and point to this module. I haven't had much time at ll to work on that site, been so busy trying to learn enough skills to call myself a dev one day...

Thanks mate ?

@flydev I adjusted the Regex Pattern for the endpoint url to allow numbers too: https://github.com/thomasaull/RestApi/commit/f2e851faf4b89449bca496d6bea20ee85dc0f6ee Please update the module to 0.0.6 for this to become active

It would possible of course but I'm not sure that would be too beneficial. It would further increase the DOM weight and make more clutter, even when it could be disabled. Furthermore, many features couldn't have such indicators (eg. hotkeys) and it would be hard to create a "trademark" that would fit for most feature. But PR's are welcomed, as always ?

TemplateEngineSmarty is now compatible with TemplateEngineFactory 2.x: https://github.com/blue-tomato/TemplateEngineSmarty

I had a stab at this over the weekend (during my free time, ahem). I'm finalising it now. Hope to post alpha(-ish) version tonight. I'll start a separate thread.

Boy, I love our community. So helpful and friendly. Never experienced anything like this. Spread the love.

Hey @Wanze What a great module! Thank you very much - I love the flexibility. One update I would like is the ability to use the meta image field as an actual image field, it would be much more understandable for clients rather than trying to find the image URL.

Yes. You can easily check that with tracy debugger: // ready.php $wire->addHook("Page::foo", function(Hookevent $event) { bd("foo was fired!"); }); You will not see any dumps of "foo was fired!" unless you explicitly call it somewhere else, eg $page->foo() in one of your templates.

BTW, if you are hitting limits with that service, maybe try https://ip.nf/ or https://api.ip.sb/geoip - the former guys are very supportive of PW.

Version Update 1.0.3 The current version 1.0.3 has some minor improvements. Items are inserted at the last position on the target page and set to the status unpublished. Furthermore, the clipboard is synchronized live, so you can jump between browser tabs without reloading the target page, for direct pasting. And the module runs only in the backend in the autoload. > Grap a copy: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDublicate

Just wanted to share the simplest language switcher possible if you only have two languages: <a href="<?= $page->localUrl($languages->findOther()->first()) ?>">DE/EN</a> ??

Just had a small world experience. I have been emailing with Ueli at https://www.whatwedo.ch/ who are the folks who operate the https://ip.nf/ IP to country API service. He just mentioned that they are partners with https://novu.ch/ (built with PW) and that they use ProcessWire a lot. So anyway, he is keen to support this module and to make sure their service will be able to keep up with any requests made by it to their service ?

Glad you got it sorted. Just an FYI:

If you go the 'modify ckeditor' route, as you say, you need to create the list (i.e. select the text, then click the list button in ckeditor), then select the list again, then use the 'Styles' dropdown to apply the classes. I find this a bit convoluted. If you are using less to compile uikit, you could always try extend. I use this in sass a lot, the syntax is different with less, but something like this: .wrapper-for-ckeditor-field { ol { &:extend(.ol-pretty); &:extend(.uk-list-large); } } i.e. just style out any ol within .wrapper-for-ckeditor-field (which would be in your template). No need for applying classes via ckeditor. This wont work for you if you need: a) Different styled lists within the outer class b) You're not compiling less Just an idea. I don't like messing around with ckeditor, find it quite infuriating, but sometimes you have to.

The notices system actually doesn't have anything to do with jQuery UI other than that the default admin theme makes use of jQuery UI class names when generating the markup for notices. But for your own front-end, you can make use of the $notices API variable to output them however you want. It can be as simple as this: echo "<ul>"; foreach($notices as $notice) { $class = $notice->className(); $text = $sanitizer->entities($notice->text); echo "<li class='$class'>$text</li>"; } echo "</ul>"; Then you would want to style the two type of notices in your CSS: .NoticeMessage { color: green; } .NoticeError { color: red; }