Jump to content

Recommended Posts

Hi all....

Apologies...I think I am now several months behind in respect of all my modules...I am still swamped with other stuff. My "I'll get to this next week.." have come and gone. I'am desisting from uttering such words for now... :). I am hoping to get to things as soon as I can....This may take a while...

@quickjeff. 

Thanks for using the module. About the main dashboard timing out, as you can see here (my bad) that has been on my to do list for a while. The other dashboards all have a limit (default = 10 if not set per user), hence don't time out (e.g. here....for Posts dashboard). For now, a quick solution for you would be to place a limit on that line...Of course that would mean it won't reflect a true count...but you could change the line as well to only display the latest posts. Eventually, I will address this more elegantly but unfortunately I don't have a firm time scale right now...

@teppo,

Thanks for reminding me about this..

Share this post


Link to post
Share on other sites

Hi  When installing ProcessBlog & MarkupBlog I selected the blogstyle 4 (add post as child of 'Home').   I rearranged my pages and now it should be blogstyle 1.  Add post is still as child of 'Home'!   How can I change the blogstyle from 4 to 1 ?

hansv

Apologies for the delay in getting back to you. The easiest way is to use the 'Cleanup Utility' to uninstall the Blog components (pages, fields, templates) and run the install wizard again (i.e. the second part of the install). Otherwise, you would have to fiddle with raw database values to change a whole lot of things. It can be done, but you need to know what you are doing.

Thanks for using Blog.. :)  

Any plans to add gravatar or avatar to comments and if not, am looking to implement one for my website, you don't mind pull-requests ?

Apologies for the delay in getting back to you. Blog utilises the (core) Comments Module that ships with PW. You'd have to direct this request to Ryan.

Share this post


Link to post
Share on other sites

I belie

@quickjeff. 

Thanks for using the module. About the main dashboard timing out, as you can see here (my bad) that has been on my to do list for a while. The other dashboards all have a limit (default = 10 if not set per user), hence don't time out (e.g. here....for Posts dashboard). For now, a quick solution for you would be to place a limit on that line...Of course that would mean it won't reflect a true count...but you could change the line as well to only display the latest posts. Eventually, I will address this more elegantly but unfortunately I don't have a firm time scale right now...

Unfortunately he already tried that based on my suggestion here: https://processwire.com/talk/topic/10609-processwire-site-header-and-footer-used-in-wordpress-blog/?p=100209

Are there any other places I have missed where adding a limit might help?

Share this post


Link to post
Share on other sites

I have enabled tags for blog_images field to use the featured image feature, but the tags are not saving. What could be the reason for tags not saving? I am using the latest dev version 2.6.4.

Are referring to the tags of an image field? If so, this is a question for Ryan really since it is outside the Blog Module's control. If you are still experiencing this problem, please file your question in the general support forum or if you've confirmed it is a bug, in GitHub (PW-dev).

Share this post


Link to post
Share on other sites

Unfortunately he already tried that based on my suggestion here: https://processwire.com/talk/topic/10609-processwire-site-header-and-footer-used-in-wordpress-blog/?p=100209

Are there any other places I have missed where adding a limit might help?

Ah, I missed that. Lines #818 and #821 also need limits (or some other filter)....(sloppy coding!!! Will optimise all three [eventually]....)....

Share this post


Link to post
Share on other sites

Ah, I missed that. Lines #818 and #821 also need limits (or some other filter)....(sloppy coding!!! Will optimise all three [eventually]....)....

I saw those two, but figured that since they are $pages->count() calls they wouldn't be a problem as they are not loading those page into memory - right ?

Oops, they are count($pages....), rather than $pages->count(). Maybe that simple change would make a big difference.

  • Like 1

Share this post


Link to post
Share on other sites

That's what I (must have) thought but not sure any more I must admit....haven't tested this in a while.... :). Either way, lines 818-825 will need looking at closely again...

Share this post


Link to post
Share on other sites

@ kongondo @adrian - Unfortunately, even adding the limit=10 to all three areas, still loads very slowly. What I don't get is why /admin/blog/posts/ loads so fast and displays all post quickly? Also an FYI, i have 420 posts at the moment. 

Share this post


Link to post
Share on other sites

Oops, forgot one more (the archives table that's part of the main dashboard)...Please try to set a limit in line 931 as well and let us know if it makes a difference...

Share this post


Link to post
Share on other sites

@kongondo, It loads but man does it take long. I thought it was going to timeout again. Its just odd, posts, categories settings etc. load lightning fast. 

Share this post


Link to post
Share on other sites

Yeah, will revisit this when I can find some time...For now, alternatively, you can skip the dashboard by making it redirect to posts....(so posts dashboard will be the landing page...)

This at the top of the function blogDashboard should do it (i.e., insert as line #799):

$this->session->redirect(wire('page')->url . "posts/");//redirect to posts dashboard
Edited by kongondo
added code

Share this post


Link to post
Share on other sites

@kongondo, that was going to be my plan B. :-)

Updated my post above with how to do it  :)

Share this post


Link to post
Share on other sites

@Kongondo -  Okay, cool. I will have to use this for now. I don't think the rest of the module is broken or anything. I think just the loading of the dashboard is buggy. Unless you think I shouldn't run the module on a site that is going to grow at 3-4 posts per week?

Share this post


Link to post
Share on other sites

Should be fine but I suggest you thoroughly stress test...When I find some time I'll take it through its paces RE scalability.....

Share this post


Link to post
Share on other sites

@quickjeff,

Found a bit of time to work on this. The Authors' Dashboard was also relatively slow. Worked on that as well. Using a combination of $pages->count() (thanks @adrian) and raw SQL queries (as explained here) and testing using 10,011 posts, the main Dashboard loads in 0.3 seconds on my machine. I think that's an acceptable time :) (given the 10+ seconds it took me to load main Dashboard with 5K posts). Although I tested with a minimal comments count, I don't think this will make much difference where there's lots of comments (using SQL for the counts). I will also look at Categories and Tags (in cases where these could run into thousands) just to be sure. Posts Dashboard loads fast as usual. Unfortunately, I still don't have time to merge the new changes any time soon.

post-894-0-88797600-1439509671_thumb.png

  • Like 2

Share this post


Link to post
Share on other sites

@kongondo this is great news! Wish I could see an update in code. :-( would love to implement this in my clients site.

Share this post


Link to post
Share on other sites

Hello, 

I have some trouble with the blog-author role. 

 I have also an editor role which can edit and add the pages. 

exampleuser 

       - editor-role

       -blog-author

but only superuser can edit the Pages. How I can handle this problem ? 

Thanks 

The module only creates the role 'blog-author'. You have to assign the right permissions to that role yourself (when editing the role itself) and check and edit the respective blog templates' access controls (i.e. the 'what roles can access the pages using this template' setting in a template's access tab).

Share this post


Link to post
Share on other sites

Good afternoon, fellas,

sooo I installed the blog module, and it works totally fine, kicking ass and everything, I love it.

I'm currently working on a site which is not a blog, but has a blog- subpage, which I got rolling. But what happens, or more like what do I do, if I want a second Subpage on my site which uses the blog - functionality? is there a way to achieve this?

consider the following page tree:

Home

stuff -> regular  content

stuff2-> Blog 1

stuff3 -> Blog 2

 

.. and so on.

so basically I would want two subpages on my site on which I would be able to publish blog posts independent from each other, which (in my opinion) would mean that I could tell the blog module at a certain point to publish a post on either one of these two pages.

Help would be much appreciated.

Best regards, 

DeM

/edit:

so I kinda had an idea for an approach to a solution to my problem, my thought was, that I could use two templates, which output blog posts by category, so basically I'm looking for a function which outputs posts with category "blog1" on the first page and in a second php script, one that outputs posts with category "blog2" on a separate page.

so far though, I couldn't find anything about that in the documentation, I only found output filtered by post author, does the same apply to post category?

//edit 2: I managed to do that, just had to change a few lines in one of the php files. Finally, everything works, and I have to admit, I am totally impressed. this module kicks ass in any way imaginable. Thank you so much Kongondo.

Greetings from Germany,

DeM

@DeM,

Glad you got it sorted. As you noticed, what you wanted was not available right out the box. 

Share this post


Link to post
Share on other sites

Hi Guys,

I was wondering whether there is an option to change the language of the publishing date of each post and also the archives from English to German.

So far though, I was unable to find a solution to this. Is this possible?

To elaborate: I want individual posts and the archive to say :

2015

       März

rather than

2015

     March

I tried changing the locale in my header.inc but that didn't help. So is there a way to achieve this?

Greetings from Germany

derelektrischemoench

Share this post


Link to post
Share on other sites

So back again,

get some sparetime to contribute to this one.

It's a real beast now with many strings to translate....and i added a few one, too..... ;)

https://github.com/kongondo/Blog/pulls

But here we are.

Complete DE translation for the actual Blog version 2.3.4 (and it's comming pullrequests with additional strings for archive, and pages).

+ Translated SchedulePages module to use both combined.

Important Notice on the main translation thing with the blogmodule:

- Some Strings are taken from the pagetitels of the autogenerated pages for eg. "cathegories" or "archive" so please use the installation step with renaming the parents correct or rename the titels later.....but not the names... ;)

- CleanUp Ultility is not complete translated because it's only a superuser thing wich should be used with care and knowlegde so don't see a real effort to translate this rarely used function...

-Some Strings are not translateable since the where automatic generated on templates and fields so please translate these, too - if needed...

Have fun - Thanks again to kongondo

So take a look at the generated template labels and field labels...to get everthing translated.

I've you have some special things that are not work please give the exact explanation where the phrase is located may put a screenshot in the post....for me i've all translated in german lang...so feel free to ask.

But i need the exact place where i've to look...since i'll glad to help you but at the other side i am lazy, too :P

Share this post


Link to post
Share on other sites

Hi Guys,

I've just deployed my first site built with the Blog Module and on the surface all is well. However, when ProCache is turned off, the blog summary page loads awfully slowly despite there only being ten or so short blog summaries displayed (at this moment in time). It would be unacceptable performance if it weren't for ProCache.

I looked into what the bottleneck was and the Blog pages are being returned by ProcessWire in an instant so, it's not data retrieval. When I stepped into the MarkupBlog.module, renderPosts method with small set true, around line #746 there is the following line:

$summary = strip_tags(substr($page->blog_body, 0, $summaryLimit), $options['post_small_allowable_tags']);

With summary limit set at 450, I noticed that the PHP strip_tags() function takes an absolute age to run! As far as I can see, this is the line of code that creates the bottleneck I am seeing without ProCache.

Has anyone else come up against this as a performance bottleneck?

Look forward to hearing from you.

Cheers and thanks! :)

Share this post


Link to post
Share on other sites

@Gazley,

Must be at your end mate. I haven't encountered this nor read anywhere that strip_tags is slow. As you can see in this demo with +10K posts, showing 20 posts per summary page with a summary limit of around 500 words each and WITHOUT ProCache, PW loads the page in about 2 seconds..

http://demo.kongondo.com/blog/

And with shorter summaries: http://demo.kongondo.com/blog/posts/

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo

Many thanks for looking into this! So, I looked at my blog_body field's text formatters. I had three specified in the following order:

Hanna Code Text Formatter

Textile

Profield: Autolinks <-- This guy hurts!

When I removed "Profield: Autolinks", the whole page load speeded up to something like I would have expected to see. So, the culprit here is Autolinks -- go figure? I wouldn't have expected that but with Autolinks, it takes an absolute age for the $page->blog_body to be rendered before it is passed into the strip_tags() function.

I guess you don't notice this when rendering a single page but when on a tight'ish loop, you clearly see the performance hit caused by Autolinks. Wow.

Cheers! 

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