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

Thanks kongondo, did read but didn't connect that at all. That worked perfectly applied to the hanna code. 

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

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 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 Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 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 Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers 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 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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...