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 3

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...