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 teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


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




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      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! :)
×
×
  • Create New...