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

In case this is important: I am currently running Proccesswire version 2.6.1 and HannaCode version 0.1.9.

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

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

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

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 Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180528, v1.0.4 add custom select statement option 180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen