Jump to content
ryan

Hanna Code

Recommended Posts

Hi,

first of all: I think the addition of this particular module is great! I can think of quite a few itches I could scratch with that.

Something I've been wondering about: How would I go about accessing specific repeater fields with the Hanna Code.

Say for example I have a repeater including a Text field, a Date and a Price.

I'd fill the text Field with

Come on the [[date]], bring [[price]]$ in small used bills. Thank you for your cooperation.

The frontend should obviously render this as

Come on the 4th of July, bring 50$ in small used bills. Thank you for your cooperation.

If Text, Date and Price where just page fields, this would be pretty obvious. However for them being fields inside a repeater I think there's something like the jQuery siblings selector needed, but I don't see anything like that in the api documentation.

Any input on this would be very much appreciated :-)

Share this post


Link to post
Share on other sites

Is there any way to get Hanna code to render within Hanna code?

I've got two tags.

[[tooltip]] and [[info]]

What I'm trying to do is this:

[[tooltip text="[[info]]" tooltip="test"]]

And then using the following snippet within the [[tooltip]] hanna code:

$hanna = wire('modules')->get('TextformatterHannaCode');
echo "<a class='tooltip' href='#' title='{$tooltip}'>".$hanna->render($text)."</a>";

This doesn't seem to be working unfortunately. Any ideas on how to make this work?

[[info]] just echos out an img tag.

Cheers

Share this post


Link to post
Share on other sites

@Sinmok,

From your example you are trying to add a tooltip.   I don't know what front-end framework you are working with on your website, however with Zurb Foundation 4 you can do a tooltip using Hanna Code as follows:

<span data-tooltip class="has-tip" title="Tooltips are awesome, you should totally use them!">extended information</span>

Your Type would be Text/HTML.

Then you just add the Hanna Code in a field that supports Hanna Code.

This may not answer your specific request for having Hanna Code within Hanna Code, but it does show how a tooltip can be added using Hanna Code.  Good Day.

  • Like 2

Share this post


Link to post
Share on other sites

This turned out to be an issue with the order of variables returned by core TemplateFile::getArray. It was doing an array_merge which gave preference to API variables, preventing them from being overwritten. Maybe that's a good thing in general, but I don't think we want that limitation. I went ahead and changed it in dev. Now it gives preference to local variables, which enables Hanna Code to provide the behavior it was supposed to. 

I think I've found another issue related to the use of $page in a Hanna code: if the field containing the hanna code is in a repeater, $page seems to point to something internal to the repeater instead of pointing to the page containing the repeater field.

Example with a hanna code echoing the page id:

// in a field directly in the home page
echo $page->id;
--> 1

// in the field from a repeater on the same home page
echo $page->id;
--> 1060

From what I understand by looking at the repeater module source code, repeaters are implemented with pages. So the observed behavior is probably a side effect of this.

Any idea of how to fix this ? 

  • Like 1

Share this post


Link to post
Share on other sites

@jean-luk

Yes repeaters are in fact internal pages, so doing the following should help (not tested):

if ($page instanceof RepeaterPage) {

$id = $page->parent->id;

} else {

$id = $page->id;

} 

echo $id;
  • Like 2

Share this post


Link to post
Share on other sites

@slkwrm
 
Thanks for the hint.
 
Actually it turns out that the repeater page's parent is not the page where the repeater field is, but this page can be got by calling the method getForPage. So the correct code is:

$containerPage = $page;
if ($page instanceof RepeaterPage) {
   $containerPage = $page->getForPage();
}

// can be checked with
echo $containerPage->id;

I added this container page calculation at the right place (I hope!) in TextformatterHannaCode.module and the repeater field case now seems to work for hanna codes.
 

  • Like 5

Share this post


Link to post
Share on other sites

Finally I'm not sure about the best way of handling this hanna-code-inside-reapeater-field case…
 
On one hand, a naive hanna code writer like myself would expect $page to refer to the user-visible field container page;
 
On the other hand, having a reference to the current "repeater page" can be useful in many cases, like this one:

Something I've been wondering about: How would I go about accessing specific repeater fields with the Hanna Code.
[...]
 
If Text, Date and Price where just page fields, this would be pretty obvious. However for them being fields inside a repeater I think there's something like the jQuery siblings selector needed, but I don't see anything like that in the api documentation.
 
Any input on this would be very much appreciated  :-)

 
Maybe a solution would be to have two different PHP variables accessible from within the hanna code, where the one referring to the repeater page would be null if the current field is not part of a repeater.
 
Easy to implement, but, as always, not so easy to keep it consistent with the rest of the PW API. 
 
Ryan, your opinion about this?

Share this post


Link to post
Share on other sites

Got a feeling this is a server issue but I'm getting an error I can't seem to recover from after saving a simple HTML code:

Method Sanitizer::entities does not exist or is not callable in this context

I can't even load the Hanna Code config screen - even if I try to ununstall/install it again. It hasn't written any files to /site/assets/cache/HannaCode/ either.

I'm running PW 2.2.9 on PHP version 5.2.17. Stuck! :)

Share this post


Link to post
Share on other sites

Marty, not sure why there is no sanitizer entities method there. Maybe we didn't have it in 2.2, I don't recall. Try replacing your wire/core/Sanitizer.php file with a fresh copy. It should be fine to take the one from 2.3 or 2.4.

Jean-luc, glad to see you found the getForPage method. This is exactly the way that repeater pages are meant to refer to their containing page, whether in a Hanna code or elsewhere.

Share this post


Link to post
Share on other sites

Perhaps this has come up already in this thread, haven't read it all, and I don't want to be a nay-sayer, but if it's primarily aimed at super users i.e. us devs, why have a GUI at all? Why not leave out the whole visual stuff and have HannaCode parse the text and search for template files (or template file in a subdir like templates/hanna) with the HannaCode name.

[[my-hanna foo=bar]] looks for templates/hanna/my-hanna.php and passes the params like with any other regular template. This way we can edit our hanna-codes in our IDE or text editor of choice with all the highlighting and we can push it into version control, no need to fiddle around with exports or imports between installations.

Am I missing something?

Share this post


Link to post
Share on other sites

@owzim, just throwing in some possible reasons:

  • Not all superusers are developers. Whether or not that's a good thing, Hanna Code allows people with no access to actual code to add features that would normally require such an access -- or at least some way to edit files on disk.
  • It's not just about PHP code. Tiny snippets of random HTML or JS can be easily added without having to add files for those too.
  • Hanna Code provides easy way to quickly sketch and test code snippets you're not going to need in the longer term. This is also handy when working in an environment where same site exists on multiple locations sharing database but not code (in which case moving a snippet of code in disk from one location to another would typically require extra steps).

That being said, I really believe that Hanna Code would benefit from more fine-grained access management.

This could mean three different permissions: hanna-code-html, hanna-code-javascript and hanna-code-php. Or perhaps just two -- hanna-code to add all sorts of snippets and another, limited permission for creating only HTML + JS snippets.

The way it is right now, I can't imagine giving a client access to creating their own Hanna Code snippets, but if it allowed me to limit that access to less destructive features this module would have a lot more potential.

Edit: almost forgot to mention that of course you could already add the sort of thing you're talking about, though the syntax would be slightly different (filename as a variable). GUI doesn't make that impossible and you don't really have to use it unless you want to :)

  • Like 3

Share this post


Link to post
Share on other sites

...sorry don't read the whole threat, too

short questions about HannaCode:

-> Is ther a Overview/Post with contributed examples for "Hannas"

-> If yes who can i contribute

i've got a few of this little helpers from another system (the CMS Argos and i used and contributed before find PW) there was an Admintool that's called "Droplets". There exists a "Dropletgallery" and we had a WYSIWYG Plugin for choose one for the editor to use.

Best Regards mr-fan


Example for a "dropletCode" could this used in Hanna as it is or need special threatment or changes...

//:genQR creates QR Codes with google Charts API
//:Use: [[genQR?size=150&link=http://what-ever.com]]
 
 Parameters:
 $size - default is 200 px
 $link - default if nothing set is google.com
 
if ( !isset($size) ){    $size = 200; };
$width = $size;
$height = $size;
if ( !isset($link) ){ $link = "http://google.com"; };
$url = urlencode(".$link."); 
return "<img src=\"http://chart.googleapis.com/chart?chs={$width}x{$height}&cht=qr&chl=$url\" />";

just for the starting point - i've more like this to share if it's usefull :rolleyes:


a starting point coudl even be a gist repo?

post-2327-0-26193400-1401426363_thumb.jp

  • Like 2

Share this post


Link to post
Share on other sites

Perhaps this has come up already in this thread, haven't read it all, and I don't want to be a nay-sayer, but if it's primarily aimed at super users i.e. us devs, why have a GUI at all? Why not leave out the whole visual stuff and have HannaCode parse the text and search for template files (or template file in a subdir like templates/hanna) with the HannaCode name.

[[my-hanna foo=bar]] looks for templates/hanna/my-hanna.php and passes the params like with any other regular template. This way we can edit our hanna-codes in our IDE or text editor of choice with all the highlighting and we can push it into version control, no need to fiddle around with exports or imports between installations.

Am I missing something?

@ozwim - not sure if you already know about this, but i follow Soma's suggestion and have a folder called 'hannas' and then keep all the hanna codes there; and then using this in the hanna code itself:

include($config->paths->templates . "hannas/some-hanna-code.php");

@mr-fan - that's great - we should try and setup a place to share hanna codes... maybe github? I have a lot of examples also

  • Like 2

Share this post


Link to post
Share on other sites

@teppo, good points I haven't yet considered, perhaps partly because I don't know jack about that Hana Code Insert WP Plugin. I don't use WP :)

@Marcura, @Soma great one!

Share this post


Link to post
Share on other sites

Mr-fan, you're right, the PW Hanna system seems to be very like the "WB-droplets" we are familiar with, coming from WebsiteBaker. There is even an integration with the editor, called HannaCodeHelper. Check it out in the Modules repo.

  • Like 1

Share this post


Link to post
Share on other sites

Ok first try seems to work with given atr in Hanna Code like:

[[genQR size="400" link="http:\\google.com"]]

but the fallback option would be nice to have a QR Code from the current Link - May used for events or articles....

heres my code for first hanna experiments may i missed the wrong API handling??

<?php 

//:genQR creates QR Codes with google Charts API
//:Use: [[genQR?size=150&link=http://what-ever.com]]
//
// Parameters:
// $size - default is 200 px
// $link - default if nothing set is google.com
 
if ( !isset($size) ){    $size = 200; };
$width = $size;
$height = $size;
if ( !isset($link) ){ $link = $page->httpUrl; };

echo "<img src=\"http://chart.googleapis.com/chart?chs={$width}x{$height}&cht=qr&chl=$link\" />";
//  to testing link url echo "<p>$link</p>";

like written it works with a link="some.link" and if not it doesn't take the current url $page->httpUrl;
:(

for a repo would be a cool place to have something like a hanna code gallery or overview of some snippets...??

like in our old system (argos and mine) there was a snippetgallery for this: http://www.websitebakers.com/pages/droplets/official-library.php

maybe there is some inspriation for PW HannaCode or if i getting more familiar with PW i can port some for usage with PW.

Best Regards mr-fan

Share this post


Link to post
Share on other sites

To make PW more user friendly (especially for non-coders) I think it would be best to create a Hannacode subsection in the Modules section on the regular PW site. Personally I think regular users should not be send to some Github page, as it is far too technical, intimidating, and therefore unfriendly environment for non-coders. Hannacodes are (as far as I can tell, as a newer than new newbie) ready to use code snippets and as such could be offered on the regular site.

Share this post


Link to post
Share on other sites

By the way, what's the difference between Hannacodes and shortcodes?

Share this post


Link to post
Share on other sites
like written it works with a link="some.link" and if not it doesn't take the current url $page->httpUrl;

I am not quite sure whether you are having problems with your code working or not. It works perfectly for me if I don't define a link - it defaults to the current page and if I do define it goes to that link. Can you tell us exactly what isn't working and what the link is instead?

By the way, what's the difference between Hannacodes and shortcodes?

Effectively they are/do the same thing. I think Ryan got the name and inspiration from WP's Hana code.

Share this post


Link to post
Share on other sites

There is a Export/Import so here comes my first HannaCode that works for me....please test and give some feedback if it is helpfull or not and if there some issues like i'm no really good at PHP (I'm willing to learn and listen to pros...;)

!HannaCode:lorem:eyJuYW1lIjoibG9yZW0iLCJ0eXBlIjoiMiIsImNvZGUiOiJcLypoY19hdHRyXG5ibG9ja3M9XCJcIlxuaGNfYXR0cipcL1xuPD9waHBcclxuXHJcblwvXC86bG9yZW06IGNyZWF0ZXMgTG9yZW1JcHN1bSBUZXh0IHBhcmFncmFwaHNcclxuXC9cLzpVc2U6IFtbTG9yZW0/YmxvY2tzPTZdXSAobWF4IDYgcGFyYWdyYXBocylcclxuXC9cL1xyXG5cL1wvIFBhcmFtZXRlcnM6XHJcblwvXC8gJGJsb2NrcyAtIGRlZmF1bHQgaXMgMSBibG9ja1xyXG5cclxuJGxvcmVtID0gYXJyYXkoKTtcclxuJGxvcmVtW10gPSBcIkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0LCBjb25zZWN0ZXR1ZXIgYWRpcGlzY2luZyBlbGl0LiBVdCBvZGlvLiBOYW0gc2VkIGVzdC4gTmFtIGEgcmlzdXMgZXQgZXN0IGlhY3VsaXMgYWRpcGlzY2luZy4gVmVzdGlidWx1bSBhbnRlIGlwc3VtIHByaW1pcyBpbiBmYXVjaWJ1cyBvcmNpIGx1Y3R1cyBldCB1bHRyaWNlcyBwb3N1ZXJlIGN1YmlsaWEgQ3VyYWU7IEludGVnZXIgdXQganVzdG8uIEluIHRpbmNpZHVudCB2aXZlcnJhIG5pc2wuIERvbmVjIGRpY3R1bSBtYWxlc3VhZGEgbWFnbmEuIEN1cmFiaXR1ciBpZCBuaWJoIGF1Y3RvciB0ZWxsdXMgYWRpcGlzY2luZyBwaGFyZXRyYS4gRnVzY2UgdmVsIGp1c3RvIG5vbiBvcmNpIHNlbXBlciBmZXVnaWF0LiBDcmFzIGV1IGxlbyBhdCBwdXJ1cyB1bHRyaWNlcyB0cmlzdGlxdWUuPGJyIFwvPjxiciBcLz5cIjtcclxuJGxvcmVtW10gPSBcIkR1aXMgYXV0ZW0gdmVsIGV1bSBpcml1cmUgZG9sb3IgaW4gaGVuZHJlcml0IGluIHZ1bHB1dGF0ZSB2ZWxpdCBlc3NlIG1vbGVzdGllIGNvbnNlcXVhdCwgdmVsIGlsbHVtIGRvbG9yZSBldSBmZXVnaWF0IG51bGxhIGZhY2lsaXNpcyBhdCB2ZXJvIGVyb3MgZXQgYWNjdW1zYW4gZXQgaXVzdG8gb2RpbyBkaWduaXNzaW0gcXVpIGJsYW5kaXQgcHJhZXNlbnQgbHVwdGF0dW0genpyaWwgZGVsZW5pdCBhdWd1ZSBkdWlzIGRvbG9yZSB0ZSBmZXVnYWl0IG51bGxhIGZhY2lsaXNpLiBMb3JlbSBpcHN1bSBkb2xvciBzaXQgYW1ldCwgY29uc2VjdGV0dWVyIGFkaXBpc2NpbmcgZWxpdCwgc2VkIGRpYW0gbm9udW1teSBuaWJoIGV1aXNtb2QgdGluY2lkdW50IHV0IGxhb3JlZXQgZG9sb3JlIG1hZ25hIGFsaXF1YW0gZXJhdCB2b2x1dHBhdC48YnIgXC8+PGJyIFwvPlwiO1xyXG4kbG9yZW1bXSA9IFwiVXQgd2lzaSBlbmltIGFkIG1pbmltIHZlbmlhbSwgcXVpcyBub3N0cnVkIGV4ZXJjaSB0YXRpb24gdWxsYW1jb3JwZXIgc3VzY2lwaXQgbG9ib3J0aXMgbmlzbCB1dCBhbGlxdWlwIGV4IGVhIGNvbW1vZG8gY29uc2VxdWF0LiBEdWlzIGF1dGVtIHZlbCBldW0gaXJpdXJlIGRvbG9yIGluIGhlbmRyZXJpdCBpbiB2dWxwdXRhdGUgdmVsaXQgZXNzZSBtb2xlc3RpZSBjb25zZXF1YXQsIHZlbCBpbGx1bSBkb2xvcmUgZXUgZmV1Z2lhdCBudWxsYSBmYWNpbGlzaXMgYXQgdmVybyBlcm9zIGV0IGFjY3Vtc2FuIGV0IGl1c3RvIG9kaW8gZGlnbmlzc2ltIHF1aSBibGFuZGl0IHByYWVzZW50IGx1cHRhdHVtIHp6cmlsIGRlbGVuaXQgYXVndWUgZHVpcyBkb2xvcmUgdGUgZmV1Z2FpdCBudWxsYSBmYWNpbGlzaS48YnIgXC8+PGJyIFwvPlwiO1xyXG4kbG9yZW1bXSA9IFwiTmFtIGxpYmVyIHRlbXBvciBjdW0gc29sdXRhIG5vYmlzIGVsZWlmZW5kIG9wdGlvbiBjb25ndWUgbmloaWwgaW1wZXJkaWV0IGRvbWluZyBpZCBxdW9kIG1hemltIHBsYWNlcmF0IGZhY2VyIHBvc3NpbSBhc3N1bS4gTG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVlciBhZGlwaXNjaW5nIGVsaXQsIHNlZCBkaWFtIG5vbnVtbXkgbmliaCBldWlzbW9kIHRpbmNpZHVudCB1dCBsYW9yZWV0IGRvbG9yZSBtYWduYSBhbGlxdWFtIGVyYXQgdm9sdXRwYXQuIFV0IHdpc2kgZW5pbSBhZCBtaW5pbSB2ZW5pYW0sIHF1aXMgbm9zdHJ1ZCBleGVyY2kgdGF0aW9uIHVsbGFtY29ycGVyIHN1c2NpcGl0IGxvYm9ydGlzIG5pc2wgdXQgYWxpcXVpcCBleCBlYSBjb21tb2RvIGNvbnNlcXVhdC48YnIgXC8+PGJyIFwvPlwiO1xyXG4kbG9yZW1bXSA9IFwiQ3JhcyBjb25zZXF1YXQgbWFnbmEgYWMgdGVsbHVzLiBEdWlzIHNlZCBtZXR1cyBzaXQgYW1ldCBudW5jIGZhdWNpYnVzIGJsYW5kaXQuIEZ1c2NlIHRlbXB1cyBjdXJzdXMgdXJuYS4gU2VkIGJpYmVuZHVtLCBkb2xvciBldCB2b2x1dHBhdCBub251bW15LCB3aXNpIGp1c3RvIGNvbnZhbGxpcyBuZXF1ZSwgZXUgZmV1Z2lhdCBsZW8gbGlndWxhIG5lYyBxdWFtLiBOdWxsYSBpbiBtaS4gSW50ZWdlciBhYyBtYXVyaXMgdmVsIGxpZ3VsYSBsYW9yZWV0IHRyaXN0aXF1ZS4gTnVuYyBlZ2V0IHRvcnRvciBpbiBkaWFtIHJob25jdXMgdmVoaWN1bGEuIE51bGxhIHF1aXMgbWkuIEZ1c2NlIHBvcnRhIGZyaW5naWxsYSBtYXVyaXMuIFZlc3RpYnVsdW0gc2VkIGRvbG9yLiBBbGlxdWFtIHRpbmNpZHVudCBpbnRlcmR1bSBhcmN1LiBWZXN0aWJ1bHVtIGVnZXQgbGFjdXMuIEN1cmFiaXR1ciBwZWxsZW50ZXNxdWUgZWdlc3RhcyBsZWN0dXMuIER1aXMgZG9sb3IuIEFsaXF1YW0gZXJhdCB2b2x1dHBhdC4gQWxpcXVhbSBlcmF0IHZvbHV0cGF0LiBEdWlzIGVnZXN0YXMgcmhvbmN1cyBkdWkuIFNlZCBpYWN1bGlzLCBtZXR1cyBldCBtb2xsaXMgdGluY2lkdW50LCBtYXVyaXMgZG9sb3Igb3JuYXJlIG9kaW8sIGluIGN1cnN1cyBqdXN0byBmZWxpcyBzaXQgYW1ldCBhcmN1LiBBZW5lYW4gc29sbGljaXR1ZGluLiBEdWlzIGxlY3R1cyBsZW8sIGVsZWlmZW5kIG1vbGxpcywgY29uc2VxdWF0IHV0LCB2ZW5lbmF0aXMgYXQsIGFudGUuPGJyIFwvPjxiciBcLz5cIjtcclxuJGxvcmVtW10gPSBcIkNvbnNldGV0dXIgc2FkaXBzY2luZyBlbGl0ciwgc2VkIGRpYW0gbm9udW15IGVpcm1vZCB0ZW1wb3IgaW52aWR1bnQgdXQgbGFib3JlIGV0IGRvbG9yZSBtYWduYSBhbGlxdXlhbSBlcmF0LCBzZWQgZGlhbSB2b2x1cHR1YS4gQXQgdmVybyBlb3MgZXQgYWNjdXNhbSBldCBqdXN0byBkdW8gZG9sb3JlcyBldCBlYSByZWJ1bS4gU3RldCBjbGl0YSBrYXNkIGd1YmVyZ3Jlbiwgbm8gc2VhIHRha2ltYXRhIHNhbmN0dXMgZXN0IExvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0LiBMb3JlbSBpcHN1bSBkb2xvciBzaXQgYW1ldCwgY29uc2V0ZXR1ciBzYWRpcHNjaW5nIGVsaXRyLCBzZWQgZGlhbSBub251bXkgZWlybW9kIHRlbXBvciBpbnZpZHVudCB1dCBsYWJvcmUgZXQgZG9sb3JlIG1hZ25hIGFsaXF1eWFtIGVyYXQsIHNlZCBkaWFtIHZvbHVwdHVhLiBBdCB2ZXJvIGVvcyBldCBhY2N1c2FtIGV0IGp1c3RvIGR1byBkb2xvcmVzIGV0IGVhIHJlYnVtLiBTdGV0IGNsaXRhIGthc2QgZ3ViZXJncmVuLCBubyBzZWEgdGFraW1hdGEgc2FuY3R1cyBlc3QgTG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQuIExvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0LCBjb25zZXRldHVyIHNhZGlwc2NpbmcgZWxpdHIsIHNlZCBkaWFtIG5vbnVteSBlaXJtb2QgdGVtcG9yIGludmlkdW50IHV0IGxhYm9yZSBldCBkb2xvcmUgbWFnbmEgYWxpcXV5YW0gZXJhdCwgc2VkIGRpYW0gdm9sdXB0dWEuIEF0IHZlcm8gZW9zIGV0IGFjY3VzYW0gZXQganVzdG8gZHVvIGRvbG9yZXMgZXQgZWEgcmVidW0uIFN0ZXQgY2xpdGEga2FzZCBndWJlcmdyZW4sIG5vIHNlYSB0YWtpbWF0YSBzYW5jdHVzIGVzdCBMb3JlbSBpcHN1bSBkb2xvciBzaXQgYW1ldC48YnIgXC8+PGJyIFwvPlwiOyBcclxuaWYgKCFpc3NldCgkYmxvY2tzKSkgJGJsb2NrcyA9IDE7XHJcbiRibG9ja3MgPSAoaW50KSRibG9ja3MgLSAxO1xyXG5pZiAoJGJsb2NrcyA8PSAwKSAkYmxvY2tzID0gMDtcclxuaWYgKCRibG9ja3MgPiA1KSAkYmxvY2tzID0gNTtcclxuJHJldHVybnZhbHVlID0gXCJcIjtcclxuZm9yICggJGk9MCA7ICRpPD0kYmxvY2tzIDsgJGkrKykge1xyXG4gICAgJHJldHVybnZhbHVlIC49ICRsb3JlbVskaV07XHJcbn1cclxuZWNobyAkcmV0dXJudmFsdWU7In0=/!HannaCode

as far as i understand copy this in the import field of the HannCode Module.

Best Regards mr-fan

@Argos: PW is much more Coding like our older System but for the frontend it isn't that hard to use it seems to me. For the Frontend it depends an procedural Coding combining with the PW API it's really amazing - Backend and process are mostly OOP PHP and a little bit more devwork

Share this post


Link to post
Share on other sites

I am not quite sure whether you are having problems with your code working or not. It works perfectly for me if I don't define a link - it defaults to the current page and if I do define it goes to that link. Can you tell us exactly what isn't working and what the link is instead?

Effectively they are/do the same thing. I think Ryan got the name and inspiration from WP's Hana code.

so i don't know what is wrong:

[[genQR size="200" link="http:\\google.com"]]
[[genQR size="200"]]

and same code as above but with echo the $link give me a screen like this (second QR is emty with no $link is given)

(....system is PW 2.4 clean install with some testaddons and the basic-site profil)

thanks for take a look

post-2327-0-62607900-1401468082_thumb.jp

Share this post


Link to post
Share on other sites

I am at a loss for why it isn't working for you. Not that it matter, but here is a slightly cleaned up version of your code:

if (!isset($size)) $size = 200;
if (!isset($link)) $link = $page->httpUrl;

echo "<img src='http://chart.googleapis.com/chart?chs={$size}x{$size}&cht=qr&chl=$link' />";

You had unnecessary curly braces and extra semi-colons and also since these are square, there is no need to define the width and height separately. If you wanted you could even make it a one liner:

echo "<img src='http://chart.googleapis.com/chart?chs=" . (isset($size) ? $size : 200) ."x" . (isset($size) ? $size : 200) ."&cht=qr&chl=" . (isset($link) ? $link : $page->httpUrl) . "' />";

Although you do sacrifice a little readability.

One other quick thing - in your google.com example, you are using backslashes instead of forwardslashes - probably just a typo :)

Share this post


Link to post
Share on other sites

Effectively they are/do sthe same thing. I think Ryan got the name and inspiration from WP's Hana code.

I'm sorry, I wasn't clear enough. What I meant was, what is the difference between the modules "Hannacode" and "Shortcode"? These are two different shortcode type modules.

http://modules.processwire.com/modules/process-hanna-code/

http://modules.processwire.com/modules/markup-shortcodes/

Share this post


Link to post
Share on other sites

Oh right - sorry I misunderstood. Both provide similar functionality, although I haven't actually used Nico's shortcode module, so not completely sure on the differences. I guess my advice would be to experiment with both and see which best provides you the functionality you need.

Share this post


Link to post
Share on other sites

thanks for get into it adrian....so here is the next one...

//:Greeting: creates output depending on actual hour
//:Use: [[greeting]] (for eg on a headline)
 

!HannaCode:Greeting:eyJuYW1lIjoiR3JlZXRpbmciLCJ0eXBlIjoiMiIsImNvZGUiOiI8P3BocFxyXG5cclxuXC9cLzpHcmVldGluZzogY3JlYXRlcyBvdXRwdXQgZGVwZW5kaW5nIG9uIGFjdHVhbCBob3VyXHJcblwvXC86VXNlOiBbW2dyZWV0aW5nXV0gKGZvciBlZyBvbiBhIGhlYWRsaW5lKVxyXG5cclxuJEhvdXJPZkRheSA9IGRhdGUoXCJHXCIpO1xyXG5pZiAoJEhvdXJPZkRheSA8IDEyKSB7XHJcbiAgICBlY2hvICAnR29vZCBNb3JuaW5nJztcclxufSBlbHNlaWYgKCRIb3VyT2ZEYXkgPCAxOCkge1xyXG4gICAgZWNobyAnR29vZCBBZnRlcm5vb24nO1xyXG59IGVsc2Uge1xyXG4gICAgZWNobyAnR29vZCBFdmVuaW5nJztcclxufSJ9/!HannaCode

If it be ok - from the modside we could make a new Threat with only HannaCode Examples as Posts - i would sort them into groups in a first post? If this is welcome?

Best Regards mr-fan

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 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
       
       
    • By Robin S
      Sanitizer EasySlugger
      Allows the use of the EasySlugger library as Sanitizer methods.
      Installation
      Install the Sanitizer EasySlugger module.
      Usage
      The module adds four new sanitizer methods.
      slugger($string, $options)
      Similar to $sanitizer->pageName() - I'm not sure if there are any advantages over that method. Included because it is one of the methods offered by EasySlugger.
      $slug = $sanitizer->slugger('Lorem Ipsum'); // Result: lorem-ipsum utf8Slugger($string, $options)
      Creates slugs from non-latin alphabets.
      $slug = $sanitizer->utf8Slugger('这个用汉语怎么说'); // Result: zhe-ge-yong-han-yu-zen-me-shuo seoSlugger($string, $options)
      Augments the string before turning it into a slug. The conversions are related to numbers, currencies, email addresses and other common symbols.
      $slug = $sanitizer->seoSlugger('The price is $5.99'); // Result: the-price-is-5-dollars-99-cents See the EasySlugger readme for some more examples.
      seoUtf8Slugger($string, $options)
      A combination of utf8Slugger() and seoSlugger().
      $slug = $sanitizer->seoUtf8Slugger('价钱是 $5.99'); // Result: jia-qian-shi-5-dollars-99-cents $options argument
      Each of the methods can take an $options array as a second argument.
      separator (string): the character that separates words in the slug. Default: - unique (bool): Determines whether a random suffix is added at the end of the slug. Default: false $slug = $sanitizer->utf8Slugger('这个用汉语怎么说', ['separator' => '_', 'unique' => true]); // Result: zhe_ge_yong_han_yu_zen_me_shuo_3ad66c4  
      https://github.com/Toutouwai/SanitizerEasySlugger
      https://modules.processwire.com/modules/sanitizer-easy-slugger/
    • By Robin S
      If you've ever needed to insert links to a large number of files within CKEditor you may have found that the standard PW link modal is a somewhat slow way to do it.
      This module provides a quicker way to insert links to files on the page being edited. You can insert a link to an individual file, or insert an unordered list of links to all files on the page with a single click.
      CKEditor Link Files
      Adds a menu to CKEditor to allow the quick insertion of links to files on the page being edited.

      Features
      Hover a menu item to see the "Description" of the corresponding file (if present). Click a menu item to insert a link to the corresponding file at the current cursor position. The filename is used as the link text. If you Alt-click a menu item the file description is used as the link text (with fallback to filename if no description entered). If text is currently selected in the editor then the selected text is used as the link text. Click "* Insert links to all files *" to insert an unordered list of links to all files on the page. Also works with the Alt-click option. Menu is built via AJAX so newly uploaded files are included in the menu without the page needing to be saved. However, descriptions are not available for newly uploaded files until the page is saved. There is an option in the module config to include files from Repeater fields in the edited page. Nested Repeater fields (files inside a Repeater inside another Repeater) are not supported. Installation
      Install the CKEditor Link Files module.
      For any CKEditor field where you want the "Insert link to file" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "LinkFilesMenu" to the "CKEditor Toolbar" settings field.
       
      http://modules.processwire.com/modules/cke-link-files/
      https://github.com/Toutouwai/CkeLinkFiles
    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate a repeater item from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
×
×
  • Create New...