Jump to content

Recommended Posts

Is it possible to hide the author link shown in the sub-nav sidebar (under the heading See Also)?

I've hidden the author in the post itself from the Settings in the Blog dashboard, but I'd like to do the same in the sidebar (since all posts will be written by the same author so it's rather redundant).

Having looked at the html I see that each sub-nav link is a <li>, but they're not given a unique class or ID so it's hard to target them individually.

All the best,

Tony.

@Tony,

It seems you are using (or copied from) the demo template files that are optionally installed with Blog. In this particular case we are dealing with blog-post.php. The code that generates that sidebar is found between lines 24 - 35. The method spewing out the markup is renderNav() (line #35).  As a quick btw, the general rule of thumb is rather than using CSS to hide markup, first check if it is possible not to output that markup in the first place :-). In our case, it is possible. Line #31 of the code is what is outputting the Author's name and URL. All you need to do is comment out that line, as well as earlier variables building up towards that code, i.e. lines 25 ($authorsURL), 27 ($authorURL) and line 28 ($authorName).

I'm not sure you've seen my earlier posts about documentation (it is a long thread after all), but I used to have Blog's documentation hosted on my website, which is currently in deep hibernation until I get time to revive it. Thankfully, the good guys over at wayback machine archived my now asleep and offline website including all the Blog tutorials. These can be found here and the documentation for renderNav() is here. As you'll see, you can use renderNav() to output all sorts of stuff.

Hope this helps :-)

  • Like 2

Share this post


Link to post
Share on other sites

Just in case you didn't see, the (fabulous, super-helpful and extensive) docs and examples @kongondo provided are here.

Current status: reading with a grin ^_^

  • Like 2

Share this post


Link to post
Share on other sites

Update: Merged dev 2.3.6 to master.

This version makes it possible to use CKEditor to create Quick Posts

Edited by kongondo
added some clarity
  • Like 2

Share this post


Link to post
Share on other sites

Hi,

how can i change the language in the frontend? For example "Post a comment".

I can't find any entries. :-X

Share this post


Link to post
Share on other sites

@congomonster,

Sorry this is one of those things that hasn't yet found its way into the documentation. Almost each method in MarkupBlog accepts options to alter its output. For the example you've given, that would be an option in renderComments(CommentArray $comments, $limit = 0, Array $options = null). Within the method, the $defaultOptions are as listed here. The option responsible for 'Post a comment' is 'comments_post_text' => $this->_('Post a comment'), . An example of passing options to the method:

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'
);

$blog = $modules->get("MarkupBlog");
$renderComments = $blog->renderComments($page->blog_comments, 0, $options);
$content = $blog->renderPosts($page) . $renderComments; 

echo $content;

Share this post


Link to post
Share on other sites

Hi kongondo,

thanks for your reply. But i need a more help to understand. Where did i have to put your example?

I put this in the blog-post.php template. I don't have to change it in the MarkupBlog.module file?

Share this post


Link to post
Share on other sites

Ok. Get it to work  :lol:

I put it in my blog-post.php and changed something looks now like this:

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'
    );

$renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments, 0, $options) : '';

Share this post


Link to post
Share on other sites

Two things:

  1. You never need to change the code in the module itself! Otherwise, your changes would be overwritten with upgrades
  2. You don't need this code to be like this: 
$renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments, 0, $options) : '';

If you read the comments in the demo blog-post.php template file, it says

for this demo, renderComments() has to adapt to whether blog commenting feature was installed or not whilst remaining blog structure/style-agnostic

 in your own blog install, you would know if you enabled the feature so there would be no need for such a check
in addition, our 'check' code is not code you would normally use in a template file. 
we use such code here to be both foolproof that the commenting feature is installed and blog structure-agnostic 

The blog demo could not know in advance whether you or anybody else was going to install Blog with the comments feature enabled/disabled. Hence, it had to make that check by looking into the module configs ($blogConfigs). In your case , you know if you installed blog with the comments feature or not, so no need to make such a check. Hence, use the other code I provided instead, i.e.

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'
    );

$blog = $modules->get("MarkupBlog");
// Here, no need to check if blog was installed with comments feature; you should know - you installed it yourself 
$renderComments = $blog->renderComments($page->blog_comments, 0, $options);

Share this post


Link to post
Share on other sites

Thank you very much! This helps me a lot.

Another question i have is, can i change classes the same way? I searched this topic but didn't find an answer.

For example:

In my blog overview there is

<ul class="MarkupPagerNav">
	<li class="MarkupPagerNavOn MarkupPagerNavFirst MarkupPagerNavFirstNum"><a href="/blog/"><span>1</span></a></li>
	<li class="MarkupPagerNavLastNum"><a href="/blog/page2"><span>2</span></a></li>
	<li class="MarkupPagerNavNext MarkupPagerNavLast"><a href="/blog/page2"><span>Vorwärts</span></a></li>
</ul>

how can i give "MarkupPagerNav" a second class like "pagination". I'm working with Zurb's Foundation Framework.

Share this post


Link to post
Share on other sites

@congomonster, I suppose you are using the pagination that comes with  renderPosts(), which is actually coming from the module @LostKobrakai has mentioned. I've added an option in renderPosts() that will accept an array of options to pass on to MarkupPagerNav. Will post an update within the hour

Share this post


Link to post
Share on other sites

Update: Version 2.3.7

Following this question, it is now possible to pass MarkupPagerNav options to renderPosts() if you wish to customise your posts' pagination. All the MarkupPagerNav options listed here can be passed as an array within an array to renderPosts() as shown in the example below:

$blog = $modules->get("MarkupBlog");

$paginationOptions = array(
                'nextItemLabel' => "Forth",
                'previousItemLabel' => "Back",
                'listMarkup' => "<ul class='MarkupPagerNav Zurb pagination'>{out}</ul>",
                'itemMarkup' => "<li class='{class} not necessary class'>{out}</li>",
                'numPageLinks' => 5
);

$options = array(
        'post_pagination' => $paginationOptions,// array of markup pager nav options
        'post_count_text' =>'Article',// other posts options passed as normal
);

echo $blog->renderPosts("limit=5", true, $options); 
  • Like 3

Share this post


Link to post
Share on other sites

Hi kongondo,

that's amazing! Thank you for your help. I tried it and it worked when i copy your code.

But i already hav an array for the defaults options. To translate "more" to "mehr" for example.

$content .= $blog->renderPosts("limit=5", true, $defaultOptions);

How can i put the second array behind the $defaultOptions array? I tried google. Is array_merge an option?

Share this post


Link to post
Share on other sites

Just like I've shown you in the example above :-). No need to do merges and such. See below (including the comments in the code); hope this is now clearer.

$paginationOptions = array(
                'nextItemLabel' => "Forth",
                'previousItemLabel' => "Back",
                'listMarkup' => "<ul class='MarkupPagerNav Zurb pagination'>{out}</ul>",
                'itemMarkup' => "<li class='{class} not necessary class'>{out}</li>",
                'numPageLinks' => 5
);

$defaultOptions = array(
        //  array of MarkupPagerNav options
        //  you have to use the index 'post_pagination' and its value MUST be an array
        //  here, we've passed it the array $paginationOptions that we created above
        'post_pagination' => $paginationOptions,// the value here must be an array; the index must be named 'post_pagination'
        
        // other stuff you already had in your defaultOptions
        'post_more_text' => 'mehr',
        'post_whatever_option_1' => 'blah blah blah',
        'post_whatever_option_2' => 'foo bar',
);

$content .= $blog->renderPosts("limit=5", true, $defaultOptions);
Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites

Hi,

i have still some things that i needed to change. Maybe someone knows the answers.

1. After i installed the modul upgrade Processwire says that i have more then one of this modules installed and that i have to choose.

Is this normal?

2. It is possible to add a new entry to the shortcut menu (backend) in Processwire? Blog Category and Blog Tag are already there.

How can i add for example Blog Post?

3. In the Comments section the date is still in english. I changed the date value in blog_date field into german

am %A, den %d.%m.%Y

I tried the same in the field blog_comments. But this doesn't work.

Share this post


Link to post
Share on other sites

#1: Not normal. PW version? If you ugraded using PW, it should have renamed the older folder as .ProcessBlog or similar

#3:

A PW date field has two parts. The output and input formats. Have a look at both (input is in the input tab).

  • In the Details tab (Date/Time Output Format Code), you can use your strftime code: am %A, den %d.%m.%Y. You will see that date in the frontend (in your post)
  • In the Input tab (Date/Time Input Formats -> Date Input Format Code) I think you can only use PHP date. So, something like l, d.m.Y in the date input format code will give you Thursday, 11.08.2016. You will see that when editing your post in the backend. You will not be able to uses 'den' with PHP date 
Edited by kongondo

Share this post


Link to post
Share on other sites

The Processwire Version is 2.7.0. I have a folder MarkupBlog and a folder called ProcessBlog. There is no folder .Processblog.

I have show hidden files on.

I already changed the entries in the input tab. The format is changeing. But the month stays in english.

Share this post


Link to post
Share on other sites

In the field blog_comments is a section where i can put my date. It says that this is the output for my comments. I can use date or srftime.

I thought strftime makes a language change. But everything i put in will not be regognized.

Share this post


Link to post
Share on other sites

@congomonster, thanks for catching that. Fixed; in dev branch for now. 

@all

Please note that if you want the method MarkupBlog::formatDate() to output your comments date according to the date field in blog_comments, you just need to pass it a second parameter 2 (integer 2). For instance, in the template file 'blog-recent-comments.php', line #30, we had this:

$date = $blog->formatDate($comment->created); 

...but we now have this:

$date = $blog->formatDate($comment->created, 2); 

Since the second parameter is give a value of 1 by default, this change should be backward compatible. Unless you want the updated feature, you don't need to do anything in your template files.

Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites

Hi kongondo,

I tried out your huge module and I think would like it, but it doesn't work properly (using PW 3.0.7). I will give you a small bug list.

  1. clicking on Posts results in Error: Call to a member function count() on null (line 1355 of .../site/modules/ProcessBlog/ProcessBlog.module.
    Problem: field blog_files isn't assigned to the blog-post template by default which is the reason for the error above.
    After removing line 1355 the modal for posts doesn't appear after clicking, linked page opened instead
  2. The dropdown function of the tabs in Admin are disabled if blog tab is active
  3. cannot open Settings -> Settings -> Edit
  4. cannot open Tags -> New -> Tags Add
  5. cannot open Categories -> New Categories -> Add
  6. cannot open Posts -> Quick Post -> Add
  7. cannot open Edit Posts -> Actions
  8. Dead link (404) in Module description on processwire.com http://kongondo.com/tutorials/specific-features/creating-a-blog-in-processwire/
    (just realized in the topic of this thread a temporarily link to the tutorial)

A personal wish: Dashboard -> Archives -> month clickable with link to a list of selected items

Share this post


Link to post
Share on other sites

Hi @kixe I know @kongondo or others will probably be better able to help you but I just wanted to say that the good news is that:

I think would like it, but it doesn't work properly
is incorrect as far as my experience goes—I just installed it on a fresh PW v2.7.3 and it worked perfectly, no errors.
 
To begin to help, perhaps, check you have debug turned on in config.php `$config->debug = true;`, then there is this post.
 
Sorry if you have already done this and good luck; it's worth it, the @kongondo's Module(s) for the blog make a very professional, complete solution. I was greatly impressed when I tried it.
  • Like 1

Share this post


Link to post
Share on other sites

@kixe,

Thanks for pointing these out in advance. I am not being naughty but as you can tell from here, Blog is only compatible with ProcessWire 2.4 - 2.7 :P  :-). I have been so busy I haven't even had a chance to install, let alone play with ProcessWire 3.X. 

So for now, I am not able to support Blog for that version of ProcessWire, but I do appreciate people catching such bugs in advance (although, PW 3.X is still an evolving beast) :-)

Edited by kongondo

Share this post


Link to post
Share on other sites

Thanks for the quick answer. I am pretty sure your module works proper in 2.7. I am involved in 2 projects both based on 3.0 probably going online in summer. I updated already most of my stuff for 3.0. Ryan is working very very quick and I am pretty sure we will have a stable Version of 3.0 very soon.
 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By Mike Rockett
      TextformatterTypographer
      A ProcessWire wrapper for the awesome PHP Typography class, originally authored by KINGdesk LLC and enhanced by Peter Putzer in wp-Typography. Like Smartypants, it supercharges text fields with enhanced typography and typesetting, such as smart quotations, hyphenation in 59 languages, ellipses, copyright-, trade-, and service-marks, math symbols, and more.
      It's based on the PHP-Typography library found over at wp-Typography, which is more frequently updated and feature rich that its original by KINGdesk LLC.
      The module itself is fully configurable. I haven't done extensive testing, but there is nothing complex about this, and so I only envisage a typographical bug here and there, if any.
    • By robert
      I often had the need for an overview of all used fields and their contents for a specific page/template while developing new websites without switching to the backend, so I made a small module which lists all the needed information in a readable manner (at least for me):
      Debug Page Fields
      https://github.com/robertweiss/ProcessDebugPageFields
      It adds two new properties to all pages:
      $page->debugFieldValues – returns an object with all (sub-)fields, their labels, fieldtypes and values $page->debugFieldTypes – returns an object with all fieldtypes and their corresponding fields // List all values of a pages $page->debugFieldValues // List a specific field $page->debugFieldValues->fieldname // List all used fieldtypes of a page $page->debugFieldTypes I recommend using it in combination with Tracy Debugger, Ray, Xdebug etc. as it returns an object and is only meant for developing/debugging uses. 
      For now, the fieldtype support includes mostly fieldtypes I use in my projects, but can easily be extended by adding a new FieldtypeFIELDNAME method to the module. I use it with five different client installations (all PW 3.0.*), but of course there might be some (or more) field configurations which are not covered correctly yet.
      Supported fieldtypes
      Button Checkbox Color Combo Datetime Email FieldsetPage * File FontIconPicker Functional Image ImageReference MapMarker Multiplier Mystique Options Page PageIDs PageTitle Radio Repeater * RepeaterMatrix * RockAwesome SeoMaestro Table Text Textarea Textareas Toggle URL * The fields with complete subfield-support also list their corresponding subfields.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. As this is my first ›public‹ module, I hope I did not miss any important things to mention here.
    • 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.6.0
      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 Cybermano
      Food Allergens Module
      A simple List of Food Allergens
      My needs were to provide a simple list of food allergens for our clients with restaurant related activity.
      The idea was to simply output the list (to speed up the data entry) without leaving the food menu editing, eg. opening another page in new tab or window.
      This isn't a perfect solution, but it works fine for my needs and I decided to share the base idea.
      This could also be easily used to show little notes or short "vademecum", not only for the list of food allergens.
      ---
      Main features
      The basis
      All moves from a short editing of the module in this tutorial: How to create custom admin pages by @bernhard
      First of all it creates an empty admin page, with a dedicated permission to let safe-user to see it (this permission has to be created as a new ones, manually or by the module).
      Once the page is created, I have hooked its behaviour into the ready.php, to show the content (basically a list).
      A step further
      With the tips of  @bernhard, @Soma (and many others), see here , the magic happens. 
      The new page will be shown as a panel, so editors will not abandon their data entry to have a quick view to the list.
      A little further
      Why scroll to the top of the page to click a link?
      The next step was to create a sticky button only in the food menu pages.
      Again with a @bernhard tip I moved into the customization of this simple module and the related hook.
      ---
      How to use this module
      After installed, it creates the page /admin/page/allergens/ and the module is to be setted up. The first field is a CKEditor with multi-language. This is the place where to write the informations that will be shown into the page. The next field is a simply text-area where to place a bit of JS that will be appended to the markup of the text (omit the 'script' tags). I also putted a checkbox with a silly statement: this to think at least twice on the safety of the written JS. Now comes the first way to display the link to the page
      Field Note with Link. Enable and save it. The module will display a new row with 4 selects (1 standard and 3 ASM):
      View mode (to show the page as Panel or as Modal PopUp); Templates to select: select one or more and save before proceed, so the  asm-select of the pages will be populated showing all the pages of the selected templates. Pages to select: also here select at least one and save before proceed to populate the asm-select for fields only with the ones that belong to the selected pages. Select the fields where to place the note and save again. That's all: now you will find into the notes of the selected fields the link "See the List of Allergens".
      At the same way, the option for the sticky button, but with a plus
      The field select is obviously unnecessary, but you could play with the last row: the inline styles to fix your sticky button where you like. Here you could set the sticky position of the <div> and the absolute ones of the <a>.

      Video Explanation
      In these screencasts you could see a custom JS that show a "copy" button near a "hanna-code" call.
      This because I've set a specific one for each allergen to show up a tooltip in the front end.

      Registrazione #33.mp4  

      Registrazione #34.mp4 ---
      Last but not the least
      Actually it works fine for my needs, even if it's much improvable: I'm working on the permissions creation, the uninstall section, a separate configs and defaults and how to include the hook into the module leaving free the ready.php. According to a simpler uninstall. Also I would make the link text as a dynamic text field, so it will be more flexible.
      I always learn a lot here, so I would share my code for whom it could be interested.
      I removed the hanna code references, but I provide you the html list of the allergens, English and Italian too, so you can paste them into the "source" of the CKEditor field to have a ready to use module.
      Obviously you are free to modify the code as per your needs.
      Please, keep in mind that I'm not a pro coder and I beg your pardon for my verbosity (speaking and coding). 😉
      I hope be helpful or for inspiration.
      Bye
      ready.phpList-ITA.htmlList-ENG.htmlAllergens.module
      README.md
×
×
  • Create New...