开发者 |
florianziegler
pandulu haptiq picu |
---|---|
更新时间 | 2025年7月3日 21:56 |
PHP版本: | 7.4 及以上 |
WordPress版本: | 6.8 |
版权: | GPLv3 |
版权网址: | 版权信息 |
picu
folder to your /wp-content/plugins
directory.Please take a look at our documentation first. Still having issues? Check out the support forum here on wp.org or reach out via our support page.
Can WordPress send emails? picu uses functions built into WordPress to send emails. If you have any email issues, please make sure your WordPress installation can send emails, e.g., notifications for new comments, resetting passwords, etc. If those don’t work, picu won’t be able to send emails either. Receiving a notification once the client has approved a collection An email will be sent to you, announcing that the client has approved a collection. This email will be sent to the email address specified in your user profile. In the WordPress Admin go to “Users > Your Profile” to see/change that address. Make sure it is correct and working, otherwise you won’t receive any notifications! Changing the FROM name and address In case picu emails end up in the client’s SPAM folder, ask them to add your FROM address (no-reply@ + your domain name) to their allow list. You might also use the email options to change the FROM name and address. There are also filters to do this.
In your WordPress Admin, go to “Settings > Permalinks”. There is no need to “Save Changes”, just visiting the page will flush the rewrite rules so that any changes to the permalink structure will take effect. Sometimes this needs to be done manually, e.g., after changing the language of your website or after a new plugin was activated that introduced new permalinks.
In 90% of cases this issue stems from using some kind of optimization or caching plugin. Please make sure to exclude picu collections from any kind of optimization or caching in the respective plugin’s settings.
By default, we hide all images in the Media Library. Sometimes, third party plugins tamper with the way image uploads are connected to their parent post. If that connection between image and collection is lost, picu can’t filter its images from appearing in the library.
This is intentional. 🙂 We wanted to separate the images that you use in a picu collection from the images you use on your website, thereby keeping you from accidentally using an image from a collection in a blog post or in your portfolio. The media library would get completely crammed and confusing having hundreds, or in some cases thousands, of (temporary) images in there. picu also cleans up behind itself: When you delete a collection, all images are deleted from the server automatically. (You can see how using an image elsewhere on the site would become a problem here.)
There are lots of additional options to configure and extend picu by using a little bit of code. To get started, have a look at our developers page. Also, please have a look at our examples page with lots of working code snippets.
Yes! picu has been translated by our kind users into many different languages. If not available already, you can contribute translations by going to translate.wordpress.org. Choose your language, then click on "Stable (latest release)" and start adding translations. (Please note that you need a WordPress.org account to add translations.) BTW: We are looking for people to help us translate our Pro modules as well. If you are interested in a free license, get in touch.
Awesome! We are always open to feature suggestions and are always interested to learn about photographers' workflows. Please get in touch!
class
to the email parts array, so individual styling is possible. Used it to add a box around the expiration info in client emails.
* Added: Added a new meta
field to history events, now saving the approval form values inside the history.
* Changed: Duplication of just the selected/not selected images is now possible for open collections. (Previously this option was only available for closed collections.)
* Changed: Updated wording of the HTML email setting.
* Changed: Updated the warning modal content, depending on the status of individual clients.
* Changed: Separated compatibilty functions into separate files for easier access and development.
* Changed: Started disabling auto loading of picu options.
* Changed: Improved styling of picu UI in the WP Admin.
2.3.4
Release Date: 2024-07-11
* Added: When adding a client, after a collection has been published, it is now possible to also enter their name. Plus, you can now decide via a checkbox, if an email should be sent to the new client.
* Added: History meta box empty state, if there are no events yet.
* Changed: The proof file prefix is now "selection-" (was "approved-collection-" previously), to reflect better the new open nature of collections.
* Changed: Improve clarity of history events: Using „Published“ instead of „Sent manually“.
* Changed: Removed current php user from our debug info, because it could interfer with some hosting providers and we don't need that information anyway.
* Bugfix: Fixed a bug where after duplicating a collection, the wrong modified date could be displayed.
* Bugfix: Remove environment type check in order to display the history meta box.
* Bugfix: Adjust collection title line-height, so it is not cut-off at the bottom.
* Bugfix: Allow very long collection titles to break in the collection overview in WordPress Admin.
2.3.3
Release Date: June 28th, 2024
* Enhancements
* Handle „private“ post status better, which is not supported with picu collections
* New and updated Pro banners, with more helpful links to our website
* Compatibility with picu Pro 1.4.4
* Pro-related Enhancements
* When re-publishing a delivery collection (eg. after editing the description), the zip file will only be re-created, if the images changed (Thx Alexandru N.)
* Pro-related Bugfixes
* Fix an issue, where the checkmark icon would disappear, when selecting an image on a mobile device – if you had a custom primary color set (Thx Amanda)
2.3.2
Release Date: June 25th, 2024
* Bugfixes
* picu Pro compatibality update
2.3.1.1
Release Date: June 9th, 2024
* Bugfixes
* Fix a possible redirect loop, for manually sent collections
2.3.1
Release Date: June 8th, 2024
* Bugfixes
* Fix a bug where previewing a collection could cause a redirect loop (Thx Torsten V.)
* Fix a bug where the "View Collection" link could be show twice in the admin bar
* Fix positioning of admin notices on the picu settings page
2.3.0
Release Date: June 4th, 2024
* Enhancements
* Collections no longer close automatically, instead you can now manually close a collection or use the expiration feature to have it close after a set amount of time
* New and improved collection overview
* Collection status has been simplified to „open“ and „closed“
* New client column that shows the status of each client
* The image count column is back!
* The proof file can now be downloaded at any time
* Updated status meta box, which shows the most important information about the collection
* New (optional) collection history meta box, which gives you get a detailed look at what is happening with your collection
* When reopening or editing a collection, the status of all of the existing client selections will stay intact
2.2.0
Release Date: March 13th, 2024
* Enhancements
* Collections can now be closed manually
* Collection images can now be ordered by create date (the images must contain the necessary IPTC/EXIF data in order for this to work)
* Updated proof file content: Using markdown headlines, better data structure
* The proof file is now also available for expired/closed collections
* Clients who did not finally approve a collection will now be displayed as "failed" if the collection expires or is closed manually
* More fine-grained events will be displayed in the "Last Modified" column of the collection overview
* Improved button layout for downloading the proof file and copying the image filenames
* If a collection is set to expire, the expiration time is now shown in the email to the client (before only the date was displayed)
* Bugfixes
* Fix an issue where the proof file could contain the wrong approval time for individual clients
* Fix an issue where the collection title would not be displayed in the WordPress admin, if the collection was expired
2.1.4
Release Date: February 20th, 2024
* Bugfixes
* Revert to original post status when restoring collections from trash
* Fix an issue where switching the default image processor would cause an error
* Fix an issue where an empty approval message would be shown
2.1.3
Release Date: January 29th, 2024
* Bugfixes
* Fixes a bug where a scrollbar would be visible below the collection title in some browsers
* Fixes a bug where the approval message would not be saved
2.1.1
Release Date: December 21st, 2023
* Bugfixes
* Remove surpurflous database queries to increase performance (Thx Daniele D.)
* Improved rendering of collections on smaller screens
* Fixes for Pro users: comments get a bit more room & the photographer logo in emails is now bigger
2.1.0
Release Date: December 8th, 2023
* Enhancements
* The approval comment is now again part of the approved collection email notification
* For Pro subscribers: All approval fields will be included in the approval email for collections with one recipient
2.0.3
Release Date: November 29th, 2023
* Bugfixes
* Fix a bug where redirecting after approval would not work correctly
* Fix a possible PHP warning after a collection has been approved
2.0.2
Release Date: November 21st, 2023
Please note: picu 2.0+ is only compatible with picu Pro 1.1.0 and higher. Learn more