ryan

Hanna Code

Recommended Posts

On 24/06/2016 at 1:08 PM, Robin S said:

I'd be keen to hear if there is a better way to get pages into a PageArray while maintaining a given order of page IDs.

Maybe $pages->getById() is the way to go.

$my_pages = $pages->getById([1086,1021,1053,1018]);

 

Share this post


Link to post
Share on other sites

It's occurred to me that adding to this existing thread might have been the better option for seeking a solution to my problem.

I've already created a new thread so I wonder if it's ok to post a link to it here in case anyone who might know the answer will be more likely to see it here...

 

 

Share this post


Link to post
Share on other sites
1 hour ago, spacemonkey95 said:

It's occurred to me that adding to this existing thread might have been the better option for seeking a solution to my problem.

I think there might be still better places to ask. :)

Table is a Pro field with it's own dedicated support sub-forum.

And the feature you are describing is not a feature of Hanna Code but rather a feature of the Hanna Code Helper module.

  • Like 1

Share this post


Link to post
Share on other sites

Hi all,

I'm struggling with a problem which is more a PHP issue than one of Hanna Code.

<?php
?>
<audio controls>
	<source src='<?= $audiofile?>' type='audio/mp3'> 
</audio>

This little HC  works fine when used in a textarea/CKEditor field like this:

[[audio file="/site/assets/files/1234/foo.mp3"]]

Now I wanted to make it flexible and enable the editor user to insert the path to any mp3 file (stored on some page in a field "mp3" of type File, allowed file extension mp3). 

In the HC Attributes I set a default value for $file, defining   file=LINK . Now the editor, inserting the HC using the HannaCodeHelper Module, gets

[[audio file="LINK"]]

The aimed workflow for the editor user was: Double click on LINK to mark it and using the Link button of the CKEditor to choose the wanted file from the wanted page. Obviously, the value created by CKE had to undergo some treatment.

Of course it's a link from which I had to extract the value of the href attribute (here  /site/assets/files/1122/bar.mp3) , but because of the double quotes from   [[audio file="LINK"]]  it would become

"<a href="/site/assets/files/1234/foo.mp3">"

where the second  "  would terminate the string. I tried string functions str_replace(), strstr() etc. but to no avail.
Perhaps I could have used Javascript, but I wanted to find a PHP solution.

Could anyone help on that?

 

Share this post


Link to post
Share on other sites

@ottogal

An easy solution would be to change...

[[audio file="LINK"]]

...to...

[[audio file='LINK']]

If you want Hanna Code Helper to insert single quotes around attributes I think you'll have to modify the module code. Change line 124 to:

$attrs .= " $attrName='$attrValue'";

You can use SimpleXML in your Hanna Code to get the href from the link:

$a = new SimpleXMLElement($file);
$path = $a['href']->__toString();

 

  • Like 1

Share this post


Link to post
Share on other sites

@Robin S

15 hours ago, Robin S said:

If you want Hanna Code Helper to insert single quotes around attributes I think you'll have to modify the module code. Change line 124 to:


$attrs .= " $attrName='$attrValue'";

Good find, thank you!

After this change even my simple use of the function strstr() works -  to crop the string on both ends, setting free the href attribute value:

<?php
$f = (string) $file;
$f = strstr($f,'/site');
$audiofile = strstr($f,'">',true);
?>
<audio controls>
	<source src='<?= $audiofile?>' type='audio/mp3'> 
</audio>

Your second hint to use SimpleXMLElement() of course is a cleaner way to do it:

<?php
$a = new SimpleXMLElement($file);
$audiofile = $a['href']->__toString();
?>
<audio controls>
	<source src='<?= $audiofile?>' type='audio/mp3'> 
</audio>

Didn't know this class before - so again I learnt something new. Thanks a lot again!

Share this post


Link to post
Share on other sites

Good day.
I really liked the Hana Code Insert plugin. But I was faced with the following problem. In WordPress platform there are 5 roles: Administrator, Editor, Author, Contributor, Subscriber.
I want only the Administrator could work with this plugin.
How to limit access to this plugin for role Contributor ?
Sorry, for my bad English.

Share this post


Link to post
Share on other sites
1 minute ago, Sergey Voronov said:

Good day.
I really liked the Hana Code Insert plugin. But I was faced with the following problem. In WordPress platform there are 5 roles: Administrator, Editor, Author, Contributor, Subscriber.
I want only the Administrator could work with this plugin.
How to limit access to this plugin for role Contributor ?
Sorry, for my bad English.

Check out the hanna specific permissions and only assign them to the contributor role.

Screen Shot 2016-11-03 at 2.36.16 PM.png

Share this post


Link to post
Share on other sites
4 minutes ago, Sergey Voronov said:

If I understand correctly, you need to edit the code in the plugin ?

No - just go to your PW Access > Roles menu and assign the relevant hanna permissions to the appropriate roles.

I just re-read your question and see that you actually only want the codes editable  by the administrator role. By this do you mean the PW superuser role? By default, only the superuser should be able to view/edit hanna codes.

  • Like 1

Share this post


Link to post
Share on other sites
Just now, Sergey Voronov said:

I have installed wordpress version 4.5.3.
Please tell me where I need to go and what to do?
Please explain the steps
Or show a screenshot

I think you're in the wrong place - this is the support forum for ProcessWire, not Wordpress!

ProcessWire also has a hanna code plugin - I think that is your confusion, but since you are here, maybe you should stay :)

 

  • Like 2

Share this post


Link to post
Share on other sites
On 6/24/2016 at 3:08 AM, Robin S said:

I'd be keen to hear if there is a better way to get pages into a PageArray while maintaining a given order of page IDs.

Probably not:

 

Share this post


Link to post
Share on other sites
7 hours ago, szabesz said:
On 24/06/2016 at 1:08 PM, Robin S said:

I'd be keen to hear if there is a better way to get pages into a PageArray while maintaining a given order of page IDs.

Probably not:

I answered my own question in the next post:

On 26/06/2016 at 8:09 PM, Robin S said:

Maybe $pages->getById() is the way to go.


$my_pages = $pages->getById([1086,1021,1053,1018]);

The situation @Wanze replied to is a little different - not an order of page IDs but an order of values to match a field against.

  • Like 1

Share this post


Link to post
Share on other sites

I like this module, I used similar plugin in Wordpress before I switched to PW, so I was happy to find it.

Regarding the code editor, a helper module would be very useful which could save and reload the scrolling and cursor position when saving the code, so I could continue the editing where I left it.
I'm not sure where, but I found something similar, but I don!t remember exactly. I tried to search in Google again and in this forum also, but no success. Maybe it was a different editor ...

Can anyone suggest a solution?
Thanks!

Share this post


Link to post
Share on other sites
1 minute ago, Battman said:

Regarding the code editor, a helper module would be very useful which could save and reload the scrolling and cursor position when saving the code, so I could continue the editing where I left it.
I'm not sure where, but I found something similar, but I don!t remember exactly. I tried to search in Google again and in this forum also, but no success. Maybe it was a different editor ...

I use that technique in the Console Panel of the TracyDebugger module - it's pretty easy to implement by storing the current position in LocalStorage or cookie. Perhaps you could send Ryan a PR with the added functionality?

Share this post


Link to post
Share on other sites
3 hours ago, adrian said:

I use that technique in the Console Panel of the TracyDebugger module - it's pretty easy to implement by storing the current position in LocalStorage or cookie.

I checked TracyDebugger and I like it, thanks for the suggestion!
As I see, it uses Ace editor also, so your solution can be implemented in the Hanna code modul too. Can you give me more details, how you did that?

Share this post


Link to post
Share on other sites
5 minutes ago, Battman said:

I checked TracyDebugger and I like it, thanks for the suggestion!
As I see, it uses Ace editor also, so your solution can be implemented in the Hanna code modul too. Can you give me more details, how you did that?

Save position:

https://github.com/adrianbj/TracyDebugger/blob/865a669a3ddfc0e528413452235e8aefe50e332e/ConsolePanel.inc#L95-L107

Restore position:

https://github.com/adrianbj/TracyDebugger/blob/865a669a3ddfc0e528413452235e8aefe50e332e/ConsolePanel.inc#L540-L545

Share this post


Link to post
Share on other sites
44 minutes ago, adrian said:

Thanks! I dig into Hanna code modul to see, how difficult would be to implement this storage ...

  • Like 1

Share this post


Link to post
Share on other sites

Hi all,

distracted for a while by other (bigger) problems, I now came back to the situation discussed here in this thread in october:

On 27.10.2016 at 3:01 PM, ottogal said:

@Robin S

Good find, thank you!

After this change even my simple use of the function strstr() works -  to crop the string on both ends, setting free the href attribute value:


<?php
$f = (string) $file;
$f = strstr($f,'/site');
$audiofile = strstr($f,'">',true);
?>
<audio controls>
	<source src='<?= $audiofile?>' type='audio/mp3'> 
</audio>

Your second hint to use SimpleXMLElement() of course is a cleaner way to do it:


<?php
$a = new SimpleXMLElement($file);
$audiofile = $a['href']->__toString();
?>
<audio controls>
	<source src='<?= $audiofile?>' type='audio/mp3'> 
</audio>

 

For my Hanna Code call    [[mp3 audio='LINK']]    now I have this Hanna Code (mp3.php):  (and all works fine - :) )

<?php
$a = new SimpleXMLElement($audio);
$pagelink = $a['href']->__toString();
$pagename = basename($pagelink);
$ap = $pages->get("template=audio,parent=audiopool,name=$pagename");
$link = $ap->mp3->url;
?>
	<div class='block'>
		<audio  controls width='400'>
			<source src='<?= $link ?>' type='audio/mp3'> 
		</audio>
	</div>
	<p><?= $pagename ?></p>

But when I open the Hanna Code in the editor and click the button "Save & Test", I get the following messages:

Quote

Warning: SimpleXMLElement::__construct() [simplexmlelement.--construct]: Entity: line 1: parser error : Start tag expected, '<' not found in ....../site/assets/cache/HannaCode/mp3.php on line 4

Warning: SimpleXMLElement::__construct() [simplexmlelement.--construct]: LINK in ....../site/assets/cache/HannaCode/mp3.php on line 4

Warning: SimpleXMLElement::__construct() [simplexmlelement.--construct]: ^ in ....../site/assets/cache/HannaCode/mp3.php on line 4


ProcessWire: ProcessHannaCode: String could not be parsed as XML
......

The line number refers to the file  ....../site/assets/cache/HannaCode/mp3.php where  the line

Quote

if(!defined("PROCESSWIRE")) die("no direct access");

and a blank line are prepended - so  the line in question is, of course: 

Quote

$a = new SimpleXMLElement($audio);

What is wrong with the code, and how can I get rid of these Warnings?

Thankful for some clarification:

ottogal

Share this post


Link to post
Share on other sites
1 hour ago, ottogal said:

But when I open the Hanna Code in the editor and click the button "Save & Test", I get the following messages:

I think that's because when you use your Hanna tag in CKEditor your audio attribute is (or should be) valid link markup, e.g. <a href="/some/url/">LINK</a>

But in the Hanna Code test tab the attribute is not a valid link but simply the string "LINK" which cannot be parsed by SimpleXML. So probably nothing to worry about, but if the error message is a concern you can do some simple check to see if the attribute looks like it will be a link. For example, at the top of your Hanna code:

if(substr($audio, 0, 2) !== '<a') return;

 

  • Like 1

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 BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • 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://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 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 BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)