Jump to content
ryan

Hanna Code

Recommended Posts

i tried using the shortcode module, and it is promising, and quite different than hanna codes; shortcodes allow you to have an opening and closing tag so you can enclose things within, which allows you to use them for things like tabs and accordions;

hanna code is very usable/flexible, but it doesn't know about things between each instance of itself (no opening/closing)...

also the shortcodes module doesn't allow for using more than 1 shortcode on a page.. i think it needs more work;

but it would be good if we could have a shortcodes module that works as well as the wordpress shortcodes, since there are still some rare use cases where shortcodes can be useful...

custom fields replaces and is superior for the most part to the concept of shortcodes, which is probably why the need has not come up much on PW.

And end users always mess up with shortcodes, like putting them in the wrong place in the RTE (like inside a heading), or forgetting to use the closing tag, and consequently break the layout on pages too easily...

  • Like 1

Share this post


Link to post
Share on other sites

I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

  • Like 1

Share this post


Link to post
Share on other sites

I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

Actuall in my testing phase of PW - there are much less usecases for such little snippets because you could use simple a extra field or do prefered PHP direkt in the page template....but in other systems you only had some blocks or one Wysiwyg per pages and such snippets catch up some content or bring some logic to a wysiwyg the user doesn't have to think about it.

For example you could easy setup some Hanna codes and implement it fast via import on new different websites....reusable codesnippets are the usecase.

Iportant question if i wanna make them work in the template i have to call the process i think??

Next HannaCode from my testings is a simple sitemap:

//:Sitemap: creates a simple sitemap (Snippet find in the forum from soma)
//:Use: [[sitemap]]

Just import this one:

!HannaCode:sitemap:eyJuYW1lIjoic2l0ZW1hcCIsInR5cGUiOiIyIiwiY29kZSI6Ijw/cGhwXHJcblxyXG5cclxuZnVuY3Rpb24gc2l0ZU1hcCgkcGFnZSwgJG91dHB1dD0nJykge1xyXG4gICAgJG91dHB1dCAuPSBcIlxcblxcdDxsaT48YSBocmVmPSd7JHBhZ2UtPnVybH0nPnskcGFnZS0+dGl0bGV9PFwvYT5cIjtcclxuICAgIGlmKCRwYWdlLT5udW1DaGlsZHJlbikge1xyXG4gICAgICAgICRvdXRwdXQgLj0gXCJcXG5cXHRcXHQ8dWw+XCI7XHJcbiAgICAgICAgZm9yZWFjaCgkcGFnZS0+Y2hpbGRyZW4gYXMgJGNoaWxkKSAkb3V0cHV0IC49IHN0cl9yZXBsYWNlKFwiXFxuXCIsIFwiXFxuXFx0XFx0XCIsIHNpdGVNYXAoJGNoaWxkKSk7XHJcbiAgICAgICAgJG91dHB1dCAuPSBcIlxcblxcdFxcdDxcL3VsPlwiO1xyXG4gICAgfVxyXG4gICAgJG91dHB1dCAuPSBcIlxcblxcdDxcL2xpPlwiO1xyXG4gICAgcmV0dXJuICRvdXRwdXQ7XHJcbn1cclxuXHJcbiRob21lcGFnZSA9ICRwYWdlcy0+Z2V0KFwiXC9cIik7XHJcbiRzaXRlTWFwID0gc2l0ZU1hcCgkaG9tZXBhZ2UpO1xyXG5lY2hvIFwiPHVsPlwiLiRzaXRlTWFwLlwiPFwvdWw+XCI7In0=/!HannaCode

Have Fun - mr-fan

  • Like 2

Share this post


Link to post
Share on other sites
I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

 Exactly my thought. And loaded/configurable per template, so that only hanna codes are shown that makes sence in that template. 

  • Like 1

Share this post


Link to post
Share on other sites

Hi all

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

Screenshot%202014-06-16%2014.08.42.png

One of the hosts has the following specs:

PHP: 5.3.28

MySQL: 5.5.37

Does anyone have a clue what might cause this error?

Share this post


Link to post
Share on other sites

For some reason I cannot get hanna code to work with php. I can get html to work just pine but php will not.

Here is my code

<?php
 
foreach($page->children as $product) {
 
    if($product->image) {
       // $image = $product->image->width(150);
        $img = "<img src='{$image->url}' alt='{$product->title}' class='flt-left-img' />";
    } 
    
    else {
     
        $img = "<span class='image_placeholder'>Image not available</span>";
    } 
 
    echo "
        $img
        <h3>{$product->title}</h3>
        <p>{$product->product_description}</p>
        <hr />
        ";
}
?>
 
 
 
The only thing that will output on the page is the product description but all other content from the body disappears.
 
Driving me nuts so any help would be great.

Share this post


Link to post
Share on other sites

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

One of the hosts has the following specs:

PHP: 5.3.28

MySQL: 5.5.37

Does anyone have a clue what might cause this error?

Is this still a problem? Does anything else work, i.e. is this the only place that's broken on this site?

Sounds like your database wasn't reachable at this point, but I'd imagine that causing issues elsewhere too. Unless, perhaps, it's somehow related to PHP's mysqli extension on that server (just about all core features have already been migrated to PDO instead).

For some reason I cannot get hanna code to work with php. I can get html to work just pine but php will not.

Here is my code

<?php
 
foreach($page->children as $product) {
 
    if($product->image) {
       // $image = $product->image->width(150);
        $img = "<img src='{$image->url}' alt='{$product->title}' class='flt-left-img' />";
    } 
    
    else {
     
        $img = "<span class='image_placeholder'>Image not available</span>";
    } 
 
    echo "
        $img
        <h3>{$product->title}</h3>
        <p>{$product->product_description}</p>
        <hr />
        ";
}
?>
 
 
 
The only thing that will output on the page is the product description but all other content from the body disappears.

Only weird thing I can spot in your code right away is that you've got $image = ... commented out, yet on the next line you try to use $image->url, which obviously won't be available here. I'm assuming that this was just something you did for testing and forgot there.

When you're saying that only output is the product description, it's coming from this Hanna Code snippet, right? Are you seeing empty <h3></h3> tags and then <p></p> tags with product description inside them and nothing else, or..?

I'm not really sure what you're referring to when you say that all other content from the "body" disappears; <body> element of your page, $page->body, or something entirely different? If you view the source of the page, is there anything weird there -- or in your log files, either in site/assets/logs/errors.txt or Apache logs?

Share this post


Link to post
Share on other sites

oops I didn't mean to have that commented out. Its not in my code, but that was a copy that I forgot to uncomment. 

I am not seeing empty <h3> tags or <p> tags and yes the product description is coming from the hanna code. In fact the only thing that showing on the page is the product description from the hanna code. Everything else disappears including all paragraphs and everything else in the textarea $page->body. There is nothing weird in the source. It has to be the way this php is whitten I think because I am using other php for another hanna code and it works.  

this is the other code that works

<?php foreach ($page->children() as $c): ?>

<li><a href="<?=$c->url;?>"><img src="<?=$c->listImage->url;?>" alt="<?=$c->listImage->description;?>" width="100" height="100"> <?=$c->listImage->description;?> <span>View More</span></a></li>
<? endforeach; ?>

Share this post


Link to post
Share on other sites

Is this still a problem? Does anything else work, i.e. is this the only place that's broken on this site?

Sounds like your database wasn't reachable at this point, but I'd imagine that causing issues elsewhere too. Unless, perhaps, it's somehow related to PHP's mysqli extension on that server (just about all core features have already been migrated to PDO instead).

Yeah it's still a problem. :-(

And now I've tried it on another host with same result. The only two places I've succesfully gotten the Hanna Code module to work were on localhost (yay) and on my Digital Ocean Droplet...

I guess I'll let the owner of the site know, that he can't get that module on the two host masters he wished for. :-)

Share this post


Link to post
Share on other sites

First problem I noticed, two people are asking two separate questions at the same time.

For @kasperwf,

 Hi all

 

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

  One of the hosts has the following specs:

 

PHP: 5.3.28

MySQL: 5.5.37

 

Does anyone have a clue what might cause this error?

 

On your localhost (that is working), what are the following:

ProcessWire version

PHP version

MySQL version

Apache version

Then, what are the same information for both hosts that you have have tried?  Having that information, will allow someone to truly be of help to you.  Thanks.

Share this post


Link to post
Share on other sites

On your localhost (that is working), what are the following:

ProcessWire version

PHP version

MySQL version

Apache version

Then, what are the same information for both hosts that you have have tried?  Having that information, will allow someone to truly be of help to you.  Thanks.

My localhost:

PHP version: 5.4.22

MySQL version: 5.6.10

Apache: Apache/2.2.26 (Unix)

The information for the hosts that doesn't work is the one I wrote earlier. Seems like they both use the exact same setup (as the other, not like mine, the working server). :-I

The info for my VPS that also work is:

PHP: 5.5.9-1ubuntu4

MySQL: I really don't know, because I obviously secured it too well, and I can't even mysql -v it. But it was last month, and it was the newest version, so, yeah. :-)

Apache: Apache/2.4.7 (Ubuntu)

Share this post


Link to post
Share on other sites

This turned out to be an issue with the order of variables returned by core TemplateFile::getArray. It was doing an array_merge which gave preference to API variables, preventing them from being overwritten. Maybe that's a good thing in general, but I don't think we want that limitation. I went ahead and changed it in dev. Now it gives preference to local variables, which enables Hanna Code to provide the behavior it was supposed to. 

Hello,

I fail to make it work. I'm using PW version 2.4.4. TemplateFile.php lines 156-158 are correctly updated:

	public function getArray() {
		return array_merge($this->fuel->getArray(), parent::getArray()); 
	}

My Hanna code is as simple as:

[[page-title]] :

<?php
echo $page->title;

The structure is as follows:

Page texts, with title "Texts" -> Field "Text 1" (Textareas ProField)-> "Some text... " . [[page-title]]

Page product name, with title "Product name"-> API reference to Field "Text 1"

Outputs "Some text... Texts"

Should be "Some text... Product name"

I think it should work, but can´t see the problem. The textareas field has Hanna Code Text Formatter applied.

Thanks,  :rolleyes:

Share this post


Link to post
Share on other sites

I think I am getting caught out by scope - well, I know I am.

I have some text on a page other than the one I am looking at, and I am drawing it in with get()

That text has a hanna code in it that simply echos the page title.

The problem is that it is echoing the page title of the page the code originates from and not from the page I am looking at.

How do I do this so that it gets my current page title, not the page where the text originates from?

Share this post


Link to post
Share on other sites

ummm ... I am halfway there.

by using this for the php for my hanna code <?php echo wire("page")->title; ?> I now get the current page title.

However, I am not getting the rest of the text.

So:

This is my [[pagetitle]] you can see

Is just printing out the page title, not the rest of the words.

Share this post


Link to post
Share on other sites

You don't happend to replace sorounding p tags and the hanna code is inside the text paragraph?

Share this post


Link to post
Share on other sites

Hi Soma, no, I have the replace bit turned off.

I think it is because the textarea that supplies the text, complete with the hanna code reference, is originating on another page.

I am calling it into my template with:

<? echo $pages->get("/servicing/")->service_model_default_text; ?>

Now, if I use a different code, one that pulls the info from a specified field in a specified page, that works fine.

For instance, a code that is:

echo "<span class='phonenumber'>Call {$pages->get("/settings/")->site_phone}</span>";

But if I try and call something from the current page, it goes wrong.

So if I used the code:

echo $page->title;

Simply prints out title of the page where the text originated, but not the rest of the text. if I use wire() it prints out the current page title, but again no text. Debug is not showing errors.

Share this post


Link to post
Share on other sites

Sorry can't really follow what you're doing. Mostly confused why you'd need hanna code at all just for a page title?

Share this post


Link to post
Share on other sites

Basically I have a huge lump of default text in a separate page that is pulled into about 100 pages or so.

The default text needs to pick up values from those pages - product name, price and so on - that will be part of that long default text. The page title is just one of those values.

The easiest way I could see to do it (and easy for the client to understand) was to use bits of hanna code within the text.

Share this post


Link to post
Share on other sites

I have hard time following what code is where and what doesn't work.

Share this post


Link to post
Share on other sites

Sorry, Soma, I should have explained it better.

I have a page called services that has a CKEditor field called service_model_default_text

It contains, for instance, "we can service your [[model-name]]"

The code for the [[model-name]] hanna code is 

<?php echo wire("page")->title; ?>

I have the replace surrounding tag set to "no" and it is type PHP

I have another page called Audi. In the template for that page I get the field from the services page.

<?php echo $pages->get("/servicing/")->service_model_default_text; ?>

The idea is that the hanna code is replace with the page title from the audi page so that the final result is:

We can service your Audi.

Unfortunately, the hanna code system does not seem to be able to do that, it prints out the page title fine, but not the rest of the text from the field.

However, if I change the hanna code to another one I have, [[phonenumber]], which takes its input from a field on a completely separate page, it works fine.

Confused!

Share this post


Link to post
Share on other sites

I tested something like this in latest dev and 2.4 installation, works fine. I can't see any text not outputting.

Default site. Added hanna code formatter to body field. In /templates/ page in the body I place a hanna code inside text [[model-name]] and output that text on the About page. 

Hanna code 

<?php
echo wire("page")->title;

In template basic-page.php

echo $pages->get("/templates/")->body;

The hanna tag gets replaced with the page title and the surrounding text is still there.

Share this post


Link to post
Share on other sites

Damn!

I wonder what I have got that is messing it up?

I think I will strip the entire template out apart from the get line and see what happens

Share this post


Link to post
Share on other sites

Do those two pages, the one you have the body field and the about page, use the same template?

I just emptied the template file, but it still is not working properly.

I noticed that when I save and test the hanna code, inside the dotted box it just says Hanna Code

No idea why.

Share this post


Link to post
Share on other sites

Yes those two pages have same template. It doesn't matter what template. I've never used the save and test. But I think you would see the current admin page title if anything at all.

Share this post


Link to post
Share on other sites

hmm ... so something is not right. 

With the other hanna code, the one that points to a telephone number, in test it shows the telephone number.

I have tried deleting the hanna code instance, and adding a new one and it is the same problem.

The only other thing is that they are on different tree levels - the page that has the text in it is a child of home, the other page, the Audi page, is its grandchild. But I dont think that should be a problem.

I am a bit lost on this, to be honest, and it has brought the project to a shuddering halt

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 horst
      ---------------------------------------------------------------------------------------------------------------------------------
        when working with PW version 2.6+, please use Pim2, not Pim!
        read more here  on how to change from the older to the newer version in existing sites
      ---------------------------------------------------------------------------------------------------------------------------------
      PageImage Manipulator, API for version 1 & 2

      The Page Image Manipulator is a module that let you in a first place do ImageManipulations with your PageImages. - And in a second place there is the possibility to let it work on any imagefile that exists in your servers filesystem, regardless if it is a 'known PW-image'.

      The Page Image Manipulator is a Toolbox for Users and Moduledevelopers. It is written to be as close to the Core ImageSizer as possible. Besides the GD-filterfunctions it contains resize, crop, canvas, rotate, flip, sharpen, unsharpMask and 3 watermark methods.



      How does it work?

      You can enter the ImageManipulator by calling the method pim2Load(). After that you can chain together how many actions in what ever order you like. If your manipulation is finished, you call pimSave() to write the memory Image into a diskfile. pimSave() returns the PageImage-Object of the new written file so we are able to further use any known PW-image property or method. This way it integrates best into the ProcessWire flow.

      The three examples above put out the same visual result: a grayscale image with a width of 240px. Only the filenames will slightly differ.

      You have to define a name-prefix that you pass with the pimLoad() method. If the file with that prefix already exists, all operations are skipped and only the desired PageImage-Object gets returned by pimSave(). If you want to force recreation of the file, you can pass as second param a boolean true: pim2Load('myPrefix', true).

      You may also want to get rid of all variations at once? Than you can call $pageimage->pim2Load('myPrefix')->removePimVariations()!

      A complete list of all methods and actions are at the end of this post.
       
      You may also visit the post with tips & examples for users and module developers.


      How to Install
      Download the module Place the module files in /site/modules/PageImageManipulator/ In your admin, click Modules > Check for new modules Click "install" for PageImageManipulator Done! There are no configuration settings needed, just install and use it. Download    (version 0.2.0)
      get it from the Modules Directory History of origins

      http://processwire.com/talk/topic/3278-core-imagemanipulation/


      ----------------------------------------------------------------------------------------------------------


      Page Image Manipulator - Methods

      * pimLoad  or  pim2Load, depends on the version you use!

      pimLoad($prefix, $param2=optional, $param3=optional)
      param 1: $prefix - (string) = mandatory! param 2: mixed, $forceRecreation or $options param 3: mixed, $forceRecreation or $options return: pim - (class handle) $options - (array) default is empty, see the next method for a list of valid options! $forceRecreation - (bool) default is false It check if the desired image variation exists, if not or if forceRecreation is set to true, it prepares all settings to get ready for image manipulation
      -------------------------------------------------------------------

      * setOptions

      setOptions(array $options)
      param: $options - (array) default is empty return: pim - (class handle) Takes an array with any number valid options / properties and set them by replacing the class-defaults and / or the global config defaults optionally set in the site/config.php under imageSizerOptions or imageManipulatorOptions.

      valid options are:
      quality = 1 - 100 (integer) upscaling = true | false (boolean) cropping = true | false (boolean) autoRotation =true | false (boolean) sharpening = 'none' | 'soft' | 'medium' | 'strong' (string) bgcolor = (array) css rgb or css rgba, first three values are integer 0-255 and optional 4 value is float 0-1, - default is array(255,255,255,0) thumbnailColorizeCustom = (array) rgb with values for colorize, integer -255 - 255 (this can be used to set a custom color when working together with Thumbnails-Module)
        outputFormat = 'gif' | 'jpg' | 'png' (Attention: outputFormat cannot be specified as global option in $config->imageManipulatorOptions!) set {singleOption} ($value)
      For every valid option there is also a single method that you can call, like setQuality(90), setUpscaling(false), etc.
      -------------------------------------------------------------------

      * pimSave

      pimSave()
      return: PageImage-Object If a new image is hold in memory, it saves the current content into a diskfile, according to the settings of filename, imagetype, targetFilename and outputFormat. Returns a PageImage-Object!
      -------------------------------------------------------------------

      * release

      release()
      return: void (nothing) if you, for what ever reason, first load image into memory but than do not save it, you should call release() to do the dishes! 😉 If you use pimSave() to leave the ImageManipulator, release() is called automatically.
      -------------------------------------------------------------------

      * getOptions

      getOptions()
      return: associative array with all final option values example:
      ["autoRotation"] bool(true) ["upscaling"] bool(false) ["cropping"] bool(true) ["quality"] int(90) ["sharpening"] string(6) "medium" ["targetFilename"] string(96) "/htdocs/site/assets/files/1124/pim_prefix_filename.jpg" ["outputFormat"] string(3) "jpg" get {singleOption} ()
      For every valid option there is also a single method that you can call, like getQuality(), getUpscaling(), etc. See method setOptions for a list of valid options!
      -------------------------------------------------------------------

      * getImageInfo

      getImageInfo()
      return: associative array with useful informations of source imagefile example:
      ["type"] string(3) "jpg" ["imageType"] int(2) ["mimetype"] string(10) "image/jpeg" ["width"] int(500) ["height"] int(331) ["landscape"] bool(true) ["ratio"] float(1.5105740181269) ["bits"] int(8) ["channels"] int(3) ["colspace"] string(9) "DeviceRGB" -------------------------------------------------------------------

      * getPimVariations

      getPimVariations()
      return: array of Pageimages Collect all pimVariations of this Pageimage as a Pageimages array of Pageimage objects. All variations created by the core ImageSizer are not included in the collection.
      -------------------------------------------------------------------

      * removePimVariations

      removePimVariations()
      return: pim - (class handle) Removes all image variations that was created using the PIM, all variations that are created by the core ImageSizer are left untouched!
      -------------------------------------------------------------------
      * width

      width($dst_width, $sharpen_mode=null)
      param: $dst_width - (integer) param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you prioritize the width, like with pageimage. Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * height

      height($dst_height, $sharpen_mode=null)
      param: $dst_height - (integer) param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you prioritize the height, like with pageimage. Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * resize

      resize($dst_width=0, $dst_height=0, $sharpen_mode=null)
      param: $dst_width - (integer) default is 0 param: $dst_height - (integer) default is 0 param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you have to set width and / or height, like with pageimage size(). Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * stepResize

      stepResize($dst_width=0, $dst_height=0)
      param: $dst_width - (integer) default is 0 param: $dst_height - (integer) default is 0 return: pim - (class handle) this performs a resizing but with multiple little steps, each step followed by a soft sharpening. That way you can get better result of sharpened images.
      -------------------------------------------------------------------

      * sharpen

      sharpen($mode='soft')
      param: $mode - (string) possible values 'none' | 'soft'| 'medium'| 'strong' return: pim - (class handle) Applys sharpening to the current memory image. You can call it with one of the three predefined pattern, or you can pass an array with your own pattern.
      -------------------------------------------------------------------

      * unsharpMask

      unsharpMask($amount, $radius, $threshold)
      param: $amount - (integer) 0 - 500, default is 100 param: $radius - (float) 0.1 - 50, default is 0.5 param: $threshold - (integer) 0 - 255, default is 3 return: pim - (class handle) Applys sharpening to the current memory image like the equal named filter in photoshop.
      Credit for the used unsharp mask algorithm goes to Torstein Hønsi who has created the function back in 2003.
      -------------------------------------------------------------------

      * smooth

      smooth($level=127)
      param: $level - (integer) 1 - 255, default is 127 return: pim - (class handle) Smooth is the opposite of sharpen. You can define how strong it should be applied, 1 is low and 255 is strong.
      -------------------------------------------------------------------

      * blur

      blur()
      return: pim - (class handle) Blur is like smooth, but cannot called with a value. It seems to be similar like a result of smooth with a value greater than 200.
      -------------------------------------------------------------------

      * crop

      crop($pos_x, $pos_y, $width, $height)
      param: $pos_x - (integer) start position left param: $pos_y - (integer) start position top param: $width - (integer) horizontal length of desired image part param: $height - (integer) vertical length of desired image part return: pim - (class handle) This method cut out a part of the memory image.
      -------------------------------------------------------------------

      * canvas

      canvas($width, $height, $bgcolor, $position, $padding)
      param: $width = mixed, associative array with options or integer, - mandatory! param: $height = integer, - mandatory if $width is integer! param: $bgcolor = array with rgb or rgba, - default is array(255, 255, 255, 0) param: $position = one out of north, northwest, center, etc, - default is center param: $padding = integer as percent of canvas length, - default is 0 return: pim - (class handle) This method creates a canvas according to the given width and height and position the memory image onto it.
      You can pass an associative options array as the first and only param. With it you have to set width and height and optionally any other valid param. Or you have to set at least width and height as integers.
      Hint: If you want use transparency with rgba and your sourceImage isn't of type PNG, you have to define 'png' as outputFormat with your initially options array or, for example, like this: $image->pimLoad('prefix')->setOutputFormat('png')->canvas(300, 300, array(210,233,238,0.5), 'c', 5)->pimSave()
      -------------------------------------------------------------------

      * flip

      flip($vertical=false)
      param: $vertical - (boolean) default is false return: pim - (class handle) This flips the image horizontal by default. (mirroring)
      If the boolean param is set to true, it flips the image vertical instead.
      -------------------------------------------------------------------

      * rotate

      rotate($degree, $backgroundColor=127)
      param: $degree - (integer) valid is -360 0 360 param: $backgroundColor - (integer) valid is 0 - 255, default is 127 return: pim - (class handle) This rotates the image. Positive values for degree rotates clockwise, negative values counter clockwise. If you use other values than 90, 180, 270, the additional space gets filled with the defined background color.
      -------------------------------------------------------------------

      * brightness

      brightness($level)
      param: $level - (integer) -255 0 255 return: pim - (class handle) You can adjust brightness by defining a value between -255 and +255. Zero lets it unchanged, negative values results in darker images and positive values in lighter images.
      -------------------------------------------------------------------

      * contrast

      contrast($level)
      param: $level - (integer) -255 0 255 return: pim - (class handle) You can adjust contrast by defining a value between -255 and +255. Zero lets it unchanged, negative values results in lesser contrast and positive values in higher contrast.
      -------------------------------------------------------------------

      * grayscale

      grayscale()
      return: pim - (class handle) Turns an image into grayscale. Remove all colors.
      -------------------------------------------------------------------

      * sepia

      sepia()
      return: pim - (class handle) Turns the memory image into a colorized grayscale image with a predefined rgb-color that is known as "sepia".
      -------------------------------------------------------------------

      * colorize

      colorize($anyColor)
      param: $anyColor - (array) like css rgb or css rgba - but with values for rgb -255 - +255,  - value for alpha is float 0 - 1, 0 = transparent  1 = opaque return: pim - (class handle) Here you can adjust each of the RGB colors and optionally the alpha channel. Zero lets the channel unchanged whereas negative values results in lesser / darker parts of that channel and higher values in stronger saturisation of that channel.
      -------------------------------------------------------------------

      * negate

      negate()
      return: pim - (class handle) Turns an image into a "negative".
      -------------------------------------------------------------------

      * pixelate

      pixelate($blockSize=3)
      param: $blockSize - (integer) 1 - ??, default is 3 return: pim - (class handle) This apply the well known PixelLook to the memory image. It is stronger with higher values for blockSize.
      -------------------------------------------------------------------

      * emboss

      emboss()
      return: pim - (class handle) This apply the emboss effect to the memory image.
      -------------------------------------------------------------------

      * edgedetect

      edgedetect()
      return: pim - (class handle) This apply the edge-detect effect to the memory image.
      -------------------------------------------------------------------

      * getMemoryImage

      getMemoryImage()
      return: memoryimage - (GD-Resource) If you want apply something that isn't available with that class, you simply can check out the current memory image and apply your image - voodoo - stuff
      -------------------------------------------------------------------

      * setMemoryImage

      setMemoryImage($memoryImage)
      param: $memoryImage - (GD-Resource) return: pim - (class handle) If you are ready with your own image stuff, you can check in the memory image for further use with the class.
      -------------------------------------------------------------------

      * watermarkLogo

      watermarkLogo($pngAlphaImage, $position='center', $padding=2)
      param: $pngAlphaImage - mixed [systemfilepath or PageImageObject] to/from a PNG with transparency param: $position - (string) is one out of: N, E, S, W, C, NE, SE, SW, NW,
      - or: north, east, south, west, center, northeast, southeast, southwest, northwest
      default is 'center' param: $padding - (integer) 0 - 25, default is 5, padding to the borders in percent of the images length! return: pim - (class handle) You can pass a transparent image with its filename or as a PageImage to the method. If the watermark is bigger than the destination-image, it gets shrinked to fit into the targetimage. If it is a small watermark image you can define the position of it:
      NW - N - NE | | | W - C - E | | | SW - S - SE  
      The easiest and best way I have discovered to apply a big transparency watermark to an image is as follows:
      create a square transparent png image of e.g. 2000 x 2000 px, place your mark into the center with enough (percent) of space to the borders. You can see an example here! The $pngAlphaImage get centered and shrinked to fit into the memory image. No hassle with what width and / or height should I use?, how many space for the borders?, etc.
      -------------------------------------------------------------------

      * watermarkLogoTiled

      watermarkLogoTiled($pngAlphaImage)
      param: $pngAlphaImage - mixed [systemfilepath or PageImageObject] to/from a PNG with transparency return: pim - (class handle) Here you have to pass a tile png with transparency (e.g. something between 150-300 px?) to your bigger images. It got repeated all over the memory image starting at the top left corner.
      -------------------------------------------------------------------

      * watermarkText

      watermarkText($text, $size=10, $position='center', $padding=2, $opacity=50, $trueTypeFont=null)
      param: $text - (string) the text that you want to display on the image param: $size - (integer) 1 - 100, unit = points, good value seems to be around 10 to 15 param: $position - (string) is one out of: N, E, S, W, C, NE, SE, SW, NW,
      - or: north, east, south, west, center, northeast, southeast, southwest, northwest
      default is 'center' param: $padding - (integer) 0 - 25, default is 2, padding to the borders in percent of the images length! param: $opacity- (integer) 1 - 100, default is 50 param: $trueTypeFont - (string) systemfilepath to a TrueTypeFont, default is freesansbold.ttf (is GPL & comes with the module) return: pim - (class handle) Here you can display (dynamic) text with transparency over the memory image. You have to define your text, and optionally size, position, padding, opacity for it. And if you don't like the default font, freesansbold, you have to point to a TrueTypeFont-File of your choice.
      Please have a look to example output: http://processwire.com/talk/topic/4264-release-page-image-manipulator/page-2#entry41989
      -------------------------------------------------------------------





      PageImage Manipulator - Example Output


    • By d'Hinnisdaël
      Format Datetime fields as Carbon instances.
      You can find the latest release and the complete readme on Github.
      Installation
      composer require daun/datetime-carbon-format Usage
      All Datetime fields will now be formatted as Carbon instances instead of strings. Some examples:
      // $page->date is a Datetime field // Output format: j/n/Y echo $page->date; // 20/10/2020 echo $page->date->add('7 days'); // 27/10/2020 echo $page->date->format('l, F j'); // Monday, October 20 echo $page->date->year; // 2020 echo $page->date->diffForHumans(); // 28 minutes ago Frontend only
      The ProcessWire admin seems to expect datetime fields to be strings. This module will only return Carbon instances on frontend page views.
      Date output format
      When casting a Carbon instance to a string (usually when outputting the field in a template), the field's date output format will be respected.
      Links
      GitHub • Readme • Carbon docs
       
       
      PS. I remember reading about a Carbon module in a recent newsletter, but couldn't find it anywhere. Was that you, @bernhard?
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Warning: This module requires ProcessWire 3.0.167 which is above the current stable master release at the moment.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Attention, please note!
      Nested repeaters cannot be supported technically. Therefore a check is made to prevent this. However, a nested repeater can only be detected if the field name ends for example with "_repeater1234". For example, if your MatrixRepeater field is named like this: "content_repeater" or "content_repeater123", this field is identified as nested and the module does not load. In version 2.0.1 the identification has been changed so that a field ending with the name repeater is only detected as nested if at least a two-digit number sequence follows. But to avoid this problem completely, make sure that your repeater matrix field does NOT end with the name "repeater".
      Changelog
       
      2.0.1
      Bug fix: Thanks to @ngrmm I could discover a bug which causes that the module cannot be loaded if the MatrixRepeater field ends with the name "repeater". The code was adjusted and information about the problem was provided 2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.1)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
×
×
  • Create New...