Jump to content
Soma

Images Manager (beta)

Recommended Posts

Yes, it was a Dev image I downloaded last night.  I see there's a newer one from about 6 hours ago, but I haven't touched that one.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian That option isn't used. I used to use this to set it, but removed it.

@cstevensjr hmm I'll also test a little to see if i can reproduce.

Share this post


Link to post
Share on other sites

Yes, it was a Dev image I downloaded last night.  I see there's a newer one from about 6 hours ago, but I haven't touched that one.

can you enable debug mode and see what errors you got?

  • Like 1

Share this post


Link to post
Share on other sites

Adrian is correct. I was referring to the maxfilesize in the module at line 36. If that's not being used then I have no idea what to say. I have several images uploaded successfully through the module but the largest I have been able to get though is 1,067Kb. I have another in there that is 3,396kb that failed through ImagesManager but I was able to upload by going directly to /images/category-1/ create new page and upload by normal pw method.

I will contact my host admin and get the max increased, maybe that will fix it. Still weird.

Share this post


Link to post
Share on other sites

I was able to reproduce issues with latest dev 2.4.2, while working in 2.4.1 still.

Took me couple hours to get around the problems introduced here, but somehow found what the issue was and committed a fix just now.

Part of it is still hackish, and it seems I can't set a custom upload path for InputfieldImage anymore. So it will take now the admin page assets folder for uploading. This results in you don't have to set a temp upload folder (took it out for now).

Also made sure images uploaded get deleted in case of errors.

Added check tomake sure parent catgegory page is selected before uploading.

Added support for showIf dependencies, so the file input will only be shown when a parent is selected, this will only work for 2.3+ (?).

Some minor changes in ImagesManagerParser to account for upcoming new fieldtypes by Ryan.

Meanwhile I found some bug in InputfieldPageListSelectMultiple that makes it not work with inputfield dependencies, I submitted a PR for Ryan. I got it still working with a trick.

So unless there's other changes to image/file inputfields this version should be save for 2.4 and upcomming 2.5. But after all still a proof of concept! :)

  • Like 6

Share this post


Link to post
Share on other sites

Hey Soma,

great module :) Anyway, when i'm uploading images, i get an error:

Pageimage::__construct requires instance of Pageimages

the first image appears in the list, but has no thumbnail...

Also, when browsing to the gallery page, i get a 404.

I created the templates without a file (in the admin cp) to test things, could that be a problem?

Share this post


Link to post
Share on other sites

Works fine, can you tell a little more how you setup things and what version of module and ProcessWire.

Have you set the image field to only 1 image max?

A page with no template file can't be browsed on front-end, if that's what you mean. Or what is gallery page?

Share this post


Link to post
Share on other sites

This is a great module! However I'm having a small issue in 2.4.0. ImageManager is not detecting the pages a photo is placed on. I've tried adding the photo to the page via the provided Imagetag and the TinyMCE inserts and either way the 'Pages' column of the ImageManager only shows the 'search' page, even though I can see the image when I view the page from the front-end. Has anyone else experienced this?

Share this post


Link to post
Share on other sites

Just fixed various issues.

- images now get correctly uploaded to the category selected (this was a bug introduced by myself in the JS).

- fix issue with category filter not showing nested categories correctly

- fix issue with page search link not working correctly, made sure it works also with new 2.5 dev search page using Lister and now uses the textarea fields specified in the module settings.

- changed the category select on images upload to a simple select input, with visually nested categories, for easier handling

- some cleanup

bumped up the version to 0.0.7. https://github.com/somatonic/ImagesManager

  • Like 4

Share this post


Link to post
Share on other sites

Soma, thanks for the update. Would you consider this "beta" at the moment or still alpha?

Share this post


Link to post
Share on other sites

Hello guys

Just committed a larger update to 0.1.0:

lots of cleanup and major changes, but still backwards compatible

  • some fixes to tag parser as there were issues with multi language
  • major rewrite of the image results table to get rid of bundled jQueryDataTable and Fancybox (saves a lot of files and resources that where not necessary)
  • now uses PW MarkupAdminDataTable with custom ajax
  • overall nicer and solider UI integration into PW new admin theme
  • other small improvements and fixes

To update, just replace the module folder with the new one. There's a lot of files deleted, so don't just merge.

So a lot of changes behind the scenes you won't notice much, but also UI wise it's much nicer now. 

It should works nice and I think requires PW 2.4 now. Not tested in 2.3, but mainly I think the use of JqueryMagnicfic Lightbox script (in core 2.4) now for image preview zoom. Otherwise it should work the same.

I removed alpha status, whatever that means. After all it's not meant to be the solution to all problems people might have with PW's media management. It's a nice little helper tool to upload images and create pages from them. In the end it's all saved in a form you could even uninstall ImagesManager and plug your own to handle the data. It can also be seen as a resource. I'm not sure I'll add it to the modules directory.

  • Like 5

Share this post


Link to post
Share on other sites

Made a little update to the ImageManager.module. Haven't recognized something before when testing.

- fixed issue with pagination not working in PW 2.4 when using has_parent=/path/, turned out that has_parent=1009 with ID works. Looks like this has been fixed in latest dev.

Share this post


Link to post
Share on other sites

Soma, Just trying out your module. Looks great.

After playing around with it for a while I noticed a few issues and some things that are shown in the demo but don't appear to work for me.

I am using Processwire 2.5.3 and found the following issues

1. Modal window doesn't open up when editing an image as shown in the screencast.

2. Small thumbnail images are not shown on the page tree as shown in screencast
3. The Drag and top doesn't work for uploading images
 

Share this post


Link to post
Share on other sites

Hi,

I install the module and test it on a 2.6.17 system. I get this error:

Error: Call to a member function count() on null (line 555 /path/to/the/module/ImagesManager.module);

If I change the line 555 and 557 like the following, it works as expected.

                    if($res->myimagefield->count()){
                        $imageUrl = $res->image->first->url;
                        $thumb = $res->myimagefield->first->size(120,0)->url;
                    }

Any clues for me??

Gideon So
 

Share this post


Link to post
Share on other sites

I was pleasantly surprised this module still works on the latest dev PW version 🙂

Well, with one exception: The search assumes there are two more fields present, but the readme doesn't mention them. This results in errors... 

https://github.com/somatonic/ImagesManager/blob/master/ImagesManager.module#L469

Are select_production + select_person page-references? I can't find them in the install instruction or module config.

(I'm fully aware the module has never been officially declared as stable and is now 5 1/2 years old, but some files have been updates 4 months ago, so I thought maybe asking here wouldn't hurt...)

  • Like 1

Share this post


Link to post
Share on other sites

Yeah those search fields are something you wanna change to your needs or remove them. It's still something that is not configurable.

Share this post


Link to post
Share on other sites
On 2/17/2019 at 2:58 PM, dragan said:

I was pleasantly surprised this module still works on the latest dev PW version

You must be kidding 😄 It's a ProcessWire module, you know 😉 

Share this post


Link to post
Share on other sites

Indeed, installed on a 3 0 131 version and it works...
however, only 20 images are saved, no more... I tried with 21, 30, 50 .... but only 20 are being saved, although the minimum default is 50... 

Anyone an idea what could be the problem?

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 Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      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 BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • 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)
       




×
×
  • Create New...