Jump to content

Recommended Posts

Hi @kongondo

For the moment I made some temporary additions to the MediaManagerActions.php file, so that it saves the title in all lang tabs. I added this lines to the code:

actionEdit()

foreach ($this->languages as $lang) {
		$p->title->setLanguageValue($lang, $sanitizer->text($media['title'])); //temporary by Nukro
}
//$p->title = $sanitizer->text($media['title']);

 

actionCreateMedia()

foreach ($this->languages as $lang) {
	$p->title->setLanguageValue($lang, $this->actionRenamer($title, $titleFormat)); //temporary by Nukro
}
//$p->title = $this->actionRenamer($title, $titleFormat);// @see @todo in actionRenamer()

 

I made this because my customer needs it urgently.

 

Greetings Nukro

  • Like 1

Share this post


Link to post
Share on other sites

Hi @kongondo

I am getting 

Empty file upload result

error upon upload. The file got uploaded though.

I am running 0.0.9

 

Thanks

Rudy

Share this post


Link to post
Share on other sites

Hi @Rudy. I think I have seen that error before in PW 3.X. I am not sure whether it is related to the PW version or if it is related to memory maxing out.

  • My guess is that your file is an image file? If so, then it is probably a large image and PW chokes on the thumb creation...due to memory issues.
  • Is the file added OK to your Media Manager library, i.e. it has a proper title, etc?
  • Were you uploading the single file or multiple files?

Please clarify these issues so that I can investigate further, thanks.

Share this post


Link to post
Share on other sites

Thanks for the lovely module, kongondo!

Before I commit, could you tell me if updating an existing image will create a new asset that must be re-linked, or can I overwrite an existing image and have all the proper associations update automatically?

(Sorry if this was already addressed, I tried to search for the answer but my keywords (overwrite/replace/existing) each only came up with talk of upgrading the module itself.)

Share this post


Link to post
Share on other sites

Hi @creativejay,

Thanks for your interest in Media Manager. Yes, that sort of update is supported. Change once, update everywhere  - no need to re-link; (but you would have to update any image variations yourself, of course). Please see point #5 in this post. Thanks.

Share this post


Link to post
Share on other sites

Hi @kongondo

Does the $config->pagefileSecure setting work with your module together? I tried it and it looks like it always blocks the access for guest users also when page(media) is published.

 

From a blog post about pagefileSecure:

Quote

"Added support for secured pagefiles. Now unpublished or non-public pages may have their files (in /site/assets/files/...) protected from direct URL access. You need to add $config->pagefileSecure = true; to your /site/config.php in order to enable this capability. Files become secured when the page is not accessible to the 'guest' role. Beyond roles, this also includes securing files for Unpublished pages. "

 

I have the feeling that it blocks always because the media pages live under the admin where no "guest" user has access? Am I right? Would it be possible to write a hook or something to support the pagefileSecure together with the Media Manager pages/files?

 

Greetings Nukro

Share this post


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

I tried it and it looks like it always blocks the access for guest users also when page(media) is published.

Isn't that exactly what $config->pagefileSecure is meant to do? According to the blog post you reference, it says the 'guest' role will not be able to directly access those files. In addition, I see this from the docs:

$config->pagefileSecure bool When used, files in /site/assets/files/ will be protected with the same access as the page. Routines files through a passthrough script.

Protection will match the same access as the page. I probably don't get your use case but it seems you want to have your cake and eat it too :lol:^_^. Do you want to secure your Media Manager media from guests? If yes, then the config setting is doing its job. MM files are secured from the public (guests).

I am guessing though that you want certain users with certain roles to still have access, no? In that case all you have to do is create a role, say 'view-mm-files' and add it to user(s) you want to have access to the files in the frontend. Then, head over to the respective MM media templates i.e. (media-manager-audio, media-manager-document, media-manager-image and media-manager-video) and under their Access Tab under 'What roles can access pages using this template (and those inheriting from it)?', under the column 'View Pages' check the box for 'view-mm-files (see screen below)'. That's it. No hook needed :). Those users (when logged in, of course) should be able to view protected files.

For the backend (i.e. use/view Media Manager) we already have the permission 'media-manager'. Just add that to the role you've created for your users, e.g. the 'view-mm-files' (as well as going through the above process of giving that role view access in the respective templates )and they should be able to both access Media Manager and see the media. 

 

 

mm-role-pagefilesecure.png

Edited by kongondo

Share this post


Link to post
Share on other sites

@kongondo

Sorry I somehow get confused now. To my understanding the pagefileSecure works like this:

pagefileSecure ON

      (The news template for example, which holds the image/file field has view access for guest users activated)

  • Guest User can't access unpublished/trashed image/document file with the direct url to it. 
  • Guest User can access published image/document files with the direct url to it.

      

      (the media-manager templates which holds the image/file field hasn't view access for guest users)

  • Guest User can't access any image/document file that comes from the media manager with the direct url to it.

 

pagefileSecure OFF

Guest User can access any(published/unpublished/trashed) image/document file (also the ones from the media manager) with the direct url to it (also the ones from the media manager).

Share this post


Link to post
Share on other sites

I somehow managed to delete the original post here when editing it :'(. Rather than rewrite it here, and since it was to feed into a write-up in the Media Manage docs, I might as well write it there. So, that's what I'll do. I'll find some time today and write that, er, write-up. I'll post a link here afterwards...

Edited by kongondo
Fat finger moment deleted my post!
  • Like 1

Share this post


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

Guest User can access any(published/unpublished/trashed)

A quick btw, in ProcessWire, by default, no users except for logged-in Superusers can view unpublished pages. 

Edited by kongondo

Share this post


Link to post
Share on other sites

Not true, any logged in user that has edit/view access can view a unpublished page not only superusers.

Add a page and upload a image. The image is in assets folder now and anyone can view that file in browser if you have the path. Even if you trash the page or unpublish page. This is where pageFilesecure comes in to avoid that.

Share this post


Link to post
Share on other sites

So i think thats the problem when enabling pageFilesecure. The files suddenly cant be accessed even if published and should be accessible for a guest user cause the pages under admin are protected. Im not sure how MM works. But maybe giving guest access to MM templates in admin could solve that but not sure what the consequences are.

  • Like 1

Share this post


Link to post
Share on other sites
20 minutes ago, Soma said:

Im not sure how MM works

Quick response lest I accidentally delete my post again! :lol:

There's two methods to access MM media (when pagefileSecure is off):

1. Indirect access; via its FieldtypeMediaManager API: $media = $page->your_media_manager_field; Returns a MediaManagerArray object. This will work regardless of the 'guest' setting in an MM template

2. Direct access: using normal PW API to reference the MM pages by their templates : $pages->find("template=media-manager-image, limit=10"); This will not work for guests unless access is granted in the template 'media-manager-image'

Keeping this short since I will be writing about this later tonight in MM's docs.

Share this post


Link to post
Share on other sites

Hi @kongondo

I have an suggestion about a new feature addition for replacing media. Would it be difficult to add a Message/Popup when the user is replacing media? At the moment it just replaces the media without a Warning Message or something like that. It would be a nice addition, since it is a risky move to let the users not know, that they have changed something, because they would replace media without noticing it. Also my customer become aware of this.

Greetings

Nukro

Share this post


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

At the moment it just replaces the media without a Warning Message or something like that.

Hi @Nukro,

Hmm, the default setting is to skip duplicate media. So, if media is being replaced the user must have set it so in the settings. A warning popup would just be an extra, to affirm what they've already set. I am not sure it will be easy/practical to implement since uploading is done via Ajax. I'll have a think. [Edit: should be easy enough as a checkbox to confirm before hitting upload :)]

By the way, I was not able to finish my write-up as promised in a previous post. I am determined to do this by the end of this week. Thanks for being patient with me.

Edited by kongondo
Clarification
  • Like 1

Share this post


Link to post
Share on other sites
On 27.2.2017 at 4:33 PM, kongondo said:

 [Edit: should be easy enough as a checkbox to confirm before hitting upload :)]

Hi @kongondo

Have you found some spare time to implement this feature?

Greetings Nukro

Share this post


Link to post
Share on other sites

Hi Kongo,

 Does the capability exist that allows the admin user to select from the media manager if the standard file/image field types are being used elsewhere?

So for clarification, I am using a file and image field type and would like the ability for the user to select from both the default or the media manager gallery. This will allow me to use the existing fields without losing any of the images that already live in the assets folder.

Edited by RyanJ
I updated this and removed my original issue as it was user error.

Share this post


Link to post
Share on other sites

I'm interested in this module for a particular site but for it to be most useful I'd need to get all existing files into the manager first and then update fields to use it rather than the current file/images fields.

Is the module able to scan the contents of assets/files and copy them to wherever Media Manager accesses them from? Or does it do that automatically when you install it?

Share this post


Link to post
Share on other sites

Hi @Tyssen,

Thanks for your interest in Media Manager.

On 21/04/2017 at 6:29 AM, Tyssen said:

Is the module able to scan the contents of assets/files and copy them to wherever Media Manager accesses them from? Or does it do that automatically when you install it?

No, not at the moment. The module creates its own fields for the 4 media types (audio, document, image and media). Each media item is a hidden page in the admin under respective media manager parent pages. I have been mulling adding this type of scanning functionality but haven't made a decision yet. Having said that, the module can currently scan /site/assets/MediaManager/uploads/

Please let me know if I can be of further help.

  • Like 1

Share this post


Link to post
Share on other sites

Media Manager version 010  (released 28/04/2017)

Happy to announce the latest release of Media Manager.

Changelog

  1. As per this request, added option to confirm duplicate media overwrite on upload. This, obviously, only works when the setting Duplicate Media is set to overwrite existing media with the one being uploaded. If you have that option selected, you will see a new option 'Always confirm when replacing/overwriting duplicate media' in the Duplicate Media sub-section. Tick that and save if you want to use this option. On the Uploads Tab you should now see a 'Confirm Overwrite' checkbox toward the top right of that page. Unless that checkbox is ticked, you will not see 'Start' upload buttons.
  2. Made various strings used in success/error messages in JavaScript translatable

This latest version is now available for download

Screens

'Always Confirm Overwrites' setting

media-manager-confirm-duplicate-overwrite-setting.thumb.png.2d5d0cb287cf89361a2353e7b4e4adec.png

'Confirm Overwrites' checkbox unchecked

media-manager-confirm-duplicate-overwrite-1.thumb.png.743fb7418f0c92abb8f2503dbe05983d.png

'Confirm Overwrites' checkbox checked

media-manager-confirm-duplicate-overwrite-2.thumb.png.373662bbee913d43e2ff8822b2f27f13.png

Edited by kongondo
Added Screens, etc
  • Like 4

Share this post


Link to post
Share on other sites
On 7.1.2017 at 6:28 PM, kongondo said:

Hi @Rudy. I think I have seen that error before in PW 3.X. I am not sure whether it is related to the PW version or if it is related to memory maxing out.

  • My guess is that your file is an image file? If so, then it is probably a large image and PW chokes on the thumb creation...due to memory issues.
  • Is the file added OK to your Media Manager library, i.e. it has a proper title, etc?
  • Were you uploading the single file or multiple files?

Please clarify these issues so that I can investigate further, thanks.

Similar problem here, version 0.10

Empty file upload result

The first test images were uploaded without any problem. Then I tried to upload a bunch of images. Part of them were uploaded successfully, but not all.

Now:

1. i can't upload image files, also no small ones

2. files are not added to the library (but saved in the assets folder)

3. i'm trying to upload single files

Share this post


Link to post
Share on other sites
21 minutes ago, Metaphora said:

Similar problem here, version 0.10

Hi @Metaphora. Sorry about the problems you are experiencing. It's a bit difficult to debug this one. Can't tell whether the problem is because of your ProcessWire version, or the image type or the image size or your server environment.

  1. Are you able to test using the exact same images using ProcessWire 2.7? I am assuming you are using ProcessWire 3.x. 
  2. Are you testing locally or remotely? If the latter, do you notice any difference if you test locally?
  3. Server environment?
25 minutes ago, Metaphora said:

also no small ones

I am not sure what you mean by 'small ones'? Do you mean size of file or dimensions?

28 minutes ago, Metaphora said:

files are not added to the library (but saved in the assets folder)

Do you mean the assets folder and not a sub-folder? What are your upload settings? E.g. upload and add immediately to library or upload to be added later to the library after review?

Share this post


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

Hi @Metaphora. Sorry about the problems you are experiencing. It's a bit difficult to debug this one. Can't tell whether the problem is because of your ProcessWire version, or the image type or the image size or your server environment.

  1. Are you able to test using the exact same images using ProcessWire 2.7? I am assuming you are using ProcessWire 3.x. 
  2. Are you testing locally or remotely? If the latter, do you notice any difference if you test locally?
  3. Server environment?

I am not sure what you mean by 'small ones'? Do you mean size of file or dimensions?

Do you mean the assets folder and not a sub-folder? What are your upload settings? E.g. upload and add immediately to library or upload to be added later to the library after review?

1. PW version 3.0.61

2. local server

3. PHP Version 7.0.8 / Apache/2.4.18 (Ubuntu)

Quote

I am not sure what you mean by 'small ones'? Do you mean size of file or dimensions?

I tried small images (file size and file dimension), to make sure it's not a memory problem.

Quote

Do you mean the assets folder and not a sub-folder? What are your upload settings? E.g. upload and add immediately to library or upload to be added later to the library after review?

Image is uploaded to a mediamanager sub folder, also a thumbnail is generated.
Upload mode = default values
Upload without review.

Share this post


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

Image is uploaded to a mediamanager sub folder, also a thumbnail is generated.
Upload mode = default values
Upload without review.

That's strange. Point #3 contradicts point #1. Media is only uploaded to that sub-folder if in the setting After Uploading you have selected option 3 (i.e., to keep media in a temporary folder until they have been reviewed). If you have option 1 or 2, the media is uploaded directly to the Media Library. Please confirm the option you have selected in this setting, just in case you are looking at a different setting from the one I am referring to, thanks.

Edit: Please also confirm that you have the latest version (005) Jquery File Upload

Edited by kongondo

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 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/
    • By Robin S
      If you've ever needed to insert links to a large number of files within CKEditor you may have found that the standard PW link modal is a somewhat slow way to do it.
      This module provides a quicker way to insert links to files on the page being edited. You can insert a link to an individual file, or insert an unordered list of links to all files on the page with a single click.
      CKEditor Link Files
      Adds a menu to CKEditor to allow the quick insertion of links to files on the page being edited.

      Features
      Hover a menu item to see the "Description" of the corresponding file (if present). Click a menu item to insert a link to the corresponding file at the current cursor position. The filename is used as the link text. If you Alt-click a menu item the file description is used as the link text (with fallback to filename if no description entered). If text is currently selected in the editor then the selected text is used as the link text. Click "* Insert links to all files *" to insert an unordered list of links to all files on the page. Also works with the Alt-click option. Menu is built via AJAX so newly uploaded files are included in the menu without the page needing to be saved. However, descriptions are not available for newly uploaded files until the page is saved. There is an option in the module config to include files from Repeater fields in the edited page. Nested Repeater fields (files inside a Repeater inside another Repeater) are not supported. Installation
      Install the CKEditor Link Files module.
      For any CKEditor field where you want the "Insert link to file" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "LinkFilesMenu" to the "CKEditor Toolbar" settings field.
       
      http://modules.processwire.com/modules/cke-link-files/
      https://github.com/Toutouwai/CkeLinkFiles
    • 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 a repeater item 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 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 Changelog
      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
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
×
×
  • Create New...