Jump to content
horst

Pia - Pageimage Assistant

Recommended Posts

I got an error when i tried to crop an image with the new processwire croppingfeature and PIA installed.
 

TemplateFile: Unknown Selector operator: '' -- was your selector value properly escaped? field='1121', value='', selector: '1121'

#0 /Users/jondoe/Documents/localdev/wire/core/Selectors.php(284): Selectors->create('1121', '', '') 
#1 /Users/jondoe/Documents/localdev/wire/core/Selectors.php(81): Selectors->extractString('1121') 
#2 /Users/jondoe/Documents/localdev/site/modules/PageimageAssistant/PageimageAssistant.module(378): Selectors->__construct('1121') 
#3 /Users/jondoe/Documents/localdev/site/modules/PageimageAssistant/PageimageAssistant.module(227): PageimageAssistant::selector2array('1121') 
#4 /Users/jondoe/Documents/localdev/site/modules/PageimageAssistant/PageimageAssistant.module(160): PageimageAssistant->getSizeParams(0, 0, 1121, 'piacrop') 
#5 /Users/jondoe/Documents/localdev/wire/core/Wire.php(388): PageimageAssistant->PiaMakeCrop(Object(HookEvent)) 
#6 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('crop', Array) 
#7 /Users/jondoe/Documents/localdev/wire/modules/Process/ProcessPageEditImageSelect/ProcessPageEditImageSelect.module(914): Wire->__call('crop', Array) 
#8 /Users/jondoe/Documents/localdev/wire/modules/Process/ProcessPageEditImageSelect/ProcessPageEditImageSelect.module(914): Pageimage->crop(1121, 764, 736, 419, Array) 
#9 /Users/jondoe/Documents/localdev/wire/modules/Process/ProcessPageEditImageSelect/ProcessPageEditImageSelect.module(556): ProcessPageEditImageSelect->processCrop() 
#10 [internal function]: ProcessPageEditImageSelect->___executeEdit() 
#11 /Users/jondoe/Documents/localdev/wire/core/Wire.php(366): call_user_func_array(Array, Array) 
#12 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('executeEdit', Array) 
#13 /Users/jondoe/Documents/localdev/wire/core/ProcessController.php(213): Wire->__call('executeEdit', Array) 
#14 /Users/jondoe/Documents/localdev/wire/core/ProcessController.php(213): ProcessPageEditImageSelect->executeEdit() 
#15 [internal function]: ProcessController->___execute() 
#16 /Users/jondoe/Documents/localdev/wire/core/Wire.php(366): call_user_func_array(Array, Array) 
#17 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('execute', Array) 
#18 /Users/jondoe/Documents/localdev/wire/core/admin.php(93): Wire->__call('execute', Array) 
#19 /Users/jondoe/Documents/localdev/wire/core/admin.php(93): ProcessController->execute() 
#20 /Users/jondoe/Documents/localdev/wire/modules/AdminTheme/AdminThemeDefault/controller.php(13): require('/Users/jondoe/D...') 
#21 /Users/jondoe/Documents/localdev/site/templates/admin.php(15): require('/Users/jondoe/D...') 
#22 /Users/jondoe/Documents/localdev/wire/core/TemplateFile.php(169): require('/Users/jondoe/D...') 
#23 [internal function]: TemplateFile->___render() 
#24 /Users/jondoe/Documents/localdev/wire/core/Wire.php(366): call_user_func_array(Array, Array) 
#25 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('render', Array) 
#26 /Users/jondoe/Documents/localdev/wire/modules/PageRender.module(356): Wire->__call('render', Array) 
#27 /Users/jondoe/Documents/localdev/wire/modules/PageRender.module(356): TemplateFile->render() 
#28 [internal function]: PageRender->___renderPage(Object(HookEvent)) 
#29 /Users/jondoe/Documents/localdev/wire/core/Wire.php(366): call_user_func_array(Array, Array) 
#30 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('renderPage', Array) 
#31 /Users/jondoe/Documents/localdev/wire/core/Wire.php(388): Wire->__call('renderPage', Array) 
#32 /Users/jondoe/Documents/localdev/wire/core/Wire.php(388): PageRender->renderPage(Object(HookEvent)) 
#33 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('render', Array) 
#34 /Users/jondoe/Documents/localdev/wire/modules/Process/ProcessPageView.module(172): Wire->__call('render', Array) 
#35 /Users/jondoe/Documents/localdev/wire/modules/Process/ProcessPageView.module(172): Page->render() 
#36 [internal function]: ProcessPageView->___execute(true) 
#37 /Users/jondoe/Documents/localdev/wire/core/Wire.php(366): call_user_func_array(Array, Array) 
#38 /Users/jondoe/Documents/localdev/wire/core/Wire.php(321): Wire->runHooks('execute', Array) 
#39 /Users/jondoe/Documents/localdev/index.php(240): Wire->__call('execute', Array) 
#40 /Users/jondoe/Documents/localdev/index.php(240): ProcessPageView->execute(true) 
#41 {main}

 
This happens when I try to save my cropped selection. (I turned debug on to get the longer error message.)
 
When I uninstall PIA it works without problems.
 
 
I use PW 2.5.22 and PIA 0.2.2

Edited by horst
changed error message from "quote" to "code"

Share this post


Link to post
Share on other sites

Hey Torsten,

What exactly have you done? Can you explain exactly, step by step, so that I can reproduce it?

Edit:

Can you reproduce it? I have installed latest dev from today 2.5.22, but it is a bit different from an earlier 2.5.22 (maybe a week ago) and everything in regard to Pia works fine.

Edited by horst

Share this post


Link to post
Share on other sites

Thanks for the screencast. But that's what I also do and it works here. Only thing that seems other here is I have no german language pack installed.

What are your settings for Pia?

I have tried it with the global ForceNew set to true and to false, both is working here.

So, what makes me completly wonder is why Pia is / should be invoked in your site when editing with the new pageimage field cropping tool. It doesn't make sense. The new image tool don't call Pia, and Pia only should get invoked by explicitly calling her:

        $this->addHook('Pageimage::pia', $this, 'PiaBallerina');
        $this->addHook('Pageimage::crop', $this, 'PiaMakeCrop');
        $this->addHook('Pageimage::cover', $this, 'PiaMakeCover');
        $this->addHook('Pageimage::contain', $this, 'PiaMakeContain');
        $this->addHook('Pageimage::retinafy', $this, 'PiaCreateRetinafy');
        $this->addHook('Pageimage::hiDPI', $this, 'PiaCreateRetinafy');

She only add her own methods to the Pageimage and do not hook into any existing one.

And in my testsite it doesn't get invoked. Why is it with your site? There must be something other that interferes with using the new cropping tool. ???

Share this post


Link to post
Share on other sites

Sorry to confuse you. ;-)

These are my settings for Pia.

post-2000-0-87738100-1426503910_thumb.pn

Just for completeness, here are the other image related modules i use:

  • Images FocusArea
  • Image Extra

What can i do to help you further with this issue?

Share this post


Link to post
Share on other sites

Not imagesizer options but "during development" forceNew setting was of interest, but this also doesn't affect it here.

Have you disabled the other modules too? Can you do it, (maybe in a new test install)?

And then try it one by one. Uninstall all site modules. Then only install Pia and try it. If no other site module is installed, I believe it will work with Pia too. If it does, install the next module to it, e.g. ImageExtra. If it works together, install the next one, etc. (Do this also for other modules, e.g. SEO or other you may have installed yet.)

Share this post


Link to post
Share on other sites

Updated Pia to version 0.3.0

Resolved a naming conflict with Pias crop() method: around PW version 2.5.17 there was a new pageimage::crop method introduced.

If you use Pia with a recent PW dev version, please update!

  • Like 1

Share this post


Link to post
Share on other sites

Hi horst, thank you for this great plugin.

I can’t install it on my new Processwire website. When I come to activate the plugin, I get the following error:

Class PageimageAssistant contains 1 abstract method and must therefore be declared abstract or implement the remaining methods
(Module::getModuleInfo) in /…/site/modules/PageimageAssistant/PageimageAssistant.module on line 738

Any idea?

Share this post


Link to post
Share on other sites

Do you have copied all files completely to the modules directory?

Which version of PW and PHP do you use?

Share this post


Link to post
Share on other sites

Horst > I try both to upload manually and from the module installer. The error happens when I check for new module or when I proceed to installation.

My php version is 5.6.10. I noticed that the error exists on my distant server as well. It blocks the access to the module page until I manually remove PIA.

Edit: and ProcessWire 2.4.0

Share this post


Link to post
Share on other sites

PIA is only compatible with PW 2.5 and 2.6!
 
in Github repo, the subheader at top:  Module for ProcessWire 2.5.0+

and in the modules directory it has the appropriate checkboxes checked.

When trying to direct install via PW 2.4, you have it on the install screen:

post-1041-0-79815000-1434215010_thumb.pn

So, with PW 2.5+ you will see more bold information when versions are mismatch, or "thumbs up icon" if they match fine. But at least, also with PW 2.4 all needed informations are on the right place(s). :)

One more reason to update your PW version, we are on 2.6 stable for some weeks now ;-)

Share this post


Link to post
Share on other sites

Oh, sorry for that and thank you for your time! You made me realize that I was a bit late in term of PW versions. I have a fresh one now, thanks again.

  • Like 1

Share this post


Link to post
Share on other sites

Successfully tested PIA with PW 3.0 and set the version to 1.0.0 stable now.

  • Like 5

Share this post


Link to post
Share on other sites

Quick question: Looking at module setttings for this 1.0.0 version in a new PW 3.0 setup there are only HiDPI/Retinafy Options. I don't see any image Sizer Options, as shown a few posts back. Is this normal? Are they somewhere else? Thanks.

Share this post


Link to post
Share on other sites

@SteveB: Sorry, I need to update this in the description here. The UI for Imagesizer options is removed now, as it could interfere with the ConfigModule. I think it is better to have only one SettingsPage / UI screen than multiple, what can let to confusion.
 
Pia is meant to assist in Image API handling, and the ConfigModule is meant for UI handling of config options.
 
So, the UI for Image Sizer Options isn't there anymore, for all PW versions, 2.5+ and 3.0+.

Edited by horst

Share this post


Link to post
Share on other sites

Hey @horst - the IMagick Image Sizer module uses a default "Quality" setting of 80. When using the "quality" option in PIA (or native PW $image methods), does it override the IMagick Image Sizer module or, if you specify "quality=75", is it 75 based on 80 (IMagick default), or 75 based on the original image?

Hope this makes sense! :)

Thanks.

Share this post


Link to post
Share on other sites

Hi @Gazley, you are speaking of the new core (PW 3) ImageSizerEngineIMagick.module? (Better do not use the old IMagick Sizer module, or, if so, do you stuck with PW 2.7 ?)

But to your question: The hirarchy of options is this way, lowest to highest: (higher ones overwrite lower ones)

  • module default                                  (is only there if all others are missing)
  • global setting in wire/config.php               (is the distribution default)
  • global setting in site/config.php               (can be set to overwrite the distribution default per site)
  • setting in array options, passed to pageimage   (overwrites all others)
    with methods width, height, size

If the module has a default of 80, the wire/config.php has 90, the result is 90.

If you pass an option with 75 to size(), the resulting quality is 75.

Pia is only a wrapper around pageimage, so any option passed to Pia (pageimage), overwrite all other (hirarchically previous) options.

  • Like 1

Share this post


Link to post
Share on other sites

Hi @horst - excellent answer! Many thanks indeed :)

I am using PW3 and taking advantage of all the latest goodness!

Hope you're having a great weekend and I appreciate your very quick response.

Cheers!

  • Like 1

Share this post


Link to post
Share on other sites

Edit: Please ignore this post - the more I play with the code, the more obvious the answer is and the more stupid this question is! Sorry

Hi @horst - I don't know whether this is the correct thread to ask this question but it is connected because I danced with this lady :)

I haven't done any cropping with PW before and have noticed the following. I add a "master" image to PW called "st_mi_18.jpg".

In the backend UI, I crop the image and PW saves the copy as "st_mi_18-v1.jpg".

The current use-case is that I want to save various "art-directed" versions of the master "st_mi_18.jpg" to use in a picture element. I guess the issue is, how do I reference these versions in my code if I didn't know the name that PW has generated? So far, PW saves them as V1, V2 etc.

I want to process (in code) each version (V1, V2) so that various sizes are available to support different DPR values but obviously, I need to access each art-directed copy (V1,V2 etc).

Do I just have to "know" that each version is called V1, V2 etc or, can I influence the name of the saved copy? Can I get V1 or V2 by using the $image variable with the known size/crop values and PW will return the matching Vx file?

I hope this makes sense. If you have any thoughts or opinions on what I am trying to do, I'd really appreciate them! :)

Many thanks.

Share this post


Link to post
Share on other sites

hello,

is there a way to add a prefix to the image name? i am trying to create a low quality and high quality image with the same size, but it seems one is overwriting the other

Share this post


Link to post
Share on other sites

You can add suffixes to image variations. 

If you want to do it with Pia, you need to add, for example, 

suffix=lowres, or suffix=hires to the selctor string.

If you want to add suffix names to image variations without Pia, pass an options array to the width, height or size methods as (optional) last argument. Within the array set the key suffix to your desired name. 

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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...