Jump to content
ryan

Hanna Code

Recommended Posts

Okay, this getting very odd.

I have changed it so that I am getting the text from a field on the actual page, rather than from another page.

And it has exactly the same problem.

????????

Share this post


Link to post
Share on other sites

I'm not sure. Can you hand a copy? 

Cache?

Share this post


Link to post
Share on other sites

OKAY!!!
 

Ummmmm

If I change it to get the page name, rather than the page title, it works!!!

WHAT??

(Cache is very definitely off and this is just on a local box)

Share this post


Link to post
Share on other sites

APC php cache?

Is there anything on the title field? Textformatter?

It's hard without sitting in front.

Share this post


Link to post
Share on other sites

BINGO!

Soma, well done. It was the HTML entity encoder textformatter on the title field (I have no memory of adding that, but then this project started a while ago)

Thanks mate, again.... :)

Now the question is why would that mess things up?

Share this post


Link to post
Share on other sites

Well the cool kids use remote control, Airplane bahh...

Glad you found it. I have no idea why.  ???

  • Like 1

Share this post


Link to post
Share on other sites

Neither do I. One for Ryan when he is wandering by at some point. 

Interesting to see if you can replicate it though.

Night!

Share this post


Link to post
Share on other sites

Correction - the problem seems to have been with the title field also having the hanna code textformatter added. Er, I think. 

I need to go through this tomorrow!

Share this post


Link to post
Share on other sites

Hi,

I've got a problem with trying to edit a hanna code. I can see the list of codes I've setup and I can create a new one but I'm not able to edit it after I've created it. I had this problem with the final 2.4 release but I thought an update to the most recent dev build (2.4.7) might fix it but, no. There's no browser errors at all. Reinstalled it, still no.

My server setup is: PHP 5.4.25 & MySQL 5.1.73-cll

Any thoughts?

Share this post


Link to post
Share on other sites

Some little new hannas from my playground with a question:

//BDay
//Use this with [[bday?d=1950-12-31]]
//You can add this to any place, even in the title of a link or alt text of an image. Also future day possible.

!HannaCode:BDay:eyJuYW1lIjoiQkRheSIsInR5cGUiOiIyIiwiY29kZSI6IlwvKmhjX2F0dHJcbmQ9XCIyMDAwLTEtMVwiXG5oY19hdHRyKlwvXG48P3BocFxyXG5cclxuXC9cL1VzZSB0aGlzIHdpdGggW1tiZGF5P2Q9MTk1MC0xMi0zMV1dXHJcblwvXC9Zb3UgY2FuIGFkZCB0aGlzIHRvIGFueSBwbGFjZSwgZXZlbiBpbiB0aGUgdGl0bGUgb2YgYSBsaW5rIG9yIGFsdCB0ZXh0IG9mIGFuIGltYWdlLiBBbHNvIGZ1dHVyZSBkYXkgcG9zc2libGUuXHJcblxyXG4kb3V0cHV0X3ZhbHVlID1cIlwiO1xyXG4kZD10cmltKCRkKTtcclxuJGRhdGVub3c9ZGF0ZShcIlktbS1kXCIpO1xyXG4kZGlmZj1zdHJ0b3RpbWUoJGRhdGVub3cpLXN0cnRvdGltZSgkZCk7XHJcbmlmKCRkaWZmIDwwKSRkaWZmPSRkaWZmICogLTE7IFwvXC9ubyBuZWdhdGl2ZSB2YWx1ZXNcclxuJGRheXM9Zmxvb3IoKCRkaWZmKVwvODY0MDApO1xyXG4keWVhcnM9cm91bmQoKCRkaWZmIFwvMzE1MzYwMDApLCAyKTtcclxuXHJcblwvXC9ERUJVR1xyXG5cL1wvJG91dHB1dF92YWx1ZT1cIiRkYXRlbm93ICRkIEFnZSBpcyAkeWVhcnMgeWVhcnMuIFRoYXQncyAkZGF5cyBkYXlzXCI7XHJcbiRvdXRwdXRfdmFsdWU9XCJBZ2UgaXMgJHllYXJzIHllYXJzLiBUaGF0J3MgJGRheXMgZGF5c1wiO1xyXG5cclxuZWNobyAkb3V0cHV0X3ZhbHVlOyJ9/!HannaCode

and

//countdown
//d_day=(day) d_month=(mont) d_year=(year) txt1=(text_before) txt2=(text_after)
//Use [[countdown?d_day=25&d_month=12&d_year=2009&txt1=Only&txt2=days until it is Christmas]]

!HannaCode:Countdown:eyJuYW1lIjoiQ291bnRkb3duIiwidHlwZSI6IjIiLCJjb2RlIjoiXC8qaGNfYXR0clxuZF9kYXk9XCIyNVwiXG5kX21vbnRoPVwiMTJcIlxuZF95ZWFyPVwiMjAxNFwiXG50eHQxPVwiT25seVwiXG50eHQyPVwiZGF5cyB1bnRpbCBpdCBpcyBDaHJpc3RtYXNcIlxuaGNfYXR0cipcL1xuPD9waHBcclxuXHJcblwvXC9kX2RheT0oZGF5KSBkX21vbnRoPShtb250KSBkX3llYXI9KHllYXIpIHR4dDE9KHRleHRfYmVmb3JlKSB0eHQyPSh0ZXh0X2FmdGVyKVxyXG5cL1wvVXNlIFtbY291bnRkb3duP2RfZGF5PTI1JmRfbW9udGg9MTImZF95ZWFyPTIwMDkmdHh0MT1Pbmx5JnR4dDI9ZGF5cyB1bnRpbCBpdCBpcyBDaHJpc3RtYXNdXVxyXG5cclxuJHRvZGF5ID0gdGltZSgpO1xyXG4kZGF5WCA9IG1rdGltZShkYXRlKCdHJyksIGRhdGUoJ2knKSwgMCwgJGRfbW9udGgsJGRfZGF5LCAkZF95ZWFyKTtcclxuZWNobyAkdHh0MS4nICcgLnJvdW5kKCgkZGF5WC0kdG9kYXkpXC8oMzYwMCoyNCksMCkuJyAnLiAkdHh0MjsifQ==/!HannaCode

so in my former cms (there was a similar addon called droplets) i could get the whole rendered page as a $var or the contentpart of it and could make a nice CreateToc droplet that search for Headingtags and build up the TOC:

preg_match_all( '#<h([1-6]).*>([^<].+)</h[1-6]>#i', $wb_page_data, $matches, PREG_PATTERN_ORDER );

the var $wb_page_data gets the actual pagecontent to analyse by the droplet (=HannaCode).

Is there a similar option or could i simply use the render() function on the parts of the page that i wanna get into the TOC?

Kind regards mr-fan

Share this post


Link to post
Share on other sites

I've double ask would it be nice to have a little hanna gallery with structured and sorted hanncode??

Could be a nic addition to the addons page? with some given parameters like name, desc, importcode, vars

Share this post


Link to post
Share on other sites

Just a note to all MODx'ers - I think this is a nice way to transfer some snippets/chunks to ProcessWire as well if people want to go down that route and have some they used to use in body text. Obviously it's not quite the same thing (potentially more powerful depending on your needs), but anything that helps make a transition easier is good in my book :)

Very useful, powerful module ryan!

Agree. I'm coming from that CMS and I really like the ability to not have to rely on includes so much.

Share this post


Link to post
Share on other sites

Hi guys

Thanks for looking at this!

A Hanna code question for you gents...

In WordPress, one of the things you can do inside the main text editor is that you can add a read more tag anywhere inside your blog posts. Usually you might insert it after say the end of the first paragraph.

And so if you set up WordPress such that it displays your blog posts as a list of excerpts or teasers, then should it come across a post that has a read more tag, it will display the contents of that post from the beginning as an excerpt right up to the point where you placed that read more tag. Finally WordPress turns that read more tag into a link such that if you click on it it takes you to the complete blog post.

So my question is gents, if we create a [[readmore]] hanna code, how do we go about replicating this WordPress functionality?

As my coding skills are not very good, I thought that there could be two approaches.

One would be to somehow break out of the body field once it reached our [[readmore]]. How to do this I do not know how. I tried getting my [[readmore]] to simply echo return; but it ignored that!

The other I guess would be to use our [[readmore]] as a "marker" of sorts and somehow extract the section between the beginning of the body field up until it sees our [[readmore]] marker. I'm thinking this might need an explode implode kind of approach but I have never ever done anything like that before and so I am really quite clueless on this one.

Or maybe there is a smarter way?

Any tips or suggestions or code chunks much appreciated!

Cheers guys!

Share this post


Link to post
Share on other sites

Hey Zahari,

In a bit of a rush, but PHP's strstr might be what you are looking for. Not sure that you really need a Hanna Code in this situation. Just parse the content of the field in your template.

$introtext = strstr($page->body, '[[readmore]]', true);

Then when you echo out the body on the full version, just:

echo str_replace("[[readmore]]", "", $page->body);

Hope that helps to get you started. I am sure there are lots of other ways to approach this. I usually go with automatic truncation because editors usually forget to add things like a [[readmore]] tag. 

  • Like 3

Share this post


Link to post
Share on other sites

Adrian!

That's such an awesome function!

Oh so elegant!

And here I was trying to bust my head with preg_split :wacko:

As always... thank you thank thank you!!

Share this post


Link to post
Share on other sites

Another little Hanna issue:

In CKEditor if you delete a space (like with backspace) and then press the space bar to put it back in, or anything similar, CKeditor inserts a

 

So, if on a hanna code you have something like this:

[[col class="medium-4 myclass"]]

When you first type it, it is fine, but if you edit it, the source becomes:

[[col class="medium-4 myclass"]]

And the code breaks.

Ryan, can you add a check in the hanna module so that it looks for   and replaces is with a blank " "?

Share this post


Link to post
Share on other sites

@Joss: unless you actually need non-breaking spaces somewhere (and assuming that you're running a new-ish version of PW), the "beautify markup toggles" section of CKEditor field are pretty neat. "Remove non-breaking spaces" has saved the day a lot of times for me. Just saying :)

Share this post


Link to post
Share on other sites

Arf'noon Teppo!

Yes, I know there is a way around it on CKEditor, but it struck me that having a catch-all on the Hanna Code is possibly not a bad idea. It's one of those things that could mess a client up if they don't know all the ins and outs.

Share this post


Link to post
Share on other sites

Ryan, next time you're are messing with the module, fancy putting in a drop down for font size on Ace? For us old blokes, you know......

  • Like 4

Share this post


Link to post
Share on other sites

Damn it is embarrassing that I felt the need to Like that suggestion of Joss'. I used to be fine on a 15" laptop running 1920x1200. Seems like 40 really is the beginning of the end when it comes to small things and low light :)

  • Like 2

Share this post


Link to post
Share on other sites

Hi, I just can't find my github login, so I'd like to report a minor bug here. (I did cost me some hours…)

In the description of the Hanna Code Name field is written, that hyphens are allowed in names:

post-426-0-43598900-1412005724_thumb.jpg

That's definitely not right. as you can read here:

https://processwire.com/talk/topic/7123-embedding-css-grid-markup-in-textareackeditor/

Hanna Code Module is not working with additional parameters if hyphens are in the Hanna Code Name.

This error was also reported on github in February here:

https://github.com/ryancramerdesign/ProcessHannaCode/issues/3

The module is great anyway. So thanks a lot in advance!  :rolleyes:

Share this post


Link to post
Share on other sites

Ryan,

I've got notified in the PW admin (2.5.3 master) that there was an update (0.1.9) available for Hanna Code. I checked GitHub and saw that you added support for hyphenated Hanna names, cool!

Unfortunately, updating via Setup->Upgrades did not go as planned. It timed out after 30 seconds and the mentions of TextformatterHannaCode and ProcessHannaCode had dissapeared from the modules list.

After that, a '.TextformatterHannaCode' directory was present in the site/modules and a 'ProcessHannaCode' directory with only partial files (the ace stuff)  in it. Clearing out these folder and installing from ClassName also did not seem to work anymore, as it also resulted in a timeout.

Grabbing the zip from GitHub, extracting it in site/modules and renaming it to 'ProcessHannaCode' and afterwards refreshing the modules section in PW admin seems to have restored everything, and i now have an up to date (0.1.9) Hanna Code Module, with all Hanna Codes i already had working correctly.

Maybe it was the initial time-out that got me screwed, but maybe there are some (re)naming issues when upgrading to the latest version of Hanna. Thought i'd mention it anyway.

  • Like 1

Share this post


Link to post
Share on other sites

next HannaCode to crosslink the topics

https://processwire.com/talk/topic/7930-screenshot-generator-url-to-img/#entry76654

!HannaCode:thumbnail:eyJuYW1lIjoidGh1bWJuYWlsIiwidHlwZSI6IjIiLCJjb2RlIjoiXC8qaGNfYXR0clxudz1cIjEyMFwiXG5oPVwiODBcIlxudXJsPVwicHJvY2Vzc3dpcmUuY29tXC9cIlxuaGNfYXR0cipcL1xuPD9waHBcclxuXHJcblwvXC9nZXQgc29tZSB0aHVtYm5haWxzIGZyb20gYSBzZXJ2aWNlIEFQSSBcclxuXC9cL2xpbmsgZXhhbXBsZTogaHR0cDpcL1wvYXBpLndlYnRodW1ibmFpbC5vcmdcLz93aWR0aD0xMjAmaGVpZ2h0PTgwJmZvcm1hdD1qcGcmdXJsPXByb2Nlc3N3aXJlLmNvbVwvXHJcblxyXG5lY2hvIFwiPGltZyBzcmM9J2h0dHA6XC9cL2FwaS53ZWJ0aHVtYm5haWwub3JnXC8/d2lkdGg9JHcmaGVpZ2h0PSRoJmZvcm1hdD1qcGcmdXJsPSR1cmwnPjxcL2ltZz5cIjsifQ==/!HannaCode

Some little thumbnailgenerator....;)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ukyo
      FieldtypeFontIconPicker
      v.0.1.6
      Fix FieldtypeFontIconPicker sanitizeValue() v.0.1.5
      Added uikit icon select support (required AdminThemeUikit), because uikit icons not working standalone. v.0.1.4 :
      Fix issue FontIconPicker inside repeater v.0.1.3 :
      FontAwesome updated to 4.7.0 v.0.1.2 :
      Little Corrections Some works about icon pickers inside repeater via ajax load v.0.1.1 :
      FontAwesome updated to 4.6.3 v.0.1.0 :
      Custom CSS file url support Added hook method ___beforeRender(), you can check hook example for usage Added multiple icons library use option Added Ionicons Library Now module using cdn for load icon fonts v.0.0.9 inside dev branch
      Added hook method ___beforeRender(), you can check hook example for usage Added multiple icons library use option Added Ionicons Library Now module using cdn for load icon fonts v.0.0.8
      FontAwesome 4.5 update, Improvements and Performance updates Important ! After update module check your input settings, because i changed input attribute names (This will only effect input options, like theme, category). Changed loading icon method from input:hidden to select>optgroup>option, added module js file for load and correct icon picker container many changes…. v.0.0.7
      FontAwesome updated to 4.4.0 v.0.0.6
      Missed... array compatibility for usage, from [$foo, $bar] to array($foo, $bar) v.0.0.5
      Fix for oldest pw versions (Assets file loding scripts moved to inputfieldfonticonpicker module) v.0.0.4
      Array compatibility for usage, from [$foo, $bar] to array($foo, $bar) v.0.0.3
      Small z-index problem solved v.0.0.2
      MarkupFontIconPicker added v.0.0.1
      Start Point FieldtypeFontIconPicker
      Supported Icon Libraries
      FontAwesome 4.7.0 Uikit 3.0.0 IonicIcons 2.0.1 Cahangelog
      NOTE: Module store data without prefix, you need to add "prefix" when you want to show your icon on front-end, because some of front-end frameworks using font-awesome with different "prefix".
      Example :
      if($my-icon-field) echo "<i class='my-prefix-{$my-icon-field}' />"; Hook Before Render Example This example using /site/templates/admin.php file for hook
      wire()->addHook('InputfieldFontIconPicker::beforeRender', function($event) { if(!$event->return) return; // Get Input Name (For specified input hook, if you want apply all InputfieldFontIconPicker remove inputName check) $inputName = ""; if(isset($event->object->attributes['name'])) $inputName = $event->object->attributes['name']; // Get Input Name (For specified input hook, if you want apply all InputfieldFontIconPicker remove inputName check) if($inputName == 'icon_picker') { /** * Load your custom icons function file * Your array need to be same format with Icons/FontAwesome.php or Icons/Ionicons.php * Also you can pass directly an array */ wireIncludeFile('MyCustomIconFile'); // Set icons as $icons variable $icons = MyCustomIconsArray(); // Set your options $return = array( 'attributes' => array( 'category' => '', 'theme' => 'fip-grey', 'empty-icon' => 1, 'empty-icon-value' => '', 'icons-per-page' => 20, 'has-search' => 1 ), 'icons' => $icons ); // Return the event $event->return = $return; } $event->return; }); MarkupFontIconPicker Usage
      // MarkupFontIconPicker::render(YourIconField=string, Options=array) echo MarkupFontIconPicker::render($page->YourIconField, [ 'prefix' => 'uk-icon-', // Icon class prefix, if you have different prefix, default is : "fa fa-" 'tag' => 'span', // Icon tag default is : "i" 'class' => 'fa-lg', // If you have extra cutom classes, for example : icons sizes, Array or Sting value 'style' => 'your custom styles if you have' // Array or String Value ]); Screenshots - InputfieldFontIconPicker input settings



      Screenshots - InputfieldFontIconPicker page edit views


       
      Github Repo
    • By Xonox
      After some years with a website working perfectly, Page Clone started to display some strange behaviour:
      1. When cloning some pages, it takes forever. The waiting icon is displayed but the page never appears. Only after I refresh the tree page, the new page appears:

      2. The other thing is that some pages can't be copied. The pages have the same templates but the users are able to copy some and other don't. It gives this error:

      (the URL is .../page/clone/?id=76376&login=1)
      Does someone have a clue why this is happening. I can't find any real difference between the pages that I'm trying to copy.
      One more thing: If the user is a super user, he's able to copy every page without problems.
      I think both errors might be related. Thanks!
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-11-15 2019-10-18 2019-08-08 2019-06-15 2019-06-02 2019-05-25 If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module and >= ProcessWire v3.0.0.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Advanced
      Define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Build entire dialog form in a hook
      You can hook after HannaCodeDialog::buildForm to add inputfields to the dialog form. You can define options for the inputfields when you add them. Using a hook like this can be useful if you prefer to configure inputfield type/options/descriptions/notes in your IDE rather than as extra attributes in the Hanna tag settings. It's also useful if you want to use inputfield settings such as showIf.
      When you add the inputfields you must set both the name and the id of the inputfield to match the attribute name.
      You only need to set an inputfield value in the hook if you want to force the value - otherwise the current values from the tag are automatically applied.
      To use this hook you only have to define the essential attributes (the "fields" for the tag) in the Hanna Code settings and then all the other inputfield settings can be set in the hook.
      Example buildForm() hook
      The Hanna Code attributes defined for tag "meal" (a default value is defined for "vegetables"):
      vegetables=Carrot meat cooking_style comments The hook code in /site/ready.php:
      $wire->addHookAfter('HannaCodeDialog::buildForm', function(HookEvent $event) { // The Hanna tag that is being opened in the dialog $tag_name = $event->arguments(0); // Other arguments if you need them /* @var Page $edited_page */ $edited_page = $event->arguments(1); // The page open in Page Edit $current_attributes = $event->arguments(2); // The current attribute values $default_attributes = $event->arguments(3); // The default attribute values // The form rendered in the dialog /* @var InputfieldForm $form */ $form = $event->return; if($tag_name === 'meal') { $modules = $event->wire('modules'); /* @var InputfieldCheckboxes $f */ $f = $modules->InputfieldCheckboxes; $f->name = 'vegetables'; // Set name to match attribute $f->id = 'vegetables'; // Set id to match attribute $f->label = 'Vegetables'; $f->description = 'Please select some vegetables.'; $f->notes = "If you don't eat your vegetables you can't have any pudding."; $f->addOptions(['Carrot', 'Cabbage', 'Celery'], false); $form->add($f); /* @var InputfieldRadios $f */ $f = $modules->InputfieldRadios; $f->name = 'meat'; $f->id = 'meat'; $f->label = 'Meat'; $f->addOptions(['Pork', 'Beef', 'Chicken', 'Lamb'], false); $form->add($f); /* @var InputfieldSelect $f */ $f = $modules->InputfieldSelect; $f->name = 'cooking_style'; $f->id = 'cooking_style'; $f->label = 'How would you like it cooked?'; $f->addOptions(['Fried', 'Boiled', 'Baked'], false); $form->add($f); /* @var InputfieldText $f */ $f = $modules->InputfieldText; $f->name = 'comments'; $f->id = 'comments'; $f->label = 'Comments for the chef'; $f->showIf = 'cooking_style=Fried'; $form->add($f); } }); Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By horst
      Wire Mail SMTP

      An extension to the (new) WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.4.2
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; }  
      A MORE ADVANCED DEBUG METHOD!
      You can add some debug code into a template file and call a page with it:
      $to = array('me@example.com'); $subject = 'Wiremail-SMTP Test ' . date('H:i:s') . ' äöü ÄÖÜ ß'; $mail = wireMail(); if($mail->className != 'WireMailSmtp') { echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; } else { $mail->from = '--INSERT YOUR SENDER ADDRESS HERE --'; // <--- !!!! $mail->to($to); $mail->subject($subject); $mail->sendSingle(true); $mail->body("Titel\n\ntext text TEXT text text\n"); $mail->bodyHTML("<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>"); $dump = $mail->debugSend(1); } So, in short, instead of using $mail->send(), use $mail->debugSend(1) to get output on a frontend testpage.
      The output is PRE formatted and contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection, like this one:
       
      Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      debugSend(1) - returns and / or outputs a (pre formatted) dump that contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection. (See above the example code under ADVANCED DEBUG METHOD for further instructions!)


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
       
×
×
  • Create New...