Recently Browsing 0 members
No registered users viewing this page.
we have many projects as pages containing images inside regular image fields and repeater matrix elements. Now we would like to organize our assets.
ProcessWire saves assets with id as folder name and makes separate folders for repeater matrix elements.
Is there a way to collect all assets of one page and export them in a folder with the page name/title?
I think I could achieve this by using the command line wget for this website or maybe by a hook. But maybe someone has done this before. 😉
Hi, on a site I want to disable access to original images and only allow to access thumbnails and watermarked image variations.
A good solution for protecting original images can be found a bit down in this thread:
Old content of this initial post:
By John W.
Summary: If I have a site sitting on a server called testing.com, then on the server change it to mycompany.com, do I have to modify any settings in ProcessWire?
After building several processwire for clients, the one question that I haven't had is about moving a processwire site from an old (temporary) domain to a new domain.
For instance, I typically setup development sites for clients and register a temporary domain (and lock with a password). For instance, thee client can go test.com and get all their content finalized, change wording, add news, swap out photos -- everything to make the site production read.
Next, on my hosting account I can have testing.com renamed to theircompany.com - and change the nameservers.
A simple question here. If I have a hosting company rename the account from testing.com to theircompany.com, change my nameservers whereas going to theircompany.com loads the production site, Is there anything I need to change in the processwire configuration or in the PW database?
In the past, I've just manually copied the site, and fresh-installed PW, and imported the data. Seems like a lot of hassle.
I have a second part question about updating the PW core, however, after consideration I'll post it as a new topic.
Currently Processwire saves the files in the assets directory as follows assets > files > pageid > jpg, doc, mp4, etc.
But what happens I have a project that we developed 2 years ago and currently uses 2 TB of space because the majority of content is video, so I thought that if Processwire could save the files per year, it means that the structure is thus assets > files > year > Pageid > jpg, doc, mp4, etc.
This in order to be able to create an NFS volume for each year and that the volume does not grow in an exaggerated way, since the bigger the volume, the longer the reading and writing times in that volume.