• Content count

  • Joined

  • Last visited

  • Days Won


ukyo last won the day on February 28

ukyo had the most liked content!

Community Reputation

213 Excellent

About ukyo

  • Rank
    Sr. Member
  • Birthday 06/08/1983

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests

Recent Profile Visitors

2,951 profile views
  1. Check this doc :
  2. Thanks for feedbacks !
  3. PHPMailer updated to v6, Module version updated to v1.0
  4. I updated WireMailPHPMailer module to PHPMailer v6. I will update WireMailPHPMailer support post. I have request for deletion of this topic and WirePHPMailer from module directory.
  5. I tested them long time ago, before i wrote my first Mail module and i think there is problem getting DKIM.
  6. I don't have any reason for not extending base WireMail class. This is why i updated module and now module extending bas WireMail class. Now you have 2 usage types: 1. Use directly PHPMailer class 2. Use extended send method For InputfieldHelper requirement, its easy to create configurable modules with this module and usable module for many cases, i won't remove requirement of this module. Like i mentioned, i am author of WireMailPHPMailer, i am not caring about module usage statics, if someone need PHPMailer module, they can use it. - I tested swift mailer module (smtp) - I tested base WireMail class (smtp) - I tested mailgun (curl) I am not prof. of mail sending but when i make simple mail send tests with same settings (mailgun not included), test result not ok for me (problem with DKIM). My test result with PHPMailer 10/10, this is why i am using PHPMailer library with my modules.
  7. I am using it for different cases. For modules (everything from a config file) : I am not defining default values as you see here : Getting module configs : Settings default values : Merging module values with defaults, building inputfields : - Its easy to build configurable module for me, no need to set all things on different places. For creating form you can see simple example usage on I am using it for creating dynamic fields for page templates on runtime by hooking ProcessPageEdit::buildForm. In screenshots Settings and General tabs added dynamically and fields inside these tabs added by a config file. Use case change up to you.
  8. InputfieldHelper for ProcessWire v3 Module Directory - Github repo This module extends base `ModuleConfig` class add some features to this class. This module creates Inputfields from array configs. I used this module for create module configuration panel for WirePHPMailer module. You can see configs here. Also you can use this module for create forms from array.You can check github repo for usage.
  9. PHPMailer for ProcessWire v3. Module Directory - Github repo I am author of WireMailPHPMailer. Old module using PHPMailer v5 and its extend WireMail base class. No more update will come for old version, but its still working :). This module using PHPMailer v6 and not extending WireMail base class. This module integrating the PHPMailer mailing library into ProcessWire v3. Usage almost same with original PHPMailer library (no need to include PHPMailer files). Here is a simple example usage : Using directly PHPMailer library $mail = wire("modules")->get("WirePHPMailer"); $mail = $mail->mailer(); $mail->addAddress("", "Someone"); $mail->isHTML(true); $mail->Subject = "WirePHPMailer"; $html = "<h1>WirePHPMailer</h1>"; $text = "WirePHPMailer"; $mail->Body = $html; $mail->AltBody = $text; $mail->send(); Using module like classic WireMail $mail = wire("modules")->get("WirePHPMailer"); $mail->from("") ->fromName("A From Name") ->to('') ->subject('A Message Subject') ->body('A Message Body') ->bodyHtml("<h1>A HTML Message Body") ->send(); Note : This module requires InputfieldHelper, PHP>=5.6.0, ProcessWire>=3.0.0 module.
  10. I opened an issue on github and have a question. Did you try this module with multi language support ? If page have multi language support what's happening on cache naming side ? When i work languages with cache, adding user language id as suffix to cache name.
  11. Try to use: $session->get('number'); or wire('session')->get('number'); // You can make a test function setMySession($key = '', $value = '') { wire('session')->set($key, $value); } setMySession('foo', 'bar'); echo $session->get('foo'); Here is doc page about sessions:
  12. Info : Before pull AdminThemeUikit module to dev branch, check this issue fixed. I see this issue after update my forked AdminThemeUikit module uikit files and opened an issue on uikit repo.
  13. @tpr I don't want to use a TemplateEngine. My module meet my needs and i am ok. Thanks for your advice !
  14. I checked :, Not allowing function calls, whats happening inside loop ? If i want to call item based tags. Its not meet my needs {pages(template=template-name):title} or {label(title)} or {description(title)} or {notes(title)}
  15. I missed : I will check it. @adrian For directly working on templates you are right. I am using same method with you. I wrote this functional group for own my needs and want to share it with community. I am working on a module (Component system for uikit-2 and uikit-3). At this component system, you can change lots of things by configs. Let me explain you little, I hope you can understand me :). Each component have index.php for component configs and template.php file for view. Also you can extend, overwrite or add new component for site specific. I will use grid-list component as example. Here is index.php for configs. And here is template.php file for display. As you see above selected area, i am using processString() function for custom title and subtitle configs. Component call on template : <?= co::component($finder['items'], 'grid-list', [ 'subtitle' => '{page:length} {notes(length)} // {page:cabins} {notes(cabins)} // {page:render:destinations}' ]); ?> Result : Same component call on another template : <?= co::component($finder['items'], 'grid-list') ?> Result : For my component module, I can have 1 component and i can use it on all my sites with different settings and different display options. <?= // 1 more example with "alert" component co::c('alert', [ 'title' => 'You are in {page('title')}.', 'content' => 'You need to go <a href="{pages(1200):url}">{pages(1200):title}</a> for view our products', 'alert_style' => 'danger', 'alert_size' => true, 'alert_close' => true, 'text_align' => 'center' ]); ?> If you want you can call something inside body field.