Jump to content
horst

Croppable Image 3

Recommended Posts

12 hours ago, adrian said:

I wonder if it has anything to do with using a string for the version number? I am switching my modules over to string version numbers as well, so would be good to know if that is the problem?

normally, the version compare function (should) work correct with strings like "0.9.17". But I can temporary change it, if this would help. (?)

 

I have updated the repo and changed the version from string '0.9.17' to number 100. Does that change anything?

Share this post


Link to post
Share on other sites

on a local test I added a fake module in the root of the modules directory hirarchy and changed the dependencies hirarchy to make it the main module that installs the three others:

/site/modules/CroppableImage3/
/site/modules/CroppableImage3/CroppableImage3.module **
/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module
/site/modules/CroppableImage3/InputfieldCroppableImage3/InputfieldCroppableImage3.module
/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module

**

Spoiler

<?php namespace ProcessWire;

class CroppableImage3 extends WireData implements Module {
    public static function getModuleInfo() {
        return array(
            'title'    => 'Croppable Image 3 (FAKE-Main-Module)',
            'summary'  => '',
            'author'   => 'Horst Nogajski',
            'version'  => '1.0.0',
            'requires' => 'ProcessWire>=3.0.20, PHP>=5.3.8',
            'installs' => 'FieldtypeCroppableImage3, InputfieldCroppableImage3, ProcessCroppableImage3',
            'icon'     => 'crop'
        );
    }
    public function __construct() {}
    public function init() {}
}

 

 

@adrian: This way it get recognized by the upgrade module. It seems, it has nothing to do with the version is a number or a string.

  • Like 2

Share this post


Link to post
Share on other sites
On 13.2.2017 at 1:59 PM, PWaddict said:

@horst Is it possible to force update the variations when the main crop has been edited without deleting the variations?

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Share this post


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

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Ok thanks for the info.

Let us know if you update the module to be visible on the Upgrades.

Share this post


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

Let us know if you update the module to be visible on the Upgrades.

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Share this post


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

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Take your time to do it right.
I'm using the 0.9.17 version and when I check for updates from the module config I get: Session: Error reported by web service: Unable to find that module

EDIT: I've just manually upgrade to 1.0.0 and the issue still exists.

Share this post


Link to post
Share on other sites

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Share this post


Link to post
Share on other sites
10 hours ago, horst said:

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Shouldn't be say: Session: Current installed version is already up-to-date like on the other modules?

Share this post


Link to post
Share on other sites

@PWaddict: just to clarify: There are two things here:

The modules version is recognized and the module gets correctly updated via the individual update function in the modules config screen!

The module is not recognized by the third party updater module. This is an issue of that updater module!

What I have tried / described above, is to find a way / workaround without needing to contact the author of the third party module "updater" and ask him if he can debug and change the module to recognize modules that are organized like CI3 too. One way I found out to get recognized by the updater, is to use a wrapper module in the root directory of the module. This will work, AFTER everyone has updated to that version. But with the current situation, before everyone has updated to that version, there may be danger to break systems when silently changing the modules hirarchy and dependencies.

  • Like 1

Share this post


Link to post
Share on other sites

I have a recurring prob on PW 3.0.42 and CI 3 v.1.0.0 on PHP 7.0.16

Anytime I try to edit a page which uses an image crop, I get the following error

Quote

Error: Uncaught Error: Class 'ProcessWire\ProcessCroppableImage3' not found in /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module:81
Stack trace:
#0 /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module(58): ProcessWire\InputfieldCroppableImage3->getCropLinks(Object(ProcessWire\Pageimage))
#1 [internal function]: ProcessWire\InputfieldCroppableImage3->___renderButtons(Object(ProcessWire\Pageimage), 'images_e875838f...', 0)
#2 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(374): call_user_func_array(Array, Array)
#3 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/WireHooks.php(549): ProcessWire\Wire->_callMethod('___renderButton...', Array)
#4 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(399): ProcessWire\WireHooks->runHooks(Object(ProcessWire\InputfieldCroppableImage3), 'renderButtons', Array)
#5 /var/www/vhosts/my-domain.co.uk/httpdocs/wi (line 81 of /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged. 

I've refreshed the Modules several times (that worked before) but the problem persisted. I thought perhaps ProCache wasn't helping so I disabled that too temporarily.

Anyone have similar issues ?

Share this post


Link to post
Share on other sites

I think I've found the issue. My uploaded CI folder still have the "-master" name.

Seems to be working now.

Files.png.392fa29b0d54edb87ce7507868fa5447.png

Share this post


Link to post
Share on other sites

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

  • Like 1

Share this post


Link to post
Share on other sites
20 hours ago, adrian said:

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

Hi Adrian

Thanks for the tip.

I normally do install via class name but CI 3 at the time had a more recent version which was only available from GitHub as a ZIP.

At least I think that was the case. Thanks anyway for the help.

Share this post


Link to post
Share on other sites
3 minutes ago, Peter Knight said:

which was only available from GitHub as a ZIP.

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

  • Like 2

Share this post


Link to post
Share on other sites
4 minutes ago, adrian said:

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

Nice - thanks :)

Share this post


Link to post
Share on other sites

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Share this post


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

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Some people do this via HannaCodes or other, self created markup-modules added to the ckeditor boxes.

Something like that:

[[image=theimagename.jpg, crop=thecropname]]

The above could be used by a custom markup module, if you have not installed HannaCode. Assumed you have only one image field on that templates/pages, you have to search for that image in the field and replace that marker with the img tag and src pointing to the crop.

if you have more than one imagefield on a page, you need to add a third param:

[[image=theimagename.jpg, crop=thecropname, fieldname=teaserimages]]

 

If you are willing to get your hands dirty with code and build an own markup module, this is a nice way to learn much about PW and PHP.

Otherwise you can install Hannacode and do it there. Hannacode is a flagship! :)
Pretty usefull for a lot more use cases.

  • Like 2

Share this post


Link to post
Share on other sites

Hello @horst,

First of all, thank you for adapting CroppableImage for ProcessWire 3.x. Modules like this one make ProcessWire into an (even more) robust and flexible option for all kinds of new projects.

I downloaded CroppableImage3 and I was wondering if "free" (variable) width/height is a supported feature in this module (and if not, could it be, pretty please?)

For example, suppose I have this in my field's crop settings:

freeheightcrop,900,0

This would allow the user to create a crop of 900px width and a custom height, so maybe the first image ends up being 900x500, the second one is 900x320, etc. It all depends on the dimensions of the area the user has selected during crop generation.

The calculation would be as follows: get the aspect ratio from the area selected by the user (e.g. a 640x360 area would have a 16:9 aspect ratio). Then, we already know the final width (900px). We calculate the final height using the selected area dimensions and the known final value (i.e. 900 * 360 / 640 = 506.25px --> round down --> 506px final height).

Same idea for width: freewidthcrop,0,900 only this time the width is the variable.

I tried to put freeheightcrop,900,0 into the field configuration and ProcessWire accepted it, but the user's crop won't be saved (it generates a crop that is exactly the same as the original image). Also, when cropping, the upper text that indicates the size of the selection will display "NaNxNaN" until the user selects an area.

Share this post


Link to post
Share on other sites

Hello Horst,

when I'm trying to install the new version I get an error:

( ! ) Notice: Undefined index: sharpening in D:\wamp\www\zaub\site\modules\CroppableImage3\FieldtypeCroppableImage3\FieldtypeCroppableImage3ConfAdaptor.php on line 96
Call Stack
#	Time	Memory	Function	Location
1	0.0040	374752	{main}( )	...\index.php:0
2	0.5650	13487256	ProcessWire\Wire->execute( )	...\index.php:55
3	0.5650	13487528	ProcessWire\Wire->__call( )	...\index.php:55
4	0.5650	13487528	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
5	0.5650	13487904	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
6	0.5650	13487904	ProcessWire\ProcessPageView->___execute( )	...\Wire.php:383
7	0.6430	14965016	ProcessWire\Wire->render( )	...\ProcessPageView.module:205
8	0.6430	14965064	ProcessWire\Wire->__call( )	...\ProcessPageView.module:205
9	0.6430	14965064	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
10	0.6440	14966448	ProcessWire\Wire->renderPage( )	...\WireHooks.php:782
11	0.6440	14966720	ProcessWire\Wire->__call( )	...\WireHooks.php:782
12	0.6440	14966720	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
13	0.6440	14967096	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
14	0.6440	14967096	ProcessWire\PageRender->___renderPage( )	...\Wire.php:383
15	0.6480	14970688	ProcessWire\Wire->render( )	...\PageRender.module:514
16	0.6480	14970736	ProcessWire\Wire->__call( )	...\PageRender.module:514
17	0.6480	14970736	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
18	0.6480	14971576	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
19	0.6480	14971576	ProcessWire\TemplateFile->___render( )	...\Wire.php:380
20	0.6480	14990608	require( 'D:\wamp\www\zaub\site\templates\admin.php' )	...\TemplateFile.php:268
21	0.6490	14991328	require( 'D:\wamp\www\zaub\wire\modules\AdminTheme\AdminThemeDefault\controller.php' )	...\admin.php:13
22	0.6490	15028512	require( 'D:\wamp\www\zaub\wire\core\admin.php' )	...\controller.php:13
23	0.6590	15076312	ProcessWire\Wire->execute( )	...\admin.php:113
24	0.6590	15076360	ProcessWire\Wire->__call( )	...\admin.php:113
25	0.6590	15076360	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
26	0.6590	15076736	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
27	0.6590	15076736	ProcessWire\ProcessController->___execute( )	...\Wire.php:380
28	0.6770	15619400	ProcessWire\Wire->executeEdit( )	...\ProcessController.php:244
29	0.6770	15619448	ProcessWire\Wire->__call( )	...\ProcessController.php:244
30	0.6770	15619448	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
31	0.6770	15619824	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
32	0.6770	15619824	ProcessWire\ProcessModule->___executeEdit( )	...\Wire.php:380
33	0.6810	15622488	ProcessWire\ProcessModule->renderEdit( )	...\ProcessModule.module:1136
34	0.7190	15742248	ProcessWire\Wire->getModuleConfigInputfields( )	...\ProcessModule.module:1213
35	0.7190	15742520	ProcessWire\Wire->__call( )	...\ProcessModule.module:1213
36	0.7190	15742520	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
37	0.7190	15742912	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
38	0.7190	15742912	ProcessWire\Modules->___getModuleConfigInputfields( )	...\Wire.php:383
39	0.7260	15747744	call_user_func:{D:\wamp\www\zaub\wire\core\Modules.php:3582} ( )	...\Modules.php:3582
40	0.7260	15747744	ProcessWire\FieldtypeCroppableImage3::getModuleConfigInputfields( )	...\Modules.php:3582
41	0.7320	15807072	ProcessWire\FieldtypeCroppableImage3ConfAdaptor->getConfig( )	...\FieldtypeCroppableImage3.module:478

 

Can you help me? I've tried to search for it, but found nothing.

ProcessWire 3.0.62 © 2017

 

Many greets!

Share this post


Link to post
Share on other sites

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

Share this post


Link to post
Share on other sites
On 20.5.2017 at 5:38 PM, horst said:

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

I deleted an older version manually and than tried to install the newer version via backend. 

Share this post


Link to post
Share on other sites

I have a serious and mysterious problem with CroppableImage3 module since I upgrade to PW 3.0.62.  Since my local copy of the site works perfectly well, I uploaded it to the production site, along with the database. But, I get this error when accessing a page using CroppableImage3.

Exception: There is no crop setting for the template 'promenade' called 'miniature' (in /home/guyvervi/public_html/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module line 209)

The miniature crop setting IS set. I really does not understand what is going on.

Share this post


Link to post
Share on other sites

I resolved my problem by adding a new crop setting in the my field and changing in my template to the new one... It does not explain why the previous crop setting still works on my local machine... Anyways...

Share this post


Link to post
Share on other sites

Hey, this is a follow up from here:

So, now I have tested every possible combination from ClassNames, filenames and the ModuleName. Every thing will break something when used from an allready installed module with an upgrade through PW.

When I define the main classname in the modules directory as FieldtypeCroppableImage3, the update process fetches the repo, but installs it under site/modules/FieldtypeCroppableImage3, whereas the existing repo stay under site/modules/CroppableImage3! This breaks the whole site, front and backend. The updater doesn't rename the origin repo with a leading dot.

Other solutions tested also broked things.

So, can you please tell me which way to go to bring the module into recognition of the update process?

Share this post


Link to post
Share on other sites

@horst, what if you create a new module file/class in the root of the CroppableImage3 directory named 'CroppableImage3', and that class does nothing apart from auto-install the other classes?

Not ideal of course but might be an okay workaround seeing as you are stuck with the existing directory name.

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
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...