Jump to content
ryan

Map Marker Map

Recommended Posts

OK, guys.

I've tried to manually execute field creating SQL and what does MySQL said:

"#1214 - The used table type doesn't support FULLTEXT indexes"

All of this because of updateDatabaseSchema function in module. You just have to comment it out (I mean "$this->updateDatabaseSchema($field, $schema);" row in getDatabaseSchema)

Hope I helped to someone :)

P.S. Ryan, I think you should reupload new module version with this bug fixed.

Search tags: Table doesn't exist, mapmarker, new field

Share this post


Link to post
Share on other sites

Sorry about that guys. It turns out that it was trying to execute a query to update the schema of the DB table, before the table existed. The exception interrupted the creation of the field in the DB. I've fixed the issue and posted an update. This applies to new MapMarker fields only, no problem with existing fields (which is why I hadn't noticed). This update should also enable you to delete any fields you created that had this error (you'll want to delete it and re-create it, since it doesn't have a table).  

Regarding the "ENGINE=MYISAM" statement, that should already be getting added by the base Fieldtype.php. In your case, it probably didn't because the field creation process was getting interrupted. But I did double check to be sure:

echo "<pre>";
$ft = $modules->get('FieldtypeMapMarker')
print_r($ft->getDatabaseSchema($fields->get('map'))); 

results in:

Array
(
    [pages_id] => int UNSIGNED NOT NULL
    [data] => VARCHAR(255) NOT NULL DEFAULT ''
    [keys] => Array
        (
            [primary] => PRIMARY KEY (`pages_id`)
            [data] => FULLTEXT KEY `data` (`data`)
            [latlng] => KEY latlng (lat, lng)
            [zoom] => KEY zoom (zoom)
        )
    [xtra] => ENGINE=MyISAM DEFAULT CHARSET=utf8
    [lat] => FLOAT(10,6) NOT NULL DEFAULT 0
    [lng] => FLOAT(10,6) NOT NULL DEFAULT 0
    [status] => TINYINT NOT NULL DEFAULT 0
    [zoom] => TINYINT NOT NULL DEFAULT 0
)
 

Please let me know if you are getting a different result or still needing to specify the engine separately?

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

after installing the module and while I tried to add a field I got this error:

MapMarker: Error geocoding address

Then I assumed the field to my basic-template but when I try to save the page I got this error again and the coordinates aren't saved.

I tried to search for this issue but didn't found anything, but the code where the error comes from:

https://github.com/ryancramerdesign/FieldtypeMapMarker/blob/master/MapMarker.php#L84

I'm using PW Ver. 2.3.0. and the latest Version of this module.

Any ideas?

Greets, Jens alias DV-JF 

Share this post


Link to post
Share on other sites

What address are you attempting to geocode? MapMarker does both server-side and client-side geocoding. When you type something into the address, click anywhere else (outside of the field) and the Javascript geocoder should populate the latitude/longitude. If that is successful, it won't attempt to use the server-side geocoder when you save. You can disable geocoding by checking the box that exists between the address and lat/lng fields. If you only enter latitude/longitude values (whether entering the values directly or dragging the map marker pin), then it will attempt a reverse-geocode, which means it will attempt to find the street address for the coordinates. If you are dealing with an address (or coordinates) that Google Maps doesn't recognize, you may just want to disable the geocoder by unchecking the box. But I get the impression that neither the JS or server-side geocoder is working in your case, and that perhaps Google's geocoding service is blocked for you or something?

Share this post


Link to post
Share on other sites

What address are you attempting to geocode? MapMarker does both server-side and client-side geocoding. When you type something into the address, click anywhere else (outside of the field) and the Javascript geocoder should populate the latitude/longitude.

I can't see any map. After entering a correct cityname and click outside the field nothing happens. Lat and long are blank.

But I get the impression that neither the JS or server-side geocoder is working in your case, and that perhaps Google's geocoding service is blocked for you or something?

That where my thoughts, too, so I checked via chrome if the gmaps  api is working: When I'm open the url to edit the field it there are four requests - all seems to be loaded correctly :

Request URL:http://maps.google.com/maps/api/js?sensor=false
Request Method:GET
Status Code:200 OK
Request URL:http://maps.gstatic.com/intl/de_de/mapfiles/api-3/14/1/main.js
Request Method:GET
Status Code:200 OK
Request URL:http://maps.gstatic.com/cat_js/intl/de_de/mapfiles/api-3/14/1/{common,util,stats}.js
Request Method:GET
Status Code:200 
http://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate?1shttp://example.com/verwaltung/setup/field/edit?id=112&5e1&callback=_xdc_._opu9sd&token=49333
Request Method:GET
Status Code:200

No Scripts are blocked, tested it on different browsers. Same problem when I enter the lat and long by hand.

Share this post


Link to post
Share on other sites

Is your map field collapsed? There is a known problem with the rendering embedded google maps when they are hidden on page load.

Share this post


Link to post
Share on other sites

Is your map field collapsed? There is a known problem with the rendering embedded google maps when they are hidden on page load.

No, here's a screenshot of how it looks, when I try to save the field...

post-889-0-92001800-1378190869_thumb.jpg

Share this post


Link to post
Share on other sites

Is your map field in a tab other than "content"? This is the same as having the map field collapsed. The Map needs to appear on the main "content" tab. I'm not really sure why, but Google Maps doesn't like being hidden when the page renders. 

 

No, here's a screenshot of how it looks, when I try to save the field...

Attached Thumbnails
 

There is not supposed to be a map on the screenshot you posted. I'm not sure if that's where you are looking for one to appear, but wanted to mention it just in case. Where you will see a map is in your page editor. 

Share this post


Link to post
Share on other sites

Ryan I just pushed a change to the inputMapMarker.js file on github that solves this problem.

Added this inside the InputFieldMarker function:

// added by diogo to solve the problem of maps not rendering correctly in hidden elements
// trigger a resize on the map when either the tab button or the toggle field bar are pressed
$(document).ready(function() {

    // get the tab element where this map is integrated
    $tab = $('#_' + $(map.b).closest('.InputfieldFieldsetTabOpen').attr('id'));
    // get the inputfield where this map is integrated and add the tab to the stack
    $inputFields = $(map.b).closest('.Inputfield').find('.InputfieldStateToggle').add($tab);

    $inputFields.on('click',function(){
        // give it time to open
        window.setTimeout(function(){
            google.maps.event.trigger(map,'resize');
        }, 200);
    });
});
 

I had to put it inside the function, to have the "map" variable in scope. I'm not sure how we could move it outside the function if you don't like it that way.

Also, the 200 value on the setTimeout works for me (it works above 120 but I set it to 200 to be on the safe side), but we can decide on a safer value depending on other's tests.

  • Like 3

Share this post


Link to post
Share on other sites

In hind sight, I'm looking to use this module to get the lat and longs of some address for later display in a map.

However, I have already created the address with just simple text fields like this:

address1

address2

town <- page select

county <-page select (although not needed now as towns are linked to their counties)

PostCode

The user does update these fields through the backend, but a front end template.

Firstly, I'm guess that because of this, it will have to do server side processing ad conversion of the address.

Secondly, I can't change my field types now to map marker type.

I think, in it's simplest terms, I need to get it to take all the address fields, bash them together, process them and then turn them to lat longs.

What's the easier way to do this please.

I'm fairly new and learning....

Share this post


Link to post
Share on other sites

In hind sight, I'm looking to use this module to get the lat and longs of some address for later display in a map.

However, I have already created the address with just simple text fields like this:

address1

address2

town <- page select

county <-page select (although not needed now as towns are linked to their counties)

PostCode

The user does update these fields through the backend, but a front end template.

Firstly, I'm guess that because of this, it will have to do server side processing ad conversion of the address.

Secondly, I can't change my field types now to map marker type.

I think, in it's simplest terms, I need to get it to take all the address fields, bash them together, process them and then turn them to lat longs.

What's the easier way to do this please.

I'm fairly new and learning....

I've solved this, but i'm sure not in the most efficient way.

I've added an additional field to the template called marker and when the address is posted to the original address fields, i get php to bash them together and also post them to the map marker field like this:

 $postcode = $sanitizer->text($input->post->postcode);
 $telephone = $sanitizer->text($input->post->telephone);
 $date = $sanitizer->text($input->post->date) . "12:00:00";
 $town = $sanitizer->text($input->post->town);
 $type = $sanitizer->text($input->post->type);
 $email = $sanitizer->email($input->post->email);


$message = "<blockquote> Excellent news, your sale has been listed. Click <a href=".$config->urls->root."counties>here </a> to view other listings.</blockquote> ";

$sale_category = "1108";

    $p = new Page();
    $p->template = $templates->get("listing");
    $p->parent = $pages->get(1016);
    $p->title = $title;
    $p->address1 = $address1;
    $p->address2 = $address2;
    $p->postcode = $postcode;
    $p->telephone = $telephone;
    $p->sale_category = $sale_category;
    $p->town_select = $town;
    $p->Date = $date;
    $p->email = $email;

 $full_address = " $address1 , $address2 , $postcode " ;
           $p->map->address =$full_address;
           $p->map->zoom = 18;

Share this post


Link to post
Share on other sites

I had a hell of a time getting the map to show up as well, until I realized the Google map API is not compatible with jQuery 1.9.1. I swapped in jQuery 1.7 and suddenly it's Miller time.

Share this post


Link to post
Share on other sites

Davo, what you are doing there looks about right to me. Populating the $p->map->address should trigger the Google Geocoder into action. Just make sure you have a $p->save(); somewhere in there so that the coordinates get saved. 



until I realized the Google map API is not compatible with jQuery 1.9.1

I wonder why this is the case? I wonder if it's jQuery or google maps that's polluting the other (I'm guessing Google Maps). Can it be resolved by using jQuery() rather than $(), or is it something beyond this?

Share this post


Link to post
Share on other sites
    <?php $map = $modules->get('MarkupGoogleMap');
    echo $map->render($page, 'MapMarker', array('height' => '350px'));
    ?>

results in

Error:     Call to a member function render() on a non-object

while the MapMarker field is called 'MapMarker' to keep things simple.... Why?

Share this post


Link to post
Share on other sites

Davo, what you are doing there looks about right to me. Populating the $p->map->address should trigger the Google Geocoder into action. Just make sure you have a $p->save(); somewhere in there so that the coordinates get saved. 

I wonder why this is the case? I wonder if it's jQuery or google maps that's polluting the other (I'm guessing Google Maps). Can it be resolved by using jQuery() rather than $(), or is it something beyond this?

Ryan,

Thank you so much. There is indeed a save module there and I'm really pleased the way the api is working. It's a simple project site i'm working on for listings to help me learn pw. I'm very please how much progress I can make in a very short amount of time.

Thank you.

  • Like 1

Share this post


Link to post
Share on other sites
Error:     Call to a member function render() on a non-object
while the MapMarker field is called 'MapMarker' to keep things simple.... Why?

Your $modules->get('MarkupGoogleMap'); call failed. Chances are you don't have the MarkupGoogleMap module installed or are running an old version of FieldtypeMapMarker. 

Share this post


Link to post
Share on other sites

Nevertheless I have another bothersome issue....

When I add a page with a MapMarker field I need three saves before it actually saves. When I input 'city, state, country' in the MapMarker field and click outside it, the Latitude, Longitude and Zoom fields and the map all appear. Upon save there's a geocode error and the page could not be saved. The MapMarker field is empty. When I enter 'city, state, country' again, it saves without error but without Latitude, Longitude, Zoom and map. Then the MapMarker field remembers the 'city, state, country' info. Only upon a third save (and clicking in and out of the MapMarker field once more) it saves with all info in the right fields and rendered map.

Share this post


Link to post
Share on other sites

Nevertheless I have another bothersome issue....

When I add a page with a MapMarker field I need three saves before it actually saves. When I input 'city, state, country' in the MapMarker field and click outside it, the Latitude, Longitude and Zoom fields and the map all appear. Upon save there's a geocode error and the page could not be saved. The MapMarker field is empty. When I enter 'city, state, country' again, it saves without error but without Latitude, Longitude, Zoom and map. Then the MapMarker field remembers the 'city, state, country' info. Only upon a third save (and clicking in and out of the MapMarker field once more) it saves with all info in the right fields and rendered map.

I'm no expert, but you could try doing what I did a couple of posts above. I bashed my address fields together and let it to geocoding server side.

Share this post


Link to post
Share on other sites

What address are you trying to geocode? I want to try it here just to see if there's something unique about it that might be confusing Google's geocoder. Also, when the JS geocoder runs, it should bypass the server side geocoder unless something changes about the address during the save. If that's not the behavior you are getting, let me know what browser and version you are using \.

Share this post


Link to post
Share on other sites

Trial and error. There was a conflict between two googleapis scripts 'maps/api/js' and 'maps/api/js?v=3'. Seems to work on first geocoding now.

Edit: The error is back....

Enter 'Leipzig, Sachsen, Germany' in the MapMarker address field. Lat and Lng appear automatically when clicking outside address field and the map is rendered correct. On clicking 'publish' I get:

Added page /selectlists/cities/leipzig/
Added page /selectlists/states/sachsen/
Saved Page: /places/leipzig-sachsen-germany/ (4 changes) - Cannot be published until errors are corrected
Error geocoding address

The MapMarker field, Lat and Lng entries and map have disappeared.

I re-enter 'Leipzig, Sachsen, Germany', click outside address field and everything appears again. On 'publish' I get 'Error geocoding address' again but now the MapMarker field entry is still there while Lat and Lng are zero and the map doesn't show. Below the map it says 'over query limit'.

Clicking in and out MapMarker field and publish again finally renders the map.

head_inc has

	<script type="text/javascript" src="<?php echo $config->urls->templates?>scripts/jquery-1.9.1.min.js?>"></script>
	<script type="text/javascript" src="<?php echo $config->urls->templates?>scripts/main.js?>"></script>
	<script type="text/javascript" src="<?php echo $config->urls->modules?>FieldtypeMapMarker/InputfieldMapMarker.js?v=203?>"></script>
	<script type='text/javascript' src='https://maps.googleapis.com/maps/api/js?&sensor=false'></script>

Using Firefox 24.0 on OSX 10.8.5 - ProcessWire 2.3 - MapMarker 2.0.3

Share this post


Link to post
Share on other sites

It sounds like the connection is being blocked server side via a firewall or perhaps limitations imposed on PHP's functions for security. Go ahead and grab the latest update FieldtypeMapMarker/InputfieldMapMarker 2.0.5 which should bypass the need for server-side geocoding in many cases, including yours I think. 

Share this post


Link to post
Share on other sites

Enter address 'city, state, country' in the MapMarker address field. Clicking outside and Lat, Lng and map appear. Upon publish the page is accepted without an error but the MapMarker address, Lat, Lng and map are empty. Entering address again and save publishes successfully.

Share this post


Link to post
Share on other sites

I can't duplicate that here. Are you sure you've got the latest version? Do you have the checkbox checked that is between address and latitude? Try hitting reload once or twice on the page as well, just in case something older is cached. 

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...