Jump to content
horst

Croppable Image 3

Recommended Posts

12 hours ago, adrian said:

I wonder if it has anything to do with using a string for the version number? I am switching my modules over to string version numbers as well, so would be good to know if that is the problem?

normally, the version compare function (should) work correct with strings like "0.9.17". But I can temporary change it, if this would help. (?)

 

I have updated the repo and changed the version from string '0.9.17' to number 100. Does that change anything?

Share this post


Link to post
Share on other sites

on a local test I added a fake module in the root of the modules directory hirarchy and changed the dependencies hirarchy to make it the main module that installs the three others:

/site/modules/CroppableImage3/
/site/modules/CroppableImage3/CroppableImage3.module **
/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module
/site/modules/CroppableImage3/InputfieldCroppableImage3/InputfieldCroppableImage3.module
/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module

**

Spoiler

<?php namespace ProcessWire;

class CroppableImage3 extends WireData implements Module {
    public static function getModuleInfo() {
        return array(
            'title'    => 'Croppable Image 3 (FAKE-Main-Module)',
            'summary'  => '',
            'author'   => 'Horst Nogajski',
            'version'  => '1.0.0',
            'requires' => 'ProcessWire>=3.0.20, PHP>=5.3.8',
            'installs' => 'FieldtypeCroppableImage3, InputfieldCroppableImage3, ProcessCroppableImage3',
            'icon'     => 'crop'
        );
    }
    public function __construct() {}
    public function init() {}
}

 

 

@adrian: This way it get recognized by the upgrade module. It seems, it has nothing to do with the version is a number or a string.

  • Like 2

Share this post


Link to post
Share on other sites
On 13.2.2017 at 1:59 PM, PWaddict said:

@horst Is it possible to force update the variations when the main crop has been edited without deleting the variations?

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Share this post


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

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Ok thanks for the info.

Let us know if you update the module to be visible on the Upgrades.

Share this post


Link to post
Share on other sites
2 hours ago, PWaddict said:

Let us know if you update the module to be visible on the Upgrades.

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Share this post


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

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Take your time to do it right.
I'm using the 0.9.17 version and when I check for updates from the module config I get: Session: Error reported by web service: Unable to find that module

EDIT: I've just manually upgrade to 1.0.0 and the issue still exists.

Share this post


Link to post
Share on other sites

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Share this post


Link to post
Share on other sites
10 hours ago, horst said:

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Shouldn't be say: Session: Current installed version is already up-to-date like on the other modules?

Share this post


Link to post
Share on other sites

@PWaddict: just to clarify: There are two things here:

The modules version is recognized and the module gets correctly updated via the individual update function in the modules config screen!

The module is not recognized by the third party updater module. This is an issue of that updater module!

What I have tried / described above, is to find a way / workaround without needing to contact the author of the third party module "updater" and ask him if he can debug and change the module to recognize modules that are organized like CI3 too. One way I found out to get recognized by the updater, is to use a wrapper module in the root directory of the module. This will work, AFTER everyone has updated to that version. But with the current situation, before everyone has updated to that version, there may be danger to break systems when silently changing the modules hirarchy and dependencies.

  • Like 1

Share this post


Link to post
Share on other sites

I have a recurring prob on PW 3.0.42 and CI 3 v.1.0.0 on PHP 7.0.16

Anytime I try to edit a page which uses an image crop, I get the following error

Quote

Error: Uncaught Error: Class 'ProcessWire\ProcessCroppableImage3' not found in /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module:81
Stack trace:
#0 /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module(58): ProcessWire\InputfieldCroppableImage3->getCropLinks(Object(ProcessWire\Pageimage))
#1 [internal function]: ProcessWire\InputfieldCroppableImage3->___renderButtons(Object(ProcessWire\Pageimage), 'images_e875838f...', 0)
#2 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(374): call_user_func_array(Array, Array)
#3 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/WireHooks.php(549): ProcessWire\Wire->_callMethod('___renderButton...', Array)
#4 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(399): ProcessWire\WireHooks->runHooks(Object(ProcessWire\InputfieldCroppableImage3), 'renderButtons', Array)
#5 /var/www/vhosts/my-domain.co.uk/httpdocs/wi (line 81 of /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged. 

I've refreshed the Modules several times (that worked before) but the problem persisted. I thought perhaps ProCache wasn't helping so I disabled that too temporarily.

Anyone have similar issues ?

Share this post


Link to post
Share on other sites

I think I've found the issue. My uploaded CI folder still have the "-master" name.

Seems to be working now.

Files.png.392fa29b0d54edb87ce7507868fa5447.png

Share this post


Link to post
Share on other sites

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

  • Like 1

Share this post


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

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

Hi Adrian

Thanks for the tip.

I normally do install via class name but CI 3 at the time had a more recent version which was only available from GitHub as a ZIP.

At least I think that was the case. Thanks anyway for the help.

Share this post


Link to post
Share on other sites
3 minutes ago, Peter Knight said:

which was only available from GitHub as a ZIP.

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

  • Like 2

Share this post


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

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

Nice - thanks :)

Share this post


Link to post
Share on other sites

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Share this post


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

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Some people do this via HannaCodes or other, self created markup-modules added to the ckeditor boxes.

Something like that:

[[image=theimagename.jpg, crop=thecropname]]

The above could be used by a custom markup module, if you have not installed HannaCode. Assumed you have only one image field on that templates/pages, you have to search for that image in the field and replace that marker with the img tag and src pointing to the crop.

if you have more than one imagefield on a page, you need to add a third param:

[[image=theimagename.jpg, crop=thecropname, fieldname=teaserimages]]

 

If you are willing to get your hands dirty with code and build an own markup module, this is a nice way to learn much about PW and PHP.

Otherwise you can install Hannacode and do it there. Hannacode is a flagship! :)
Pretty usefull for a lot more use cases.

  • Like 2

Share this post


Link to post
Share on other sites

Hello @horst,

First of all, thank you for adapting CroppableImage for ProcessWire 3.x. Modules like this one make ProcessWire into an (even more) robust and flexible option for all kinds of new projects.

I downloaded CroppableImage3 and I was wondering if "free" (variable) width/height is a supported feature in this module (and if not, could it be, pretty please?)

For example, suppose I have this in my field's crop settings:

freeheightcrop,900,0

This would allow the user to create a crop of 900px width and a custom height, so maybe the first image ends up being 900x500, the second one is 900x320, etc. It all depends on the dimensions of the area the user has selected during crop generation.

The calculation would be as follows: get the aspect ratio from the area selected by the user (e.g. a 640x360 area would have a 16:9 aspect ratio). Then, we already know the final width (900px). We calculate the final height using the selected area dimensions and the known final value (i.e. 900 * 360 / 640 = 506.25px --> round down --> 506px final height).

Same idea for width: freewidthcrop,0,900 only this time the width is the variable.

I tried to put freeheightcrop,900,0 into the field configuration and ProcessWire accepted it, but the user's crop won't be saved (it generates a crop that is exactly the same as the original image). Also, when cropping, the upper text that indicates the size of the selection will display "NaNxNaN" until the user selects an area.

Share this post


Link to post
Share on other sites

Hello Horst,

when I'm trying to install the new version I get an error:

( ! ) Notice: Undefined index: sharpening in D:\wamp\www\zaub\site\modules\CroppableImage3\FieldtypeCroppableImage3\FieldtypeCroppableImage3ConfAdaptor.php on line 96
Call Stack
#	Time	Memory	Function	Location
1	0.0040	374752	{main}( )	...\index.php:0
2	0.5650	13487256	ProcessWire\Wire->execute( )	...\index.php:55
3	0.5650	13487528	ProcessWire\Wire->__call( )	...\index.php:55
4	0.5650	13487528	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
5	0.5650	13487904	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
6	0.5650	13487904	ProcessWire\ProcessPageView->___execute( )	...\Wire.php:383
7	0.6430	14965016	ProcessWire\Wire->render( )	...\ProcessPageView.module:205
8	0.6430	14965064	ProcessWire\Wire->__call( )	...\ProcessPageView.module:205
9	0.6430	14965064	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
10	0.6440	14966448	ProcessWire\Wire->renderPage( )	...\WireHooks.php:782
11	0.6440	14966720	ProcessWire\Wire->__call( )	...\WireHooks.php:782
12	0.6440	14966720	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
13	0.6440	14967096	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
14	0.6440	14967096	ProcessWire\PageRender->___renderPage( )	...\Wire.php:383
15	0.6480	14970688	ProcessWire\Wire->render( )	...\PageRender.module:514
16	0.6480	14970736	ProcessWire\Wire->__call( )	...\PageRender.module:514
17	0.6480	14970736	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
18	0.6480	14971576	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
19	0.6480	14971576	ProcessWire\TemplateFile->___render( )	...\Wire.php:380
20	0.6480	14990608	require( 'D:\wamp\www\zaub\site\templates\admin.php' )	...\TemplateFile.php:268
21	0.6490	14991328	require( 'D:\wamp\www\zaub\wire\modules\AdminTheme\AdminThemeDefault\controller.php' )	...\admin.php:13
22	0.6490	15028512	require( 'D:\wamp\www\zaub\wire\core\admin.php' )	...\controller.php:13
23	0.6590	15076312	ProcessWire\Wire->execute( )	...\admin.php:113
24	0.6590	15076360	ProcessWire\Wire->__call( )	...\admin.php:113
25	0.6590	15076360	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
26	0.6590	15076736	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
27	0.6590	15076736	ProcessWire\ProcessController->___execute( )	...\Wire.php:380
28	0.6770	15619400	ProcessWire\Wire->executeEdit( )	...\ProcessController.php:244
29	0.6770	15619448	ProcessWire\Wire->__call( )	...\ProcessController.php:244
30	0.6770	15619448	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
31	0.6770	15619824	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
32	0.6770	15619824	ProcessWire\ProcessModule->___executeEdit( )	...\Wire.php:380
33	0.6810	15622488	ProcessWire\ProcessModule->renderEdit( )	...\ProcessModule.module:1136
34	0.7190	15742248	ProcessWire\Wire->getModuleConfigInputfields( )	...\ProcessModule.module:1213
35	0.7190	15742520	ProcessWire\Wire->__call( )	...\ProcessModule.module:1213
36	0.7190	15742520	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
37	0.7190	15742912	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
38	0.7190	15742912	ProcessWire\Modules->___getModuleConfigInputfields( )	...\Wire.php:383
39	0.7260	15747744	call_user_func:{D:\wamp\www\zaub\wire\core\Modules.php:3582} ( )	...\Modules.php:3582
40	0.7260	15747744	ProcessWire\FieldtypeCroppableImage3::getModuleConfigInputfields( )	...\Modules.php:3582
41	0.7320	15807072	ProcessWire\FieldtypeCroppableImage3ConfAdaptor->getConfig( )	...\FieldtypeCroppableImage3.module:478

 

Can you help me? I've tried to search for it, but found nothing.

ProcessWire 3.0.62 © 2017

 

Many greets!

Share this post


Link to post
Share on other sites

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

Share this post


Link to post
Share on other sites
On 20.5.2017 at 5:38 PM, horst said:

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

I deleted an older version manually and than tried to install the newer version via backend. 

Share this post


Link to post
Share on other sites

I have a serious and mysterious problem with CroppableImage3 module since I upgrade to PW 3.0.62.  Since my local copy of the site works perfectly well, I uploaded it to the production site, along with the database. But, I get this error when accessing a page using CroppableImage3.

Exception: There is no crop setting for the template 'promenade' called 'miniature' (in /home/guyvervi/public_html/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module line 209)

The miniature crop setting IS set. I really does not understand what is going on.

Share this post


Link to post
Share on other sites

I resolved my problem by adding a new crop setting in the my field and changing in my template to the new one... It does not explain why the previous crop setting still works on my local machine... Anyways...

Share this post


Link to post
Share on other sites

Hey, this is a follow up from here:

So, now I have tested every possible combination from ClassNames, filenames and the ModuleName. Every thing will break something when used from an allready installed module with an upgrade through PW.

When I define the main classname in the modules directory as FieldtypeCroppableImage3, the update process fetches the repo, but installs it under site/modules/FieldtypeCroppableImage3, whereas the existing repo stay under site/modules/CroppableImage3! This breaks the whole site, front and backend. The updater doesn't rename the origin repo with a leading dot.

Other solutions tested also broked things.

So, can you please tell me which way to go to bring the module into recognition of the update process?

Share this post


Link to post
Share on other sites

@horst, what if you create a new module file/class in the root of the CroppableImage3 directory named 'CroppableImage3', and that class does nothing apart from auto-install the other classes?

Not ideal of course but might be an okay workaround seeing as you are stuck with the existing directory name.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Xonox
      After some years with a website working perfectly, Page Clone started to display some strange behaviour:
      1. When cloning some pages, it takes forever. The waiting icon is displayed but the page never appears. Only after I refresh the tree page, the new page appears:

      2. The other thing is that some pages can't be copied. The pages have the same templates but the users are able to copy some and other don't. It gives this error:

      (the URL is .../page/clone/?id=76376&login=1)
      Does someone have a clue why this is happening. I can't find any real difference between the pages that I'm trying to copy.
      One more thing: If the user is a super user, he's able to copy every page without problems.
      I think both errors might be related. Thanks!
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-11-15 2019-10-18 2019-08-08 2019-06-15 2019-06-02 2019-05-25 If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module and >= ProcessWire v3.0.0.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Advanced
      Define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Build entire dialog form in a hook
      You can hook after HannaCodeDialog::buildForm to add inputfields to the dialog form. You can define options for the inputfields when you add them. Using a hook like this can be useful if you prefer to configure inputfield type/options/descriptions/notes in your IDE rather than as extra attributes in the Hanna tag settings. It's also useful if you want to use inputfield settings such as showIf.
      When you add the inputfields you must set both the name and the id of the inputfield to match the attribute name.
      You only need to set an inputfield value in the hook if you want to force the value - otherwise the current values from the tag are automatically applied.
      To use this hook you only have to define the essential attributes (the "fields" for the tag) in the Hanna Code settings and then all the other inputfield settings can be set in the hook.
      Example buildForm() hook
      The Hanna Code attributes defined for tag "meal" (a default value is defined for "vegetables"):
      vegetables=Carrot meat cooking_style comments The hook code in /site/ready.php:
      $wire->addHookAfter('HannaCodeDialog::buildForm', function(HookEvent $event) { // The Hanna tag that is being opened in the dialog $tag_name = $event->arguments(0); // Other arguments if you need them /* @var Page $edited_page */ $edited_page = $event->arguments(1); // The page open in Page Edit $current_attributes = $event->arguments(2); // The current attribute values $default_attributes = $event->arguments(3); // The default attribute values // The form rendered in the dialog /* @var InputfieldForm $form */ $form = $event->return; if($tag_name === 'meal') { $modules = $event->wire('modules'); /* @var InputfieldCheckboxes $f */ $f = $modules->InputfieldCheckboxes; $f->name = 'vegetables'; // Set name to match attribute $f->id = 'vegetables'; // Set id to match attribute $f->label = 'Vegetables'; $f->description = 'Please select some vegetables.'; $f->notes = "If you don't eat your vegetables you can't have any pudding."; $f->addOptions(['Carrot', 'Cabbage', 'Celery'], false); $form->add($f); /* @var InputfieldRadios $f */ $f = $modules->InputfieldRadios; $f->name = 'meat'; $f->id = 'meat'; $f->label = 'Meat'; $f->addOptions(['Pork', 'Beef', 'Chicken', 'Lamb'], false); $form->add($f); /* @var InputfieldSelect $f */ $f = $modules->InputfieldSelect; $f->name = 'cooking_style'; $f->id = 'cooking_style'; $f->label = 'How would you like it cooked?'; $f->addOptions(['Fried', 'Boiled', 'Baked'], false); $form->add($f); /* @var InputfieldText $f */ $f = $modules->InputfieldText; $f->name = 'comments'; $f->id = 'comments'; $f->label = 'Comments for the chef'; $f->showIf = 'cooking_style=Fried'; $form->add($f); } }); Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By horst
      Wire Mail SMTP

      An extension to the (new) WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.4.2
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; }  
      A MORE ADVANCED DEBUG METHOD!
      You can add some debug code into a template file and call a page with it:
      $to = array('me@example.com'); $subject = 'Wiremail-SMTP Test ' . date('H:i:s') . ' äöü ÄÖÜ ß'; $mail = wireMail(); if($mail->className != 'WireMailSmtp') { echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; } else { $mail->from = '--INSERT YOUR SENDER ADDRESS HERE --'; // <--- !!!! $mail->to($to); $mail->subject($subject); $mail->sendSingle(true); $mail->body("Titel\n\ntext text TEXT text text\n"); $mail->bodyHTML("<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>"); $dump = $mail->debugSend(1); } So, in short, instead of using $mail->send(), use $mail->debugSend(1) to get output on a frontend testpage.
      The output is PRE formatted and contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection, like this one:
       
      Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      debugSend(1) - returns and / or outputs a (pre formatted) dump that contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection. (See above the example code under ADVANCED DEBUG METHOD for further instructions!)


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
       
    • By Robin S
      Sanitizer EasySlugger
      Allows the use of the EasySlugger library as Sanitizer methods.
      Installation
      Install the Sanitizer EasySlugger module.
      Usage
      The module adds four new sanitizer methods.
      slugger($string, $options)
      Similar to $sanitizer->pageName() - I'm not sure if there are any advantages over that method. Included because it is one of the methods offered by EasySlugger.
      $slug = $sanitizer->slugger('Lorem Ipsum'); // Result: lorem-ipsum utf8Slugger($string, $options)
      Creates slugs from non-latin alphabets.
      $slug = $sanitizer->utf8Slugger('这个用汉语怎么说'); // Result: zhe-ge-yong-han-yu-zen-me-shuo seoSlugger($string, $options)
      Augments the string before turning it into a slug. The conversions are related to numbers, currencies, email addresses and other common symbols.
      $slug = $sanitizer->seoSlugger('The price is $5.99'); // Result: the-price-is-5-dollars-99-cents See the EasySlugger readme for some more examples.
      seoUtf8Slugger($string, $options)
      A combination of utf8Slugger() and seoSlugger().
      $slug = $sanitizer->seoUtf8Slugger('价钱是 $5.99'); // Result: jia-qian-shi-5-dollars-99-cents $options argument
      Each of the methods can take an $options array as a second argument.
      separator (string): the character that separates words in the slug. Default: - unique (bool): Determines whether a random suffix is added at the end of the slug. Default: false $slug = $sanitizer->utf8Slugger('这个用汉语怎么说', ['separator' => '_', 'unique' => true]); // Result: zhe_ge_yong_han_yu_zen_me_shuo_3ad66c4  
      https://github.com/Toutouwai/SanitizerEasySlugger
      https://modules.processwire.com/modules/sanitizer-easy-slugger/
×
×
  • Create New...