Jump to content
ryan

Hanna Code

Recommended Posts

I don't have any problems running HannaCode on my 2.5.5 dev environment. Have you made sure that Hanna Code Text Formatter is applied to the field(s) that you put a Hanna on?

Share this post


Link to post
Share on other sites

Hi SiNNut

Yes, I had. Although for some reason it didn't appear to be saving and that could have been my problem.

I logged out, cleared the cache and it's working now. :)

Share this post


Link to post
Share on other sites

Separate Listing Permission

Not sure if this would be totally useful or not to everyone, but it might be nice to have a separate permission for just viewing a list of hanna codes for authors. No editing, or viewing of code, but just a list.

To make this work properly, they would also need descriptions, I would think.

This is really just so that contributors to the site know what codes are available and where they can be used.

  • Like 1

Share this post


Link to post
Share on other sites

I have installed and re-installedTextFormatterHannaCode but cannot see the item under setup. It appears fine as an option in a body field for instance and indicates it is installed correctly.

For info, I have  just upgraded this install from 2.3 to 2.5 but have not seen any other problems.

Any help appreciated.

Edited by kongondo
Moved Topic: Hanna Code has its own forum

Share this post


Link to post
Share on other sites

@Joss: not too far-fetched, but you could always try the Hanna Code Helper module too. Not trying to advertise it or anything, but I feel it's pretty convenient to see the tags right in the context where they're actually needed. Slightly longer description would be great thing to have, either way :)

  • Like 2

Share this post


Link to post
Share on other sites

Actually I had forgotten about that till after I wrote this and it does actually address a lot of the issues.

Though, it is one of those odd things that sometimes it is nice to look at a list. :)

Share this post


Link to post
Share on other sites

Somehow got things working by adding the hanna code module? Maybe I ought to read things a bit more carefully? Baffled but happy.

Share this post


Link to post
Share on other sites

I have a Hanna Code question and I am putting it here as a previous post was moved from its own thread. I can't see having a great big thread about a particular module being helpful to anyone, other than as a general module development conversation, and also can't see it being seen? I could understand if it was a separate forum, but not an 11 page thread.

Anyway, I am using hanna code for an item in a body field (for a blog post) However, when I publish excerpts of these posts on a summary, I dont want the hanna code to show. I tried to use a bit of php to refer to the template for the individual post

if($page->template == 'works'){
    echo "<div class='circle floatleft'><h2><i class='fa fa-line-chart'></i></h2></div>";
}

but as I am calling the same pages in the summary page

$articles = $pages->get("/blog/, limit=10")->children;

and looping, then calling $article->body, I think the template of the summary page is ignored.

I think the template that the hanna code snippet applies is still the one for the individual post.

So, any ideas how I can code out the hanna code snippet on the summary page? Hope that makes sense.

Thanks for taking a look.

Share this post


Link to post
Share on other sites

I have a Hanna Code question and I am putting it here as a previous post was moved from its own thread. I can't see having a great big thread about a particular module being helpful to anyone, other than as a general module development conversation, and also can't see it being seen? I could understand if it was a separate forum, but not an 11 page thread.

Why do you think the conversation wouldn't be seen? Module developers follow the support forums of their modules and are notified of new posts :-)

If we were to open new topics just because some threads were 'long' things could become chaotic and confusing very quickly.

This forum is Hanna Code's support forum. You have raised a Hanna Code support question hence it should be here :-).

post-894-0-16959000-1416426551_thumb.png

To further clarify...(not just for you):

Each module has (should have) its own support forum.

these are found here: https://processwire.com/talk/forum/4-modulesplugins/

post-894-0-10596900-1416426553_thumb.png

If one wants to discuss general module development they should post them in this sub-forum:

https://processwire.com/talk/forum/19-moduleplugin-development/

post-894-0-14509500-1416426552_thumb.png

I hope these clarify things.

  • Like 2

Share this post


Link to post
Share on other sites
 also can't see it being seen

yup, wrong terminology, what I meant is that it may be lost in a diverse thread. And I notice you call it a sub-forum, but to me this looks like a big thread?

If we were to open new topics just because some threads were 'long' things could become chaotic and confusing very quickly.

I don't see why a proper sub-forum with multiple threads would be chaotic. It would work just like any other on-topic forum? Couldn't we just as easily say that having a bunch of different points and questions in a single thread is confusing as well?

Might seem like I am carping. I am not honest :-) - just wondering about the efficacy of threads like this. Always get great friendly support here so don't think I am being churlish.

Anyway.... hopefully someone can help out re the post concerned ;)

Share this post


Link to post
Share on other sites

Not sure you have seen this in Hanna Code's PHP usage notes?

Please see the Javascript and PHP usage notes on the Hanna code entry screen.

The $page API variable available to your Hanna code represents the page where the Hanna code exists. It is possible for this to be different from wire('page'), which represents the page that originated the request.

Hence $page->template refers to your blog post template whereas wire('page')->template refers to your summary page template.

  • Like 1

Share this post


Link to post
Share on other sites

That has caught me out a few time ... its fine knowing all this stuff, but I am having a struggle actually remembering at the moment when it is most useful! Ouch! :)

Share this post


Link to post
Share on other sites

Hi all,

I found a small glitch in HannCode version 1.9. This only affects Hanna Code tag names which contain a . (dot) character and at the same time contain attributes.

For example:

[[admin.email]]   or [[admin_email recaptcha="true"]]

both work as expected and get processed and replaced.

But this

[[admin.email recaptcha="true"]]

does not.

In file TextformatterHannaCode.module change line 242 from

if(preg_match('!^([-_a-z0-9]+)([\s,]|$)!i', $expression, $matches)) {

to:

if(preg_match('!^([\.-_a-z0-9]+)([\s,]|$)!i', $expression, $matches)) {

solves the issue.

What is the best way to submit bugfixes/patches? Should I fork this on github and post a pull request?

  • Like 1

Share this post


Link to post
Share on other sites

What is the best way to submit bugfixes/patches? Should I fork this on github and post a pull request?

Yes. But it would also be worthwhile to first check if a similar issue has not yet been submitted.

Welcome to the forums too :-)

Share this post


Link to post
Share on other sites

Recursive Hanna Code

Hanna Code currently (version 1.9) does not support recursive Hanna tags, for example one Hanna Code tag is rendereing a partial which again contains another Hanna Code tag.

As I needed that requirement I made changes to support recursion to my private repository.

Is that something useful to the wider community? If yes I could issue a pull request.

  • Like 1

Share this post


Link to post
Share on other sites

Recursive Hanna Code

Is that something useful to the wider community? If yes I could issue a pull request.

let's say yes we can recursive ;)

Share this post


Link to post
Share on other sites

I have some very simple Hanna Code placed in a body field. It gives very mixed results.

This works and I've no opening or closing PHP tags. The docs say I dont need them.

$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
echo "
    <div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
    <img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
    {$supplier->title}
    </div>
    "
;}

I now need to top and tail that block with an opening and closing div.

To do this, I have to reinstate the opening and closing PHP tags as follows

<div class="row">

<?php
$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
echo "
    <div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
    <img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
    {$supplier->title}
    </div>
    "
    ;}
?>
</div>

This gives me an error 

Parse error: syntax error, unexpected '<' in /var/www/vhosts/test-domain.com/site/assets/cache/HannaCode/get-supply-partners.php on line 3

Currently, line 3 is blank due to formatting. I also tried placing all the code on the same 2 lines and I still get an error re. Line 3.

Do you think this is a general bug or a bug in HC 0.1.9? I'm running PW 2.5.17.

Share this post


Link to post
Share on other sites

Well you could either start with a close tag:

?> //close initial php open here
<div class="row">

<?php
$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
    echo "
       <div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
          <img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
          {$supplier->title}
       </div>
    ";
}
?>
</div>

or instead put your divs in the php code block and echo them out.

<?php
echo '<div class="row">';
$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
echo "
<div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
<img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
{$supplier->title}
</div>
"
;}
echo '</div>';
?>

Share this post


Link to post
Share on other sites
echo "<div class='row'>";

$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
echo "
    <div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
    <img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
    {$supplier->title}
    </div>
    "
    ;}
echo "</div>";

try this one

edit: adrian beat me....

Edited by mr-fan

Share this post


Link to post
Share on other sites

Because you have set the code as php, the module assumes anything you write is in php, which is why you don't need to use php tags.

But that means you need to close the php first before you put any pure html

Share this post


Link to post
Share on other sites

Well you could either start with a close tag:

?> //close initial php open here
<div class="row">

<?php
$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
    echo "
       <div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
          <img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
          {$supplier->title}
       </div>
    ";
}
?>
</div>

or instead put your divs in the php code block and echo them out.

<?php
echo '<div class="row">';
$suppliers = $pages->find("template=brfs-suppliers-detail");
foreach ($suppliers as $supplier) {
echo "
<div class=\"small-12 medium-6 large-4 columns partner-wrapper\" >
<img src=\"{$supplier->supply_partner_logo->url} \" class=\"partner-thumb\" >
{$supplier->title}
</div>
"
;}
echo '</div>';
?>

@Adrian - you just beat me to it :) Thats how I fixed too. 

Share this post


Link to post
Share on other sites

I usually use this approach for Hanna Code. A few initial lines in pure PHP code to init vars and prepare data enclosed in a <?php ... ?> tag and then follows the HTML "view" using PHP's alternative syntax to fill in variables and control structures like loops.

    <?php
    $images = wire()->page->images->findTag($tag);
    ?>

    <?foreach ($images as $image):?>
        <p><img src="<?=$image->url?>" alt="<?=$image->description?>"></p>
        <?if ($image->description):?>
            <small><?=$image->description?></small>
        <?endif?>
    <?endforeach?>

This approach allows separation of logic from presentation but still encapsulates both within a Hanna Code component.

  • Like 1

Share this post


Link to post
Share on other sites

I have this really odd HannaCode bug which I've been trying to fix for about a day now. I think it's finally beaten me  :mellow:

get-team-management is a simple loop through some team pages and outputs their name, job role, body and photo.

<?php
$teams = $pages->find("template=team_member,limit=10");
foreach ($teams as $team) {echo"
<div class=\"team-wrapper\">
<h2>{$team->title}</h2>
<h3>{$team->team_role}</h3>
{$team->body}
</div>
";}
?>

Hitting Save and Test on HannaCode displays the content perfectly. Great !

Next it's time to add my HC tag within body field. I'm adding it after a small piece of dummy intro text as per screengrab.

post-1166-0-89424400-1423221572_thumb.pn

The resulting output is single team biography (body field) from a single team member. There should be 8 team members outputted and the dummy text before my HC tag has vanished too. There should be a small intro paragraph followed by each team members title, role, body. 

The next logical step is to embed my PHP directly in the template and bypass HannaCode.

This works in that each team member has all the info required. 

Any ideas where to look on this one? I'm running the latest Dev 2.5.17.

My first thought was to check the team members were all published and all had the correct template (team_member). They do.

Next step was to try placing my echo directly into the template. That way I'd know if it was perhaps/or not HannaCode at fault.

Edited by kongondo
Moved to HC support forum

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
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...