Jump to content
ryan

Hanna Code

Recommended Posts

Does width() or size() not work with Hanna Code?

I've something like this:

<?php
$out = '';

if ( isset($ma) ){ 

    //get mitarbeiter
    $mitarbeiter = $pages->get("template=part_ma,shortcut=$ma");
    if ($mitarbeiter) {
        
        //get the original image
        $image = $mitarbeiter->mitarbeiter_bild;
        //get thumbnail
        $thumb = $image->width(90);
        
        //render mitarbeiter
        $out .= '
                <div class="b-author">
        			<p>'.$mitarbeiter->title.'<br><span>'.$mitarbeiter->headline.'</span></p>
        			<img alt="'.$mitarbeiter->title.'" src="'.$thumb->url.'">
        		</div>
        		';
    }
} else {
    $out = 'noting there!'; 
}

echo $out;

works in a template but with Hanna code i get

Call to a member function width() on a non-object

don't know why - if i remove width() or size() image is working but this is not good since it is the wrong size...

Best Regards mr-fan

(normal single image field without something special - PW dev 2.6.19)

Share this post


Link to post
Share on other sites

Recursive hanna codes is mentioned already a few time in this topic. There's an open pull request on the github repo, that adds support for that, but the official release doesn't have that right now.

+1 for the bug with recursive/nested hanna code textformatters, +1 for the github pull request which does fix the issue, and +1 for having it integrated to the official release

cheers

Share this post


Link to post
Share on other sites

Hi, 

I wrote some simple Hanna code for outputting external links given an identifier and a link text. The actual link URL is stored in a repeater field along with a unique id.

Example usage:

[[link id=myid text="My Great Link"]]

Default attributes:

id
text
target=_blank
 
Code:
<?php

$link = $pages->get("template=repeater_links, identifier={$id}")->link;

echo "<a href='{$link}' target='{$target}'>{$text}</a>";

?>
The problem is that the value of the text attribute ("My Great Link" in the example above) gets cut off at the first whitespace ("My). 
 
From the module description I learnt that in order to pass a string containing blank characters, all I needed to do was put quotes around the attribute. However, it seems I am still missing something, and it would be great if someone could point me to the right direction.
 
Cheers, 
 
Stefan
Edited by kongondo
Moved your question to HC's support forum

Share this post


Link to post
Share on other sites

Just tested and works fine here.

Maybe you take a look at other textformatters or try to change your code....here is the changed example i used to test on normal pages:

<?php

$template = "basic-page";

//search for special content
//$link = $pages->get("template=repeater_links, identifier={$id}");

//seach normal pages
$link = $pages->get("template={$template}, id={$id}");

//check if $link has a page for output
if ($link != "") {
    echo "<a href='{$link->url}' target='{$target}'>{$text}</a>";
}

regards mr-fan

  • Like 2

Share this post


Link to post
Share on other sites

@mr-fan

You solved the issue!

Thanks to you mentioning other textformatters I took a closer look at the body field, where the Hanna code was to be applied to - only to find out that the HannaCode textformatter was applied after the textile textformatter. Switching both resolved the issue immediately!

Best regards,

  • Like 2

Share this post


Link to post
Share on other sites

I am trying to create a hanna code [[side-menu]] to display a static menu. If I put the menu html in the hanna file directly it works fine. What I'd want though is to keep the menu html in a external file and just let the hanna code include it. So in my hanna code I put:

<?php

include('/site/templates/mysidemenu.php');

?>

This does not work - no errors just no output. The menu in mysidemenu.php is just plain html. Not sure what I am missing on this. 

RESOLVED: I determined that if I write the include like this it will work as expected:

include($config->paths->templates.'/mysidemenu.php');

Surprised though that I didn't see a file not found on the first approach.

  • Like 1

Share this post


Link to post
Share on other sites

I've seen this issue before on the forums.  I believe you have to use $config->paths->templates as part of your include.

Alternatively, if you have a page that utilizes mysidemenu.php as its template file you could just use render, like:

echo $pages->get("/path/to/page/")->render(); // add ['prependFile'=>''] inside of render if necessary

Share this post


Link to post
Share on other sites

Yes that's true. However I may extend the hanna code with a parameter to allow me to load different menu files with it or possibly load a menu based on the current page it is on.

Share this post


Link to post
Share on other sites

RESOLVED: I determined that if I write the include like this it will work as expected:

include($config->paths->templates.'/mysidemenu.php');

Surprised though that I didn't see a file not found on the first approach.

I like this approach. HannaCode is an integral part of most of my sites but I find it easier to upload chunks of code via my FTP editor.

And by using a proper text editor, I have better syntax highlighting etc. 

I put them in a sub-folder just to keep them separate from main templates

include($config->paths->templates.'/chunks/get-client-logos.php');

Only problem I have is ye olde recursive Body not working unless I manually update the Module.

Share this post


Link to post
Share on other sites

Wheren't those hanna code snippets actually stored as files? So you should be able to edit those directly.

you can't edit the hanna code 'cached' files directly

  • Like 1

Share this post


Link to post
Share on other sites

Anyone have tested hannacode in PW3?

When I use [[image src=pic1.jpg]] in PW2 — Hanna trim quotes and  sends pic1.jpg to src var, but in PW3 it includes "" to string and looks like src=>"pic1.jpg", so in the rendered code I get _quot_pic1.jpg_quot_

p.s. [[image src=pic1.jpg]] and [[image src=pic1.jpg]] works fine but...

Share this post


Link to post
Share on other sites

Using the following code in Hanna code always evaluates as TRUE:

if ($page->id == "1187") {
    echo $page->id;
}

or

if ($page == $pages->get("1187")) {
    echo $page->id;
}

returns true and prints out 1187 no matter what page I run the code on  ??? 
I should be able to use $page and $pages in Hanna code without problem or did I misunderstood something?
Thanks
 

Share this post


Link to post
Share on other sites

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.

http://modules.processwire.com/modules/process-hanna-code/

I am guessing your HC exists on the page with ID 1187? So it will always evaluate to true. Use wire('page') to refer to pages originating the request.

  • Like 2

Share this post


Link to post
Share on other sites

I have some trouble with an "unstable" Hanna Code at my 2.6.1 site. Whenever I edited a php code, I was redirect to a 404 front end error. So I installed Hanna Code afresh. But also when I am trying to add a new php code, I get the error. Creating a html code works.

Any ideas?

(I tried with debug mode on, but got no notifications.)

Share this post


Link to post
Share on other sites

Hi 

after I changed a domain to ssl, HannaCode throws on error on each saving. Anyone any idea on how this could be solved?

Share this post


Link to post
Share on other sites

http://modules.processwire.com/modules/process-hanna-code/

I am guessing your HC exists on the page with ID 1187? So it will always evaluate to true. Use wire('page') to refer to pages originating the request.

Kongondo, thank you, that was it indeed. I overlooked that part. Sorry for only reacting now, I keep forgetting to follow the topics and just assume I'm added automatically. ;)

Share this post


Link to post
Share on other sites
I keep forgetting to follow the topics and just assume I'm added automatically.

Just in case you don't know, there is a setting under your forum profile for automatically following topics that you post to.

  • Like 1

Share this post


Link to post
Share on other sites

I have some trouble with an "unstable" Hanna Code at my 2.6.1 site. Whenever I edited a php code, I was redirect to a 404 front end error. So I installed Hanna Code afresh. But also when I am trying to add a new php code, I get the error. Creating a html code works.

Any ideas?

(I tried with debug mode on, but got no notifications.)

Anyone else got this problem? I tried on multiple installations of ProcessWire. Always when trying to create (or save an existing) Hanna Code in PHP, I'm throw and error. I.e. this one:

Forbidden
You don't have permission to access /processdisplay/processwire/setup/hanna-code/edit/ on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Share this post


Link to post
Share on other sites

That sounds like wrong directory/file permissions.

That might be! I checked on a local installation as well, no problems there. Probably some permissions being mixed up on copy to a live site, which most of my pages have been that I have tested on.

Any idea what specific folder or file I could check for this? I've been looking here and there now, without luck.

Share this post


Link to post
Share on other sites

Status: I have found that my described issue is related to my current host. I set up a test on my old host and it gave me full access to edit/create PHP with Hanna Code again. I have not pinpointed exactly what requirements I need on my current host.

Share this post


Link to post
Share on other sites

Status: I have found that my described issue is related to my current host. I set up a test on my old host and it gave me full access to edit/create PHP with Hanna Code again. I have not pinpointed exactly what requirements I need on my current host.

You could check with your host to see if they are running mod_security.

I just struck the same 404 problem when I use an include in my Hanna PHP code. My host lets me disable mod_security via htaccess, and sure enough when I disable it the 404 problem is gone.

  • Like 2

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 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 (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...