Jump to content

Recommended Posts

I had to move the CSS folder into the template folder. It's in the Markupblog folder in the Modules folder.

Thanks kuba2, worked perfectly as it should.

  • Like 1

Share this post


Link to post
Share on other sites

I had to move the CSS folder into the template folder. It's in the Markupblog folder in the Modules folder.

Yes, just like it says in the instructions :-)

If you chose to install the demo Template Files, also manually copy over the /css/ and /js/ folders present in Blog module's folder to your /site/templates/ folder.

@RogC1,

Welcome to PW and the forums. Please note that the CSS and the demo template files are just that; a demo...You can do pretty much what you want using MarkupBlog. I'm in the process of transferring the documentation to my new server. Thanks for choosing Blog :-)

  • Like 2

Share this post


Link to post
Share on other sites

Yes, just like it says in the instructions :-)

@RogC1,

Welcome to PW and the forums. Please note that the CSS and the demo template files are just that; a demo...You can do pretty much what you want using MarkupBlog. I'm in the process of transferring the documentation to my new server. Thanks for choosing Blog :-)

Thanks kongondo geuss I didnt read enough before I posted a typical newbie mistake :-[

Share this post


Link to post
Share on other sites

I'm sure this question has been asked and answered but I can't seem to find it.

First please excuse my lack of wisdom that stems from my newbiness.

In the readme it states "Easily output your Blog in the frontend, where and how you wish"

What my first goal is to out put recent posts lets say three of them on my home page.

I can't figure out how to do this.

Thanks in advance for any help.

p.s. If it matters I am using the Zurb Foundation Site Profile

Share this post


Link to post
Share on other sites

Hi Kongondo,

Is there a way of copying or preserving the blog posts on 1 database to another?

My users want the ability to auto-publish the blog articles, and it looks like it's possible but I would need to reinstall the Blog Module again with some pre-requisite modules preinstalled first?

I'm guessing reinstalling the Blog Module would result in the loss of the blog articles.

Share this post


Link to post
Share on other sites

Rather than reinstalling and reimporting from your old database, you can do the following:

Do not test this on the production server, obviously :-)

  1. Back up the database of your current Blog install
  2. Import your backed-up database into a fresh Blog install on your local/test server. This Blog install should not have 'Schedule Pages' installed (just to better illustrate the steps below)
  3. Check that this test Blog works fine
  4. OK, now the fun part. Install and configure the module Schedule Pages. If you do not yet have LazyCron installed, ProcessWire will complain that it cannot install Schedule Pages since a required dependency is missing. LazryCron ships with ProcessWire so, in that case, head over to modules -> install to install it.
  5. The module 'Schedule Pages' will create two fields with the names 'publish_from' and 'publish_until'. Give them appropriate labels if you wish, e.g. 'Auto-publish from' and 'Auto-unpublish on' respectively. Make sure you read the module's usage notes (e.g. that you need to confirm LazyCron is working properly on your server)
  6. Add the above two fields to the template 'blog-post' and save. If this had been done via the Blog Install Wizard, these fields are placed at the very top of the list of fields on this template, just above the 'blog_date' field  and given a width of 50%.
  7. OK, off to the database we go. In phpMyAdmin or similar, go to the ProcessWire database where you have your (test) Blog installed and find the table 'modules'. In that table, looking into the 'class' column, find the row 'ProcessBlog' (see screenshot below). In the column 'data' you will see saved Blog configurations (see example code below). Find and edit the entry 'schedulePages'. In your case it should be empty and looks like this: schedulePages":"". Modify it to be like this: schedulePages":1. That 1 tells Blog that use of 'Schedule Pages' is true. If using phpMyAdmin, it has inline editing (double click on what you want to edit and make your edits and mouse out to save)
  8. In your Blog's Posts Dashboard, under 'Quick Post' You should now see two entries 'Publish from' and 'Publish until'. When editing/creating a post, you should also see the two fields that you added to the 'blog-post' template. 
  9. Create (but do not publish) a Test Post to test auto-publishing/unpublishing at the dates you set. Note that since the module 'Schedule Pages' uses LazyCron, it needs a browser visit to trigger it. Visit your post (in the frontend, in a different browser where you are not logged in) at a time near its scheduled auto-publish time. You should get  404. Reload your browser some time after the auto-publish date and you should see your 'Test Post'.
  10. You are done :-)

database blog config

post-894-0-09988900-1449081225_thumb.png

database blog config without 'schedulePages' enabled

{"blogFullyInstalled":1,"blogStyle":"1","schedulePages":"","commentsUse":1,"templateFilesInstall":"2","tagTemplatesFields":"blog","blog":1020,"blog-posts":1021,"blog-categories":1022,"blog-tags":1023,"blog-comments":1024,"blog-widgets":1025,"blog-authors":1026,"blog-archives":1027,"blog-settings":1028,"blog-asc":1032,"blog-dnc":1033,"blog-dc":1034,"blog-rposts":1035,"blog-rcomments":1036,"blog-broll":1037,"blog-tweets":1039,"blog-pauthor":1040}
  • Like 1

Share this post


Link to post
Share on other sites

Hi Kongondo,

I've an early version of the blog module (2.0) running.

Now that I'm more comfortable with PW selectors etc I want to custom-build my own blog using basic pages. Tags and Categories will be new pages too. In fact - it's very similar to what you've done with blog but less technical.

My questions are:

1. if I start a new blog (manually built) is there anything to stop me moving the old Posts to a new containing Page (called Blog 2).

2. Ditto with Tags and categories (I'm not worried about Archives and Authors right now)

3. Not urgent but I'd like then to uninstall Blog. is there a clean way to do this and leave my tweaked templates intact or should I just leave it installed?

Share this post


Link to post
Share on other sites

@Peter,

  1. No. Just re-parent them or leave them as is and rename parent(s) (if you wish) Blog to whatever you want (e.g. Blog 2 :-))
  2. No. Ditto
  3. If you uninstall Blog without first running the Cleanup utility (only seen on menu if logged in as superuser), none of your fields, templates, demo template files, blog pages and role 'blog-author' will be touched. They will be left as is. So, don't run the Cleanup utility and you should be fine.
Edited by kongondo

Share this post


Link to post
Share on other sites

Hi and thanks for this modules sir.

For days, I follow https://web.archive.org/web/20150227095218/http://www.kongondo.com/tutorials, the docs, the forum and the source at https://github.com/kongondo/Blog/blob/master/MarkupBlog.module. Time for me now to ask help.

I would like to know what is the best way to get only posts's title, for example to show them in list in the footer of a page ?

Note: I have a newbie's experience with ProcessWire :rolleyes:

<div class="col-sm-4">
   <h3>Recents</h3>
   <?php

       $blog = $modules->get('MarkupBlog');
       $posts = $pages->find("template=blog-post, limit=5");
       foreach ($post as $posts) {
           var_dump($post);
       }
    ?>
</div>

Share this post


Link to post
Share on other sites

Hi @flydev

Welcome to ProcessWire and the forums and thanks for using Blog.

If all you want is to show the titles, there's no need to call the module itself. The posts are normal ProcessWire pages, so adapting your code like below should work.

<div class="col-sm-4">
   <h3>Recents</h3>
   <?php
       $out ='<ul>';
       //$blog = $modules->get('MarkupBlog');// no need for this line
       //$posts = $pages->find("template=blog-post, limit=5, sort=-blog_date");// if you want to sort by date
       $posts = $pages->find("template=blog-post, limit=5");
       foreach ($posts as $post) {
           //var_dump($post);
           $out .= '<li><a href="' . $post->url . '">' . $post->title . '</a></li>';
       }
       $out .= '</ul>';       
       echo $out;
    ?>
</div>
  • Like 1

Share this post


Link to post
Share on other sites

Yeah, that  ;) . Wanted to recommend that you look at the ProcessWire docs as well but figured out you are doing that already :-)

Share this post


Link to post
Share on other sites

@flydev are you sure you want to have an unfinished site as your signature? Although the domain is pretty cool :)

Share this post


Link to post
Share on other sites

Hi @Asmordean,

Welcome to the forums. 

Until yesterday, not it was not possible. Given your question (and previous requests), I have gone ahead and added an option to enable CKEditor in Quick Post (see demo below). This is currently in the dev branch only (version 2.3.6). To enable, follow these steps:

  1. Update Blog to version 2.3.6 from Dev branch (either download the zip or use url to pass to PW to upgrade the module)
  2. Scroll to the bottom of ProcessBlog's module configurations (via /modules/). 
  3. Check the box to enable use of RTE in Quick Post. NOTE: This setting (unlike the others) is available both before and after installing Blog). I decided to keep it here so that only Superusers can control it
  4. Head over to /blog/posts/ and reload the page. You should see CKEditor loaded

Note:

  • If you are on an older ProcessWire install without CKEditor, you will not see the RTE,  of course.
  • You cannot insert images in your post using this option. To do that, edit your post in normal 'page-edit' mode

Please test and let me know how it goes. 

post-894-0-34457800-1453208814_thumb.gif

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for testing. Please look out for any PHP errors (debug needs to be on => but not if you are testing on a live site :-)), thanks.

Share this post


Link to post
Share on other sites

Nothing so far, but it is just a dev domain at the moment.  My tiny number of hits per day aren't causing any issues yet.

Share this post


Link to post
Share on other sites

OK, thanks. I'll let it marinate a bit more then merge to master, probably next week.

Share this post


Link to post
Share on other sites

Hi,

This is a great module, and thanks Kongondo for all your work  :rolleyes:

I'm using featured images on my posts, which works fine apart from when I try to show the un-truncated post, when the image doesn't appear for some reason.
This is the code I'm using in my blog-post.php file (but I've also tried changing 'true' to 'false' in the blog.php file with the same result):
 

$options = array('post_small_image' => 1, 'post_count' => 0, 'post_comments' => 0, 'post_author' => 0);
$content .= $blog->renderPosts($page, false, $options) . $blog->renderNextPrevPosts($page); 

As you can see I've added some options, to turn off the post count, comments and author, since I don't need these features (I'm using the module more as a news page than a fully featured blog).

If I change 'false' to 'true' on line 57 the image is shown, but obviously the post body is truncated and displays the 'Show more' link, but using the 'false' option causes the image not to display.

Is there something I'm failing to do? I'll admit I'm a bit of a ProcessWire newbie!

Thanks in advance,

Tony.

Share this post


Link to post
Share on other sites

Hi Tony,

Glad you find the module helpful.

I have really been so busy I've not had a chance to update the docs, my bad. As the name of that option suggests 'post_small_image' will only work with truncated posts. What you want is its big brother, 'post_large_image' option set to 1. The default is 0 (meaning don't show the image), hence why you don't see your image in un-truncated posts. Until I get round to updating the docs, please have a look at the source code (not ideal, I know :-() for all available renderPosts() options (as well as other methods' options). For your particular question, these might also be of use:

$options = array(
  // ** large/full post featured image **
  'post_large_image_width' => '',// no width manipulation of featured image if this is blank or 0
  // no height manipulation if this is blank or 0. 
  // Note, if size is true and both width and height > 0, we use size() instead  
  'post_large_image_height' => '',				
  'post_large_image_size' => false,// if 'size' = true AND both width and height > 0, this kicks in
);
  • Like 2

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks for the reply.

I have really been so busy I've not had a chance to update the docs, my bad.

No need to apologise! If I'd given it some logical thought I should have realised that 'post_large_image' was meant for the full post. :)

Anyway it's working great now - thanks again.

Tony.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

@kongondo Finally got an opportunity to look at this Module(s). Deeply impressed and grateful to you (Ryan et al), this is fabulous, looking forward to building this in ^_^

  • Like 1

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