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   1 member

  • Similar Content

    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if anyone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put, I've been using MSN (...) for a number of years, and it's been great – but there have been some smallish issues with it, particularly with the markup generation part, and it's also doing some things in a way that just doesn't work for me – the xtemplates thing being one of these. In many ways it's less about features, and more about style.
      In MarkupMenu I've tried to correct these little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and PHP 7.1+, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) on my todo list.
      One smallish and rather specific difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site has a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to omit that 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • 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...