blynx

MarkupProcesswirePhotoswipe

Recommended Posts

Hej,

A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated :)

(Also pull requests are appreciated ūüėȬ†- have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

petersburger.gif.b4f2866466f2d40855977717dd78f484.gif

Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe

.zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip

You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:

<?php
$pwpswp = $modules->get('Pwpswp');
echo $pwpswp->renderGallery($page->nicePictures);

Options are provided like so:

<?php
$galleryOptions = [
    'imageResizerOptions' => [
        'size' => '500x500'
        'quality' => 70,
        'upscaling' => false,
        'cropping' => false
    ],
    'loresResizerOptions' => [
        'size' => '500x500'
        'quality' => 20,
        'upscaling' => false,
        'cropping' => false
    ],
    'pswpOptions' => (object) [
        'shareEl' => false,
        'indexIndicatorSep' => ' von ',
        'closeOnScroll' => false
    ]
];

echo $pswp->renderGallery($page->images, $galleryOptions);

More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe

What do you think? Any ideas, bugs, critique, requests?

cheers
Steffen

  • Like 18

Share this post


Link to post
Share on other sites

This is cool! Thanks a lot. In the near future, I want to port some WP sites with galleries to ProcessWire, so I will definitely give it a try. I put it on my loooooooong todo list :) 

Share this post


Link to post
Share on other sites

Hey Blynx,

Thanks for the nice module :)

Not sure, it's probably just me, but to get this working (local MAMP setup) I had to use the full module class name (MarkupProcesswirePhotoswipe) (not the alias Pwpswp) and the css/javascript etc paths were incorrect , so instead of MarkupPwpswp/path-to-files within the .module file, I had to change these to MarkupProcesswirePhotoswipe/path-to-files 

After this all worked nicely :) 

Thanks again!

  • Like 3

Share this post


Link to post
Share on other sites

Ah! yep, I renamed the module later on - thats a bug I will correct later. Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Update is out: https://github.com/blynx/MarkupProcesswirePhotoswipe

Also removed the Pwpswp class alias, because it was pretty pointless. Processwire does not recognise it as a module and I don't really use static methods in that class.

0.5.1 - 2017/07/06, fixes

removed: Removed pointless shortcut alias class  
fixed: Use of correct module/class name for file paths  
fixed: Configuration instructions for file paths  
other: Updated readme  

  • Like 5

Share this post


Link to post
Share on other sites

Yay, update: https://github.com/blynx/MarkupProcesswirePhotoswipe

Now has some simple 'themes', cooler ones later ...

<?php
$pwpswp = $modules->get('MarkupProcesswirePhotoswipe');
echo $pwpswp->renderGallery($page->nicePictures, ['theme' => 'h-scroller']);

// available themes: plain, flex, h-scroller

0.7 - 2017/07/11, themes

fixed: Size option correctly adopts height value
added: Theme functionality
added: Simple themes 'plain' (previous default), 'flex', 'h-scroller'
other: Updated readme
other: No notice on undefined photoswipe options
other: Refactoring

  • Like 5

Share this post


Link to post
Share on other sites

A great module!  I needed a photo gallery for a few websites and this works fantastic.  Please go ahead and get this module published in the ProcessWire Module Directory.

  • Like 2

Share this post


Link to post
Share on other sites

Hey @blynx,

It is voluntary to make this module only compatible with PHP 7 ?

 

I wanted to give a try to your module for a website I am building right now - using PHP 5.6 - but calling the module with :

$pwpswp = $modules->get('MarkupProcesswirePhotoswipe');
$gallery = $pwpswp->renderGallery($page->gallery, ['theme' => 'masonry']);

give me the following error (due to scalar type arguments) :

errphotoswipe.thumb.png.7cd1f87083994cc25ed28abd0d4207ba.png

 

Anyway, already loving it, thanks for making this module. I am using it with InstagramFeed, IsotopeJS and InfiniteScroll in a custom theme - Masonry - based on the Plain one :

 

MarkupProcesswirePhotoswipe.thumb.gif.dedb2554421ab1df139ef3ef8d5cc1e2.gif

 

  • Like 2

Share this post


Link to post
Share on other sites

Nice, glad you like it!

I will consider this and probably change that - thanks for the feedback!

  • Like 2

Share this post


Link to post
Share on other sites

Ok,

so there is the new version out now which includes a gallery type like the ones in the medium articles.

The whole module has been rewritten and I changed the way the galleries are rendered. Instead of weird template files the galleries are now modules which extend the MarkupPwpswpGallery module. Have a look at the readme for some more info.

Everything should work just fine when updating despite the code changes. I build a gallery module which should ensure compatibility in case anyone was using her/his own template file.

This is the new gallery type ‚ÄěPetersburger H√§ngung‚Äú

petersburger.gif.b4f2866466f2d40855977717dd78f484.gif

 

The inspiration for that type: https://github.com/SiteMarina/guggenheim

The linear partition problem:
http://www8.cs.umu.se/kurser/TDBAfl/VT06/algorithms/BOOK/BOOK2/NODE45.HTM
https://github.com/crispymtn/linear-partition/blob/master/linear_partition.coffee#L11 (coffee script)

Yet, I implemented a simplier and I guess faster algorithm: https://stackoverflow.com/a/6670011/3004669
Maybe I will implement the original algorithm, too, at some point. ... 

 

  • Like 8

Share this post


Link to post
Share on other sites

Updated to the new version and it completely broke my site on my local machine.

see attached image.

Screenshot at Nov 17 21-41-33.png

Share this post


Link to post
Share on other sites

It looks like Tracy bd call. Either install Tracy or remove that bd() in line 471.

Share this post


Link to post
Share on other sites

@JasonS

Noooooo, I was afraid this would happen. It is fixed now! Sorry!
Yep, that was a Tracy bd() call ... as a quick fix you may just remove that line ...

  • Like 1

Share this post


Link to post
Share on other sites

I tried to update my installation with the new updated version and still failed to update safely.

 

Screenshot at Nov 21 16-09-46.png

Share this post


Link to post
Share on other sites

Hm!

This is weird - but it looks like a permissions problem on your side? I guess you can fix this by setting the file/folder permissions.
I couldn't find anything wrong here at my place - is the folder name of the module correct?

How did you install it?

Sorry for the trouble - will have a closer look later the week

Maybe try a fresh installation of the module for now -

Share this post


Link to post
Share on other sites
13 minutes ago, blynx said:

Maybe try a fresh installation of the module for now -

Yes, This worked. Thank you for the great module.

I noticed a small typo just FYI.

 

Screenshot at Nov 21 20-54-44.png

  • Like 1

Share this post


Link to post
Share on other sites

Great module @blynx! Thanks for coding it.

Would you consider making a caption option? I can't seem to find any at the moment.

  • Like 1

Share this post


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

Great module @blynx! Thanks for coding it.

Would you consider making a caption option? I can't seem to find any at the moment.

ah yep, noticed that the captions were missing the other day. Will look into it!

  • Like 2

Share this post


Link to post
Share on other sites

Hi ! Thanks for the module. I tried to install it in a local MAMP setup. But it does not load everything...

Any idea ?

 

Capture d‚ÄôeŐĀcran 2018-05-09 aŐÄ 16.08.22.png

Share this post


Link to post
Share on other sites

Hi!

Mh can't really tell from that screenshot.
One thing I noticed by myself already is, that it doesn't seem to work when caching is turned on - but I can't find the time to work on it right now. : |

Can you have a look into the markup and see what actually was appended, also which actual paths/urls are used which are failing here?

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 bernhard
      @Sergio¬†asked about the pdf creation process in the showcase thread about my 360¬į feedback/survey tool and so I went ahead and set my little pdf helper module to public:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
       
    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported,¬†and page values can't be directly accessed configuration settings are limited to the bare essentials¬†(selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently)¬†supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine¬†for me in one particular project, but hasn't been tested that much, so please tread carefully ‚Äď and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github¬†ūüôā
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180528, v1.0.4 add custom select statement option 180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/