adrian

Migrator

Recommended Posts

@manlio - sorry for the rough first experience with Migrator - any chance you could PM me the zip package you are trying to import?

@Septhiroth - good catch, and yes, PR's are always very welcome - thanks :)

  • Like 1

Share this post


Link to post
Share on other sites

Adrian you don't have to be sorry! Instead thanks for you effort that I know is great and thanks for support. I send you a message with the zip file.

Ciao

Share this post


Link to post
Share on other sites

Just wanted to post a little warning here.

@SteveB PM'd me with an issue he was have with a relatively complex migration. I initially tested on PW 2.5.3 and everything worked flawlessly in several tests, which is great!

But then testing on the latest PW dev there were some significant issues with certain pages not ending up where they were supposed to be, so I need to look into this in more detail, but just wanted to remind you guys on dev to be careful until I figure this out. Not sure what version of PW this started happening with.

  • Like 1

Share this post


Link to post
Share on other sites

An update on the status of Migrator with respect to current dev version of PW (soon to be stable 2.7) would be much appreciated!

Reading this thread I get the sense that, understandably, there are plenty of edge case problems but do we know what's working reliably on recent PW installations? I'm piecing together a staging-to-live strategy for a site where most of the content will be imported from non-PW data sources (including images).

One way is to first delete those pages which get imported from the external data, then use the reliable method of copying over the whole database, the site folders (templates and modules) and any necessary config, .htaccess, index.php tweaks. This keeps users, roles, user/role mapping and template access settings intact.

I feel as though a "cleaner" way would be to explicitly export/import users, roles, user/role mapping and all template settings. Then I could start with a clean PW install. How much of that might Migrate be able to do these days?

Thanks,

Steve

Share this post


Link to post
Share on other sites

Hi Steve,

I am sorry, I haven't had time to work on Migrator for a while now. It is definitely not abandoned - I just need to find a good chunk of time to revisit a few things regarding Page fields and sort out remaining bugs. I will try to take a look at this sometime soonish.

Regarding the last part of your question - Migrator currently creates new users/roles if the creator/modifier of the imported content was created by a user that doesn't exist on the new site. The problem of course is migrating the user's password - is this a requirement in your scenario? All the template settings etc are all handled completely by Migrator.

I also have some aspirations to take Migrator a step further and allow it to connect directly to another site and sync changes, but if this happens it will be some time away and will likely be a commercial version of Migrator.

I am not sure if that really helps you at the moment. I am away for the next few days and busy for the week or so after that, but might see if I can get a new version out before the end of the month - but no promises :)

  • Like 4

Share this post


Link to post
Share on other sites

Thanks Adrian. I'm just trying to figure out what it might be relied upon to do in it's current, work-in-progress, state. For this project I can probably just build users from scratch each time. The password issue can be dealt with.

Share this post


Link to post
Share on other sites

Hi Adrian

this module looking very good! But i have some strange problems. So export on page tree from one site (whole tree; pw 3.0.15) wich works very well. And I want to import it on PW 3.0.18 System. wich seems to work also well. Templates and fields are created. I also get the info "Created all required templates and fields and imported/edited 140 pages" but if I view on the page tree nothing is there. I dont see any errors. So maybe its because of the 3.0.x version. Do you have tested it with the 3.0.x version?

What else could I try?

Share this post


Link to post
Share on other sites

@jensweigel - please try this commit: https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

I also have a PR from @jlahijani (https://github.com/adrianbj/ProcessMigrator/pull/5) which may also take care of the problem. I will try to make some time today to review his changes and the last working commit noted above and get a new version out.

Share this post


Link to post
Share on other sites

Seems like Migrator has problems with templates that include InputfieldPageTable fields. When importing pages that include this fieldtype, Migrator also creates the pages that are stored inside this fieldtype.

Share this post


Link to post
Share on other sites
4 hours ago, charger said:

Seems like Migrator has problems with templates that include InputfieldPageTable fields. When importing pages that include this fieldtype, Migrator also creates the pages that are stored inside this fieldtype.

HI @charger - isn't that the desired behavior? If it didn't create the pages that belong to the Page Table then you wouldn't be migrating all the content. Maybe I am misunderstanding though?

Share this post


Link to post
Share on other sites

You’re of course right. The problem is that the pages that reside in these InputfieldPageTable fields will be moved out of their previous (nested) structure and are applied (flat) to the parent one selects during import.

Share this post


Link to post
Share on other sites

I'm trying to use this module to get pages to an external translation agency, that uses a translation memory. The multilanguage modules are in use and working fine. [Added English manually to the Dutch (default) site, trying to add French and German automatically.]

What worked fine:

  • Export of all pages as a json file
  • Import of that json file in their translation software
  • Inspection of their translated json file in Atom - looks fine

Then I tried to import their file, and that failed.

  • Append: nothing changed — expected behaviour
  • Overwrite/Replace: shows me this error
Error: Uncaught Error: Call to a member function setLanguageValue() on null in /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module:1441
Stack trace:
#0 /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module(161): ProcessMigrator->processImportForm2(Object(ProcessWire\InputfieldForm))
#1 /Applications/MAMP/htdocs/wire/core/Wire.php(374): ProcessMigrator->___executeImport()
#2 /Applications/MAMP/htdocs/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___executeImpor...', Array)
#3 /Applications/MAMP/htdocs/wire/core/Wire.php(402): ProcessWire\WireHooks->runHooks(Object(ProcessMigrator), 'executeImport', Array)
#4 /Applications/MAMP/htdocs/wire/core/ProcessController.php(244): ProcessWire\Wire->__call('executeImport', Array)
#5 /Applications/MAMP/htdocs/wire/core/Wire.php(374): ProcessWire\ProcessController->___execute()
#6 /Applications/MAMP/htdocs/wire/core/WireHooks.php(698): ProcessWire\Wire->_ (line 1441 of /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module) 

 

Share this post


Link to post
Share on other sites

I did some further testing.

When I choose Replace instead of Overwrite, all texts with multi-language input are deleted, including default language.

I even tested with exporting to a zip, and then importing that same zip. Same errors. So, it's not related to what the translator could have done with the files.

Share this post


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

Inspection of their translated json file in Atom - looks fine

Just because it looks like valid json doesn't mean it's in the correct format for Migrator.

But could you please make sure you are using this version of Migrator: https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

It is two commits behind, but it looks like some bugs were introduced since that commit.

As an update on this project. I still do want to get back to it, but I am now going to wait until Ryan completes all the new core page migration tools so I can use those new core methods. Will wait and see exactly what functionality he builds and extend from there if needed.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, Adrian. Very grateful. 
That version doesn't spit out the error I mentioned.

I get another error now: the Home-page gets added as a new page on import, but that's something I can manually adjust.

Looking forward to updates on exporting/importing/migrating.
Loving Processwire so far, and it's only early days!

Share this post


Link to post
Share on other sites

Will this module be updated for PW 3.x?

I have problems like: "Call to a member function setLanguageValue() on a non-object"

Line 1441 of ProcessMigrator.module.

Is there a similar working tool for copying local pages (trees) to remote?

Thank you.

Share this post


Link to post
Share on other sites

Hi @theo - this looks related to (https://github.com/adrianbj/ProcessMigrator/issues/4).

What commit are you using? Please try this one (two back from current) - https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

I will likely recreate this module in the future after Ryan fully implements the new core methods for exporting/importing pages

http://processwire.com/blog/posts/roadmap-2017/

Quote

Tools for exporting and importing of pages. We've got some nice built-in tools for importing and exporting of templates and fields, but not yet for pages. Over the coming year, I'm hoping to add page import/export as well. I'd like to be able to copy/paste a page or group of pages from one server to another.

 

I just don't have the time to put more effort into the current iteration of this, especially given that future versions should make use of the new core features.

  • Like 2

Share this post


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

 

Hi @Adrian

Yes, 0.6.9 seems to work better than 0.7.0

Thank you!

  • Like 1

Share this post


Link to post
Share on other sites

Hello all. 

After playing with PW for some time now and having a heavy WP website, I decided to look this morning about a way to migrate WP to PW (how ironically it sounds ;) ). And here I am - trying out the MigratorWordpress.

Downloaded the XML file (18Mb containing around 700 posts and over 5000 comments). Uploaded the file and started the import. At the end, everything went smooth and I was suggested to check the imported pages. I was not surprised to find out that the import only did find some pages but not the posts itself (no offense to the authors for sure). This issue was not new to me as I was trying to import WP to ModX long time ago and ran into it as well. So what helped me at that time was a simple WP plugin caled Post Type Switcher that allowed me to move all the WP posts from custom post type to the default WP posts. After that I was able to import posts and comments almost flawlessly (I say almost, as I still had to go around the posts and clear the short-tag leftovers etc. - which is not an issue). 

As of now, I am testing the same approach to see if that would work again and will report back. My biggest concern is to have the posts properly imported and attached to their comments. I do not mind loosing keywords etc. as I am planning on redoing every post manually but moving comments that way would be an overkill ;)

Share this post


Link to post
Share on other sites

Ok. All custo post types were converted back to standard wordpress posts and then the XML was exported using the Tools->Export feature. Then installed the both required modules - ProcessMigrator and MigratorWordpress and tried to import the posts into a newly created page called Import. Unfortunately it did not work with PW 2.8.5 and blows an error:

Error: Call to a member function get() on a non-object (line 1450 of C:\OpenServer\domains\recipemagician.pw\site\modules\ProcessMigrator\ProcessMigrator.module) 

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

I tried with the latest 3.0.55 and it did not work either. Is there any specific version to try with that would seemed to work?

Share this post


Link to post
Share on other sites

Thanks Adrian. Testing it now. Would you recommend using 3.X or 2.X?

Share this post


Link to post
Share on other sites
2 minutes ago, MilenKo said:

Thanks Adrian. Testing it now. Would you recommend using 3.X or 2.X?

Migrator and MigratorWordpress were written for 2.x so that might be safer, but I have used Migrator itself with 3.x without any issues, but I haven't used MigratorWordpress with 3.x yet.

FYI - as I mention above:

On 1/11/2017 at 7:07 AM, adrian said:

As an update on this project. I still do want to get back to it, but I am now going to wait until Ryan completes all the new core page migration tools so I can use those new core methods. Will wait and see exactly what functionality he builds and extend from there if needed.

 

Share this post


Link to post
Share on other sites

Adrian, that is understandable considering the amount of work and changes that needs to be applied. Will try now with 2x version and see how it goes. In regards to the shorcodes, this was one of the things that initially pushed me to search for another CMS. I used a few themes before starting to deal with the next one on my own and with every theme change there were more and more shortcodes used. After the latest theme some were dropped out so it got ugly. That is why all I care is to have the comments and posts imported properly. The rest I will setup up/change/clean myself as a part of the process and learning curve ;)

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 Noel Boss
      Page Query Boss
      Build complex nested queries containing multiple fields and pages and return an array or JSON. This is useful to fetch data for SPA and PWA.
      You can use the Module to transform a ProcessWire Page or PageArray – even RepeaterMatrixPageArrays – into an array or JSON. Queries can be nested and contain closures as callback functions. Some field-types are transformed automatically, like Pageimages or MapMarker.
      Installation
      Via ProcessWire Backend
      It is recommended to install the Module via the ProcessWire admin "Modules" > "Site" > "Add New" > "Add Module from Directory" using the PageQueryBoss class name.
      Manually
      Download the files from Github or the ProcessWire repository: https://modules.processwire.com/modules/page-query-builder/
      Copy all of the files for this module into /site/modules/PageQueryBoss/ Go to “Modules > Refresh” in your admin, and then click “install” for the this module. Module Methods
      There are two main methods:
      Return query as JSON
      $page->pageQueryJson($query); Return query as Array
      $page->pageQueryArray($query); Building the query
      The query can contain key and value pairs, or only keys. It can be nested and 
      contain closures for dynamic values. To illustrate a short example:
      // simple query: $query = [ 'height', 'floors', ]; $pages->find('template=skyscraper')->pageQueryJson($query); Queries can be nested, contain page names, template names or contain functions and ProcessWire selectors:
      // simple query: $query = [ 'height', 'floors', 'images', // < some fileds contain default sub-queries to return data 'files' => [ // but you can also overrdide these defaults: 'filename' 'ext', 'url', ], // Assuming there are child pages with the architec template, or a // field name with a page relation to architects 'architect' => [ // sub-query 'name', 'email' ], // queries can contain closure functions that return dynamic content 'querytime' => function($parent){ return "Query for $parent->title was built ".time(); } ]; $pages->find('template=skyscraper')->pageQueryJson($query); Keys:
      A single fieldname; height or floors or architects 
      The Module can handle the following fields:
      Strings, Dates, Integer… any default one-dimensional value Page references Pageimages Pagefiles PageArray MapMarker FieldtypeFunctional A template name; skyscraper or city
      Name of a child page (page.child.name=pagename); my-page-name A ProcessWire selector; template=building, floors>=25
      A new name for the returned index passed by a # delimiter:
      // the field skyscraper will be renamed to "building": $query = ["skyscraper`#building`"]  
      Key value pars:
      Any of the keys above (1-5) with an new nested sub-query array:
      $query = [ 'skyscraper' => [ 'height', 'floors' ], 'architect' => [ 'title', 'email' ], ]  
      A named key and a closure function to process and return a query. The closure gets the parent object as argument:
      $query = [ 'architecs' => function($parent) { $architects = $parent->find('template=architect'); return $architects->arrayQuery(['name', 'email']); // or return $architects->explode('name, email'); } ] Real life example:
      $query = [ 'title', 'subtitle', // naming the key invitation 'template=Invitation, limit=1#invitation' => [ 'title', 'subtitle', 'body', ], // returns global speakers and local ones... 'speakers' => function($page){ $speakers = $page->speaker_relation; $speakers = $speakers->prepend(wire('pages')->find('template=Speaker, global=1, sort=-id')); // build a query of the speakers with return $speakers->arrayQuery([ 'title#name', // rename title field to name 'subtitle#ministry', // rename subtitle field to ministry 'links' => [ 'linklabel#label', // rename linklabel field to minlabelistry 'link' ], ]); }, 'Program' => [ // Child Pages with template=Program 'title', 'summary', 'start' => function($parent){ // calculate the startdate from timetables return $parent->children->first->date; }, 'end' => function($parent){ // calculate the endate from timetables return $parent->children->last->date; }, 'Timetable' => [ 'date', // date 'timetable#entry'=> [ 'time#start', // time 'time_until#end', // time 'subtitle#description', // entry title ], ], ], // ProcessWire selector, selecting children > name result "location" 'template=Location, limit=1#location' => [ 'title#city', // summary title field to city 'body', 'country', 'venue', 'summary#address', // rename summary field to address 'link#tickets', // rename ticket link 'map', // Mapmarker field, automatically transformed 'images', 'infos#categories' => [ // repeater matrix! > rename to categories 'title#name', // rename title field to name 'entries' => [ // nested repeater matrix! 'title', 'body' ] ], ], ]; if ($input->urlSegment1 === 'json') { header('Content-type: application/json'); echo $page->pageQueryJson($query); exit(); } Module default settings
      The modules settings are public. They can be directly modified, for example:
      $modules->get('PageQueryBoss')->debug = true; $modules->get('PageQueryBoss')->defaults = []; // reset all defaults Default queries for fields:
      Some field-types or templates come with default selectors, like Pageimages etc. These are the default queries:
      // Access and modify default queries: $modules->get('PageQueryBoss')->defaults['queries'] … public $defaults = [ 'queries' => [ 'Pageimages' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'focus', ], 'Pagefiles' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'filesize', 'filesizeStr', 'hash', ], 'MapMarker' => [ 'lat', 'lng', 'zoom', 'address', ], 'User' => [ 'name', 'email', ], ], ]; These defaults will only be used if there is no nested sub-query for the respective type. If you query a field with complex data and do not provide a sub-query, it will be transformed accordingly:
      $page->pageQueryArry(['images']); // returns something like this 'images' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'focus'=> [ 'top', 'left', 'zoom', 'default', 'str', ] ]; You can always provide your own sub-query, so the defaults will not be used:
      $page->pageQueryArry([ 'images' => [ 'filename', 'description' ], ]); Overriding default queries:
      You can also override the defaults, for example
      $modules->get('PageQueryBoss')->defaults['queries']['Pageimages'] = [ 'basename', 'url', 'description', ]; Index of nested elements
      The index for nested elements can be adjusted. This is also done with defaults. There are 3 possibilities:
      Nested by name (default) Nested by ID Nested by numerical index Named index (default):
      This is the default setting. If you have a field that contains sub-items, the name will be the key in the results:
      // example $pagesByName = [ 'page-1-name' => [ 'title' => "Page one title", 'name' => 'page-1-name', ], 'page-2-name' => [ 'title' => "Page two title", 'name' => 'page-2-name', ] ] ID based index:
      If an object is listed in $defaults['index-id'] the id will be the key in the results. Currently, no items are listed as defaults for id-based index:
      // Set pages to get ID based index: $modules->get('PageQueryBoss')->defaults['index-id']['Page']; // Example return array: $pagesById = [ 123 => [ 'title' => "Page one title", 'name' => 123, ], 124 => [ 'title' => "Page two title", 'name' => 124, ] ] Number based index
      By default, a couple of fields are transformed automatically to contain numbered indexes:
      // objects or template names that should use numerical indexes for children instead of names $defaults['index-n'] => [ 'Pageimage', 'Pagefile', 'RepeaterMatrixPage', ]; // example $images = [ 0 => [ 'filename' => "image1.jpg", ], 1 => [ 'filename' => "image2.jpg", ] ] Tipp: When you remove the key 'Pageimage' from $defaults['index-n'], the index will again be name-based.
       
      Debug
      The module respects wire('config')->debug. It integrates with TracyDebug. You can override it like so:
      // turns on debug output no mather what: $modules->get('PageQueryBoss')->debug = true; Todos
      Make defaults configurable via Backend. How could that be done in style with the default queries?
    • By daniels
      General
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      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 You can find it here: https://github.com/danielstieber/SubscribeToMailchimp
      Let me know what you think and if I should add it to the Modules Directory.
      Setup
      Log into your Mailchimp account and go to  Profile > Extras > API Keys. If you don't have an API Key, create a new one. Copy your API Key and paste it in the module settings (Processwire > Modules > Site > SubscribeToMailchimp). Back in Mailchimp, go to the list, where you want your new subscribers. Go to Settings > List name and defaults. Copy the List ID an paste it in to the module settings.
      Usage
      To use the module, you need to load it into your template:
      $mc = $modules->get("SubscribeToMailchimp"); Now you can pass an email address to the module and it will try to edit (if the user exists) or create a new subscriber in your list.
      $mc->subscribe('john.doe@example.com'); You can also pass a data array, to add additional info.
      $mc->subscribe('john.doe@example.com', ['FNAME' => 'John', 'LNAME' => 'Doe']); You can even choose an alternative list, if you don't want this subscriber in your default list.
      $mc->subscribe('john.doe@example.com', ['FNAME' => 'John', 'LNAME' => 'Doe'], 'abcdef1356'); // Subscribe to List ID abcdef1356 If you want to unsubscribe a user from a list, you can use the unsubscribe method.
      $mc->unsubscribe('john.doe@example.com'); // Unsubscribe john.doe@example.com from the default list $mc->unsubscribe('john.doe@example.com', 'abcdef1356'); // Unsubscribe john.doe@example.com from the list abcdef1356 If you want to permantly delete a user, you can call the delete method. Carefully, this step cannot be undone
      $mc->delete('john.doe@example.com'); // Permanently deletes john.doe@example.com from the default list $mc->delete('john.doe@example.com', 'abcdef1356'); // Permanently deletes john.doe@example.com from the list abcdef1356  
      Important Notes
      This module does not do any data validation. Use a sever-sided validation like Valitron Make sure that you have set up your fields in your Mailchimp list. You can do it at Settings > List fields and *|MERGE|* tags Example
      Example usage after a form is submitted on your page:
      // ... validation of form data $mc = $modules->get("SubscribeToMailchimp"); $email = $input->post->email; $subscriber = [ 'FNAME' => $input->post->firstname, 'LNAME' => $input->post->lastname, ]; $mc->subscribe($email, $subscriber);  
      Troubleshooting
      In case of trouble check your ProcessWire warning logs.
      I can't see the subscriber in the list
      If you have enabled double opt-in (it is enabled by default) you will not see the subscriber, until he confirmed the subscription in the email sent by Mailchimp
      I get an error in my ProccessWire warning logs
      Check if you have the right List ID and API Key. Check if you pass fields, that exist in your list. Check if you pass a valid email address. Go to Mailchimps Error Glossary for more Information
      How To Install
      Download the zip file at Github or clone directly the repo into your site/modules If you downloaded the zip file, extract it in your sites/modules directory. You might have to change the folders name to 'SubscribeToMailchimp'. Goto the modules admin page, click on refresh and install it  
      Changelog
      0.0.2
      Note: You can update safely from 0.0.1 without any changes in your code
      New Features
      Added 'Unsubscribe' method $mc->unsubscribe($email, $list = "") Added 'Delete' method $mc->delete($email, $list = "") Bug Fixes and compatibility changes
      Removed type declarations to be compatible with PHP 5.1+* (thanks to wbmnfktr) Other
      Changed the way, the base url for the api gets called *I have only tested it with PHP 7.x so far, so use on owners risk
    • By BitPoet
      As threatened in the Pub sub forum in the "What are you currently building?" thread, I've toyed around with Collabora CODE and built file editing capabilities for office documents (Libre-/OpenOffice formats and MS Office as well as a few really old file types) into a PW module.
      If you are running OwnCloud or NextCloud, you'll perhaps be familiar with the Collabora app for this purpose.
      LoolEditor
      Edit office files directly in ProcessWire
      Edit your docx, odt, pptx, xlsx or whatever office files you have stored in your file fields directly from ProcessWire's page editor. Upload, click the edit icon, make your changes and save. Can be enabled per field, even in template context.
      Currently supports opening and saving of office documents. Locking functionality is in development.
      See the README on GitHub for installation instructions. You should be reasonably experienced with configuring HTTPS and running docker images to get things set up quickly.
      Pull requests are welcome!
      Here is a short demonstration:

    • By Robin S
      An Images field allows you to:
      Rename images by clicking the filename in the edit panel or in list view. Replace images, keeping metadata and filename (when possible) by dropping a new image on the thumbnail in the edit panel. Introduced here. But neither of these things is possible in File fields, which prompted this module. The way that files are renamed or replaced in this module is not as slick as in the Images field but it gets the job done. The most time-consuming part was dealing with the UI differences of the core admin themes. @tpr, gives me even more respect for the work that must go into AdminOnSteroids.
      Most of the code to support the rename/replace features is already present in InputfieldFile - there is just no UI for it currently. So hopefully that means these features will be offered in the core soon and this module can become obsolete.
       
      Files Rename Replace
      Allows files to be renamed or replaced in Page Edit.

      Usage
      Install the Files Rename Replace module.
      If you want to limit the module to certain roles only, select the roles in the module config. If no roles are selected then any role may rename/replace files.
      In Page Edit, click "Rename/Replace" for a file...
      Rename
      Use the text input to edit the existing name (excluding file extension).
      Replace
      Use the "Replace with" select to choose a replacement file from the same field. On page save the file will be replaced with the file you selected. Metadata (description, tags) will be retained, and the filename also if the file extensions are the same.
      Tip: newly uploaded files will appear in the "Replace with" select after the page has been saved.
       
      https://github.com/Toutouwai/FilesRenameReplace
      http://modules.processwire.com/modules/files-rename-replace/
    • By d'Hinnisdaël
      So I decided to wade into module development and created a wrapper module around ImageOptim, a service that compresses and optimizes images in the cloud. ImageOptim currently handles JPG, PNG and GIF files and, depending on the settings you use, shaves off between 15% and 60% in filesize. Great for bandwidth and great for users, especially on mobile.
      This module handles the part of uploading images to ImageOptim via their official API, downloading the optimized version and storing it alongside the original image.
       

       
      Download & Info
      GitHub / Module directory / Readme / Usage
       
      Why ImageOptim?
      There are other image optimization services out there, some of them free, that have outstanding ProcessWire modules. A few things make ImageOptim the best tool for most of my customers: It's not free, i.e. it will probably be around for a while and offers support. However, it's cheaper than some of the bigger competitors like Cloudinary. And it does PNG compression better than any of the free services out there, especially those with alpha channels.
       
      Installation
      Install the module like any other ProcessWire module, by either copying the folder into your modules folder or installing it via the admin. See above for downloads links on GitHub and in the module directory.
       
      Requirements
      To be able to upload images to the service, allow_url_fopen must be set on the server. The module will abort installation if that's not the case.
      I have only tested the module on ProcessWire 3.x installations. I don't see why it shouldn't work in 2.x, if anyone wants to try it out and report back.
       
      ImageOptim account
      To compress images, you first need to sign up for an ImageOptim account. They offer free trials to try the service.
       
      Usage (manual optimization)
      Images can be optimized by calling the optimize() method on any image. You can pass an options array to set ImageOptim API parameters.
      $image->size(800,600)->optimize()->url $image->optimize(['quality' => 'low', 'dpr' => 2]) // Set quality to low and enable hi-dpi mode
      Automatic optimization
      The module also has an automatic mode that optimizes all image variations after resizing. This is the recommended way to use this module since it leaves the original image uncompressed, but optimizes all derivative images.
      $image->size(800,600)->url // nothing to do here; image is optimized automatically
      To change compression setting for single images, you can pass an options array along with the standard ImageResizer options. Passing false disables optimization.
      $image->size(800, 600, ['optimize' => 'medium']) $image->size(800, 600, ['optimize' => ['quality' => 'low', 'dpr' => 2]]) $image->size(800, 600, ['optimize' => false])
      For detailed usage instructions and all API parameters, see the usage instructions on GitHub.
       
      Filenames
      Optimized images will be suffixed, e.g. image.jpg becomes image.optim.jpg. You can configure the suffix in the module settings.
       
      Roadmap
      Asynchronous processing. Not really high on the list. Image variations need to be created anyway, so waiting a few seconds longer on first load is preferable to adding complexity to achieve async optimization. Optimize image variations created by other modules. CroppableImage comes to mind. I don't use any of these, so if somebody wants to help out and submit a pull request — all for it! Add a dedicated page in the setup menu with a dashboard and detailed statistics. ImageOptim's API is very barebones for now, so not sure if that's feasible or even necessary.
      Stability
      I've been using this module on production sites for some time now, without hiccups. If you do notice oddities, feel free to comment here or investigate and submit PRs.