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

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...