Jump to content
ryan

Hanna Code

Recommended Posts

For efficiency reasons, Textformatter modules run from a single instance, so I'm guessing this is a side effect of that. I'll look into options for how we might get around the issue the next time I'm making updates to it. But assuming that 'body' is a rich text field and Hanna Code is the only Textformatter you had on it, you could probably get the unformatted version of it from your Hanna code and use that instead, to avoid triggering the circular reference (or whatever it's called). 

echo $child->getUnformatted('body'); 
  • Like 1

Share this post


Link to post
Share on other sites

right - should have thought of that, getUnformatted..  for now i just went with the template approach;

I was trying out ways to do more in the admin and less in the template code, as a means to eventually give the clients more flexibility;

Share this post


Link to post
Share on other sites

Realy nice this module.

I noticed when using the "Hanna Code Text Formatter" to output a field that has also "Hanna Code Text Formatter" you need to set Output Filtering to false at some point.

In my example i wanted to output the page title of multiple pages, while the page title itself also had the "Hanna Code Text Formatter" attached. Then it would show only the last title.

Edit: i just see that this is kinda what Ryan mentioned 2 posts before.

echo $child->getUnformatted('body'); 

The following works also, thats what i am using, but i suppose its the "same same, but different":

$child->of(false);
echo $child->body; 
  • Like 1

Share this post


Link to post
Share on other sites

How can you pass parameters to a selector in Hanna Code; for some reason i can't get it to work;

i have an attribute called "range" and then my hanna tag looks like this:

[[works range=<2000]]

which means my $range variable is <2000

the $workrange variable is then work_year<2000,

but the code doesn't work...

$workrange = "";
if($range) {$workrange = " work_year{$range}, "; }

$works = $pages->find("template=work,$workrange sort=-work_year");

$out = '<ul>';

foreach($works as $work) {
    $out .= "<li>{$work->title}- {$work->work_year}</li>"; 
}

$out .= '</ul>';

echo $out;

the selector works if i put the work_year<2000 directly in the code, it just doesn't work with hanna code.

it also works if I use an = sign not a > or <.... so i get results if i put in range==2000 to the tag, which makes the $range var be "=2000"

Share this post


Link to post
Share on other sites

so i guess i should assume that hanna code can't handle PHP comparison operators?

Share this post


Link to post
Share on other sites

so i guess i should assume that hanna code can't handle PHP comparison operators?

I guess it is safer to assume that Ryan has been quite busy lately ;):D

  • Like 1

Share this post


Link to post
Share on other sites

Sorry Kongondo, I guess it is safer to assume that Ryan has been quite busy as long as I know ProcessWire. :)

  • Like 1

Share this post


Link to post
Share on other sites

right thanks as always kongondo...  it's not a huge rush, i was just wondering if anyone else had done hanna codes with comparison operators, and if there were some examples i could look at to determine if I'm doing something wrong... i also think it will be good to eventually have a repository of hanna code examples; 

hanna codes are going to be really essential to this one site i'm working on, in order to let the editors place tags for redundant info, such as telephone # etc...

  • Like 1

Share this post


Link to post
Share on other sites
i was just wondering if anyone else had done hanna codes with comparison operators, 

I'm not sure I understand the question? The only thing I can think of you might be talking about is using comparison operators where you pass attributes to the Hanna code? The thing is, attributes are no different from HTML attributes (key=value)... they are assignments, not comparisons. So I'm confused about the question. 

Share this post


Link to post
Share on other sites

i just meant that i can't get this hanna code to work with less than or greater than symbols, like this:

[[works range=<2000]]

i get no results for the selector; this does work if i put the selector directly in the code, as per original post on this;

thanks!

Share this post


Link to post
Share on other sites

@Macrura: first of all, if you've enabled HTML Entity Encoder, make sure it comes in after, not before, Hanna Code textformatter. The code snippet you posted earlier works just fine for me, so I'm guessing something else is wrong.. most likely another textformatter messing with markup before it gets sent to Hanna Code.

If that doesn't solve your problem, try debugging your snippet, ie. what's the actual attribute value in there.

  • Like 2

Share this post


Link to post
Share on other sites

@teppo - thanks, i finally got it to work, i had to decode the > and < signs, that's what i was wondering about with hanna code and why i originally was asking about using comparison operators like > and <, since in the editor they get encoded and that's why the selectors were not working...

i just had to add this line and it works now:

if($range) $range = html_entity_decode($range);
  • Like 1

Share this post


Link to post
Share on other sites

I think I have discovered a bug with images.

When using the save+test feature, i get errors with image field.

THe image field is a single image field and I write:

$page->image->size(0,50)->url

TemplateFile: Method Pageimages::size does not exist or is not callable in this context

 
So no matter what image field max files is set to it's always threated as array. But on front-end the code works, just not in the preview/test.
 
I have to write 
 
$page->image->first()->size(0,50)->url
 
to make it work in the admin preview, but then the code doesn't work anymore on front-end.
 
 
Ace editor:
 
I already got this with the ace editor fieldtype from adam, the code has tabs added at the end of the text. Sometimes it grows and grows after saving the code...

Share this post


Link to post
Share on other sites
When using the save+test feature, i get errors with image field.

Soma, it sounds like output formatting is disabled in test mode. Can you try the attached to see if that fixes it?

TextformatterHannaCode.module

I already got this with the ace editor fieldtype from adam, the code has tabs added at the end of the text. Sometimes it grows and grows after saving the code...

Do you know if this is an issue with AceEditor, or something about the way I've implemented it? I only ask since you mentioned Adam's inputfield had the same issue. 

Share this post


Link to post
Share on other sites

div style="color:rgb(0,0,0);font-family:Times;font-size:medium;">Strange inability to migrate Hanna between two hosts

 
I have a local dev site that I copied to a remote dev site. All good (copy of files, export and import of DB).
 
Then on the remote dev site I added Hanna module, all good.
 
Now I have just re-sync'd the files back from the remote site to local (and sure enough the Module files for Hanna came down) and exported the remote db and imported it locally. All good, PW works AOK. Except however, the local system seems to only partially know it is meant to have Hanna.
 
If I look under Admin > Modules it's not listed, but there is a menu item for Setup > Hanna and I can visit it and PW admin says "This page has no Process assigned".
 
To date with all sites I have always used Navicat.app to simply Backup/Import in whichever direction I needed a db to be copied and all good. I will try actually deleting the local database, making a new empty one and then importing to that (in case it's something weird there) and report back in this thread. Did that and it made no difference.
 
Has anyone else had this problem?
 
Update 2013-10-01-0822 EST: I took a snapshot of the site and db (in case) and then went ahead and used Modules Manager to install Hanna (even tho it was already sorta installed). The 'install' occurred without a hitch, as if Hanna was not there, and the codes that had been plain text on the site immediately changed to their correct output.
 
Still puzzled and slightly concerned by this, hope reporting it is of some help if at some point it's debugged/explained. Update: I think based on what I suspect and Ryan's comment (below) it must have been a bad FTP, even tho I tried hard to rule that out (below x 2). Happy bunny ^_^
Edited by alanfluff

Share this post


Link to post
Share on other sites

It doesn't sound like a DB migration issue, it really sounds like a file migration issue. My best guess is either: 1) File permissions on your Hanna code modules rendered it unreadable to your web server; or 2) that you had Hanna code installed as a symlink on your source server, and the symlink didn't migrate or didn't match up on the target server. That would explain why you'd have a Hanna Code Setup menu item and DB entries, but no ability to run it. Installing through Modules manager would have fixed it since it knows to install the files into the right place with the right permissions, etc. 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks very much for that analysis Ryan. It's good to read you think it's 'files' not 'database' and reading your comment I think that too.

I used Transmit.app and hopefully but perhaps not coincidentally it had crashed occasionally. On this occasion I was very careful to check it really thought the two sites were fully in sync but I am not confident that that test necessarily checks permissions etc and so perhaps it was an initial bad sync from my FTP that then got overlooked on subsequent check-sync runs.

Long story short, confidence still at 100% in PW and robustness (the most polished product of it's type I've used) and I'm off to look at alternatives to Transmit (tho there is much I like about it). Cheers!

  • Like 1

Share this post


Link to post
Share on other sites

I used to use Transmit and honestly never had the syncing working quite right with it. Though this was years ago, and Transmit is pretty much the most popular FTP app in OS X. I would be surprised if it were still buggy in that respect. I personally use Yummy FTP now, but I generally try to avoid using any FTP for transferring files unless it's the only option. I have a strong preference for rsync. 

  • Like 1

Share this post


Link to post
Share on other sites

On a completely other topic I was looking at rsync for webserver backup and as I was new to it the initial intro read was exciting as it looked like such a robust technology.

So I'm very interested to see you use rsync over FTP SFTP etc and I've seen only good comments so far re arRsync (rsync for command line weaklings).

Off to go have a play, thanks for the tip Ryan!

  • Like 1

Share this post


Link to post
Share on other sites

I really love rsnapshot: http://www.rsnapshot.org/

It is still command line and uses rsync, but handles all the incremental backup setup for you. Just setup and call from cron!

  • Like 3

Share this post


Link to post
Share on other sites

Strangely, i too have developed a great fondness for rsync as "it just bloody works !!" :rolleyes:

Have downloaded that app you linked to @alanfluff and will have a play. Perhaps its a good baby step towards learning how to use all those rsync options in the man pages? Shall see...

Speaking of which, I found this to be a really great and accessible link / reference to all the unix commands on a Mac: http://ss64.com/osx/

  • Like 1

Share this post


Link to post
Share on other sites

Thanks adrian and Zahari—checking out rsync and OSX ref bookmarked! ^_^

Share this post


Link to post
Share on other sites

having trouble with this, for some reason the hanna code is not working with atttributes like this [[accordion title=Some Title]]

this one has an attribute called 'link'.

all it outputs is "Some

but i don't get why my variable is not being fully passed to HC, i'm following the instructions from the ReadMe

<?php 
echo "<div class='trigger'>
	  <a href='#'>";
echo $link;
echo "</a>
      </div>
	  <div class='hide'>
	  ";
!HannaCode:accordion:eyJuYW1lIjoiYWNjb3JkaW9uIiwidHlwZSI6IjIiLCJjb2RlIjoiXC8qaGNfYXR0clxubGluaz1cIlNvbWUgVGV4dFwiXG5oY19hdHRyKlwvXG48P3BocCBcclxuZWNobyBcIjxkaXYgY2xhc3M9J3RyaWdnZXInPlxyXG5cdCAgPGEgaHJlZj0nIyc+XCI7XHJcbmVjaG8gJGxpbms7XHJcbmVjaG8gXCI8XC9hPlxyXG4gICAgICA8XC9kaXY+XHJcblx0ICA8ZGl2IGNsYXNzPSdoaWRlJz5cclxuXHQgIFwiOyJ9/!HannaCode

Share this post


Link to post
Share on other sites

@Macrura: are you using Hanna Code in a CKEditor field?

I recently debugged similar issue and eventually found out that it was caused by CKEditor encoding " to " (default behavior) before Hanna Code had a chance to grab it. Similar issues could be caused by other editors, textformatters placed before Hanna Code etc.

Share this post


Link to post
Share on other sites

yes - i'm using CK editor (and your hanna code helper...thanks for that!!!).;

so what would be the fix for this, is there a way to prevent CK editor from encoding automatically? 

this issue also relates to my posts a few up about php comparison operators like < and >; the reason those hanna codes were not working was from the same editor problem;

being that this is really a major issue for Hanna Code, i think this should be addressed, or at least some instructions or disclaimer in the readme file, as i have spent several hours trying to figure out a fix/workaround for this..

so i added this to the config.js:

config.entities = false;

not sure if this will have any impact on other areas, but it at least fixed this issue.

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 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');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...