Jump to content

Recommended Posts

1 hour ago, heliumrotator said:

Only the configuration looks very ugly. I don't know if this your new style or an accident. I saw that better in the official video:

The very ugly configuration is the new style (since a couple of versions back). What you saw in the (old) 'official' video is the old style.

Welcome to the forums 🙂.

Share this post


Link to post
Share on other sites

Thank you for fast you reply.

My first thought was that I did something wrong. For hours I've been looking for the fault. Until I realized that there is no fault. I would never have thought that it should look like this.

Is there a way to get the old style back?

   

Share this post


Link to post
Share on other sites

Hi all,
I am using the blog module, and I love it. Thank you @kongondo.
I have created some posts with featured images and it seems to work fine.
The featured image is displayed above the post-headline.
But if I chose a category and take a view at the blog-category template, the featured image is not displayed at the posts which are belongs to the category.
Probably I forgot something to set?

Thanks in advance for the help.

 

Blog/MarkupBlog: 2.4.2

ProcessWire 3.0.42. 

Share this post


Link to post
Share on other sites

Hello there,

I have added a Repeater field in the blog_post template. But when I go to Quick Post to add a post I don't see the Repeater field in the editor. Am I missing anything?

Share this post


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

I have added a Repeater field in the blog_post template. But when I go to Quick Post to add a post I don't see the Repeater field in the editor. Am I missing anything?

Currently, such 'user-added' fields are not supported in Quick Post. They can only be accessed when you edit the blog page normally. Maybe it's something I need to think about.

Share this post


Link to post
Share on other sites
On 5/29/2018 at 1:42 PM, St3f4n said:

But if I chose a category and take a view at the blog-category template, the featured image is not displayed at the posts which are belongs to the category.
Probably I forgot something to set?

Sorry, @St3f4n. I forgot to answer your question! Use post_large_image option for featured image in a non-summarised (i.e. large/full) post and post_small_image option for featured image in a small/summarised post (e.g. in the default blog-category template file). Does this help?

Welcome to the forums 🙂.

Share this post


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

Currently, such 'user-added' fields are not supported in Quick Post. They can only be accessed when you edit the blog page normally. Maybe it's something I need to think about.

Thanks @kongondo

Is there a way to add a new post other than "quick post'? I can see the Repeater field when I edit an existing post, but how do I access it when creating a new post?

Share this post


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

Is there a way to add a new post other than "quick post'?

Yes, but only via the normal PW page tree.  Posts are just PW pages that use the template blog-post. I don't know what Blog style you used, but just add a child page to whoever the parent of pages using blog-post is. If using style 1 of Blog, then the parent should be the page Posts and it uses the template blog-posts. Adding a child to that parent page should automatically select the template blog-post for the children being added (i.e. individual posts).

Share this post


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

Yes, but only via the normal PW page tree.  Posts are just PW pages that use the template blog-post. I don't know what Blog style you used, but just add a child page to whoever the parent of pages using blog-post is. If using style 1 of Blog, then the parent should be the page Posts and it uses the template blog-posts. Adding a child to that parent page should automatically select the template blog-post for the children being added (i.e. individual posts).

Yes, of course. Thank you @kongondo 🙂

Share this post


Link to post
Share on other sites
On 1/20/2015 at 9:44 AM, kongondo said:

Pretty much, but with a few additions as well. I have created a Gist of the renderPosts() function here:

1

Hi kongondo, I've been trying to make this plugin work for two straight days and I'm not having much luck. 

I'm a bit of a noob when it comes to PHP but I'm usually able to stumble my way through. Can you provide an updated Gist? I'm thinking maybe this one is just too old and won't work with the latest version of your plugin. It seems like copying the renderPosts function to my _func.php file (instead of editing MarkupBlog.module) is the best way to do it so that my changes aren't overwritten when the plugin is updated. I've read this forum over and over, I hate to bother you but the documentation doesn't seem to be complete yet.

[UPDATE: I finally got the featured images to work - didn't realize I had to add the "featured" tag to the image - otherwise, I get an error].

Any chance you can provide a working Gist for each of the other properties? IE: categories, authors, archives, comments, tags, next/prev post, etc. -  I would like to modify them to match my theme in the same way I did with renderPosts.

Share this post


Link to post
Share on other sites
On 5/24/2018 at 3:49 PM, heliumrotator said:

Is there a way to get the old style back?

Not unless you roll back to previous versions or modify the module itself to your liking (being aware that any future updates will wipe out your changes unless you rename your module class and files).

 

On 7/15/2018 at 1:33 AM, Ben Sayers said:

I've read this forum over and over, I hate to bother you but the documentation doesn't seem to be complete yet.

Welcome to the forums @Ben Sayers. Yes, apologies for the documentation. Despite my best intentions, I've never been able to find time to complete it.

On 7/15/2018 at 1:33 AM, Ben Sayers said:

[UPDATE: I finally got the featured images to work - didn't realize I had to add the "featured" tag to the image - otherwise, I get an error].

Again, sorry about this. Docs should be clearer.

On 7/15/2018 at 1:33 AM, Ben Sayers said:

Any chance you can provide a working Gist for each of the other properties? IE: categories, authors, archives, comments, tags, next/prev post, etc. -  I would like to modify them to match my theme in the same way I did with renderPosts.

Not at the moment, I'm afraid. Any reason why you can't/won't use the Blog module itself to render your posts? The demo template files and the present documentation provide examples that should get you going.

Share this post


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

Not at the moment, I'm afraid. Any reason why you can't/won't use the Blog module itself to render your posts? The demo template files and the present documentation provide examples that should get you going.

I guess that's where the documentation would come in handy, I just don't understand how to use the Blog module... If I make changes to MarkupBlog.module, won't they be overwritten if I update your plugin in the future? The demo templates seem to be using the delayed output method which I don't know how to use. When I install PW, I use the "Beginner" option with Direct Output (head/foot includes). 

Share this post


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

If I make changes to MarkupBlog.module, won't they be overwritten if I update your plugin in the future

Yes, they would be overwritten.

2 hours ago, Ben Sayers said:

I guess that's where the documentation would come in handy, I just don't understand how to use the Blog module

I agree, however, the current Blog API documentation is sufficient to get you started, I would think 🙂.

2 hours ago, Ben Sayers said:

The demo templates seem to be using the delayed output method which I don't know how to use

True, but it shouldn't be a problem because the most important thing for you is to use Blog's own methods. E.g. renderPosts(), renderCategories(), etc. They'll still work irrespective of output method. Hence, the reason I pointed you to the examples in the demo template files.

Maybe if you could explain what exactly you need help with?

 

Share this post


Link to post
Share on other sites

I've just updated my PW to 3.0.98 and installed ProCache. Unfortunately now I'm getting a 404 on all blog pages. Also I see ProCache doesn't even list the blog templates.

Any advice?

Share this post


Link to post
Share on other sites
On 8/10/2018 at 3:25 PM, DarsVaeda said:

I've just updated my PW to 3.0.98 and installed ProCache. Unfortunately now I'm getting a 404 on all blog pages. Also I see ProCache doesn't even list the blog templates.

Any advice?

Hi @DarsVaeda,

I am totally clueless about this as I've never used ProCache. Could you disable ProCache and see if we can rule out the upgrade to PW 3.0.98 as the cause? Any errors? (use Tracy Debugger)

Share this post


Link to post
Share on other sites

I actually just found the error this morning. Whilst uploading something went wrong with file rights of the template. When going to the template it actually states so (that it can't access the template and no pages with that template will be displayed).

But on frontend it's just a 404 and no log entry. Would be nice to get that error as log entry so debugging is a bit easier.

Share this post


Link to post
Share on other sites
28 minutes ago, DarsVaeda said:

Whilst uploading something went wrong with file rights of the template.

So problem solved?

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks for this massive module! I've been away from PW for a while and finding this was a true gem.

How would we render just the Categories list with page count next to it without actual blog entries? Similar to /blog/categories/

I have tried setting the limit without much change:

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

//number of posts to list per category
$limit = 0;

//get the categories page. 
$categories = $pages->get('/blog/categories/');

//Render list of categories showing a maximum of 0 posts titles per category
//children = the individual category pages
echo $blog->renderCategories($categories->children, $limit);

I could not see many parameters or examples in the docs.

Thanks so much!

 

Using  ProcessWire 3.0.98 and Blog Module 2.4.2

Edited by biotech
original issue solved

Share this post


Link to post
Share on other sites
On 8/29/2018 at 3:22 AM, biotech said:

Thanks for this massive module! I've been away from PW for a while and finding this was a true gem.

Glad you are finding it useful.

On 8/29/2018 at 3:22 AM, biotech said:

How would we render just the Categories list with page count next to it without actual blog entries? Similar to /blog/categories/

Currently, you can't. You can file it as a feature request though. Please file as an issue here.

Edit: Alternatively, you can do this easily yourself like so:

// get the categories page. 
$categories = $pages->get('/blog/categories/');
$out = '';

// @note: optionally limit these if there's lots of posts >>> children('limit=x')
foreach ($categories->children as $category) {
    $categoryPostsCount = $pages->count("template=blog-post, blog_categories=$category, sort=-blog_date");
    // append category title and link
    $out .= "<h3><a href='$category->url'>$category->title</a></h3>";
    $out .= "<span>$categoryPostsCount</span>";
}


echo $out;

 

On 8/29/2018 at 3:22 AM, biotech said:

I have tried setting the limit without much change:

limit controls number of posts returned. A value of zero means do not apply any limit, hence returns all available posts 🙂.

Edited by kongondo

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks, the "blog/categories/" template makes sense when listing categories over all, my goal above was to generate something short and simple for a side bar listing - your snipped was exactly what I was after, thank you!

Share this post


Link to post
Share on other sites

Hello,

This module is great! However I have some issues with outputting the posts on the blog template. I've published a blog post and tried to output the post on the blog page with the following code:

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

// main content
$content = '';
//$content .= "<h2>{$page->get('blog_headline|title')}</h2>";
//render a limited number of summarised posts
$content .= $blog->renderPosts("limit=5", true);

This code is provided with the module so I suppose it works. However it just returns that there are no posts found. I also tried to find the posts by myself, not using the module with the following line of code:

$posts = wire('pages')->find("template=blog-post, sort=-blog_date");

But if I try to output the page ID or the title, it returns nothing. 

I double checked the post that the page is published (it is published and not hidden) so in theory I have to find the page but no matter what I do, I can't find the posts.

What am I doing wrong here or can someone point me in the right direction?

Share this post


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

This module is great!

Glad you like it.

1 hour ago, Harmen said:

What am I doing wrong here or can someone point me in the right direction?

I'm not sure what's going on. The code looks OK. Do you have debug on? Any errors? Are you able to output other pages? Did you perhaps set some access control on the posts?

By the way, is there any reason you are using wire() inside template files? i.e. $pages->find() and $modules->get() should work just fine without wire() in template files.

Share this post


Link to post
Share on other sites
44 minutes ago, kongondo said:

Do you have debug on? Any errors?

I have TracyDebugger up and running. Doesn't throw any errors.

45 minutes ago, kongondo said:

Are you able to output other pages?

Yes, I can output other pages.

45 minutes ago, kongondo said:

Did you perhaps set some access control on the posts?

The page containing the post has normal right, like every other page. Just like the parent of the post and the blog page itself.

47 minutes ago, kongondo said:

By the way, is there any reason you are using wire() inside template files?

Result of some tests I did. There is no specific reason, was just trying some things because I don't know why it isn't working

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      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. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...