Claudio Rimann

Hi Wilfried

We use the native uploader of WP under the hood to process the uploaded images.

When images are uploaded, they get automatically resized to predefined smaller sizes for use in various layouts.

This is recommended for performance and is done to avoid loading *all* the images of a gallery in full-res, which could make the gallery very slow, especially when using many images.

If your goal is to allow clients to download images from a collection, there is also a download option in our pro version, which allows them to download full sizes while still using smaller sizes in the layout for optimal performance.

That being said, there *is* a filter to switch the image sizes generation off, if you know what you are doing and are aware of the consequences: https://picu.io/docs/developers/filter-examples/do-not-generate-picus-custom-images-sizes/

Hope this helps!

I’ll go ahead and close this thread for now, as we haven’t received a response. Please feel free to reach out again by opening a new thread or via email, if you still need support.

Hey @nyoz !

Sorry it took us this long, but we have good news. We finally managed to get someone to look over your translations and approved all of them today.

The french translation should be available as an update in your (and everyones!) installation very soon.

Merci beaucoup for your translations. Very much appreciated!

Best
Claudio

Hey there, just saw this thread because you mentioned our plugin picu.

It looks to me like this error is coming from the Elementor plugin itself, but if you (or Elementor support) feel there’s anything we could or should do from our side to fix this, please feel free to get in touch with us.

Hi

You are right, the “Upload Images” window is kind of limited in this regard. There is a workaround though: you should be able to drag & drop images right onto the window in your screenshot and it should upload and add them to your collection.

We’d like to improve this in the future, so I hope this will get easier then, but for now maybe this works? Please let us know.

Hi,

Yes, picu so far does not support featured images for collections. Also, while the images are technically stored in the WP library, we remove them from all queries (other than the ones inside picu collections) because proofing images are usually not meant to be placed into the content of the website anywhere. I think that was the reason why you couldn’t load the first image from WP Grid Builder Plugin.

You can add a list of collections for your clients using our shortcode, to build a simple client area. So far, this won’t display any images though, but we intend to improve this and also switch to a block instead of shortcode, soon. You find some info here: https://picu.io/docs/shortcodes/#list-collections

Hi,

Usually picu deletes all images of a collection, when it is deleted (removed from trash). This should also delete the empty directories like /12961/ in your case, so it would make sense that you don’t see this folder anymore.

That you still can see an image from the browser sounds to me like a caching issue.

Could you test the following:

1. Clear your browser cache and see if it still opens
2. Open the URL of the image in a private window and see if it still opens
3. Open the URL in a completely different browser or even device, and see if it still opens

I’m almost sure that the image was properly deleted, but was just still in your browser cache, and therefore showed up still. Please let us know what you find out!

I’ll close this for now. If you should need any further assistance please send us an email with an example of your snippet to the address you find above.

Hi @imanuelrajan

The code snippet found in our docs (link above) should take precedence over the wp-config.php code, so this should not be needed if you’re using the snippet.

Did you add the snippet using the Code Snippets plugin? And if so, did you make sure the snippet is “activated”?

Sometimes by copy/pasting a snippet the quotation marks can get mixed up? Could you double check the code and maybe manually add the quotation marks again in your snippet?

If this does not work, could you send us an email with the snippets you added, and exactly as you added them to your site to [email protected]?

Thanks!

Hey @imanuelrajan

Yes, the default is using spaces between filenames, but this can be changed using a filter with a little bit of code.

You find some more about it here:
https://picu.io/docs/developers/#custom-filename-separator

Hope this helps!

Hey
thank you – much appreciated!

Not right now, but we actually work on some changes to make this possible and maybe even letting clients can add their name on their own without first “registering” them in the backend.

If you’d like to share some more details about your specific workflow, please get in touch via email at info AT picu.io. It’s always great to hear from real users and it helps us a lot in shaping the development!

Best, Claudio

Hey Daniel

Cool! Glad you found out what was going wrong, and thanks for letting us know.

Let us know if there’s anything else we can do.

Hi Daniel

Ok, it really looks like something is messing with the output of our picu collections and/or the CSS. Some elements are nested that shouldn’t be which is why the styling doesn’t work properly.

Modifying any files (WP core, plugin or theme) directly, is never a good idea, as this will prevent you from updating in the future and most certainly introduce more problems than we are trying to solve.

Did you try the steps in this link we sent you, to rule out if there are incompatibilities with any of the installed plugins?
https://picu.io/docs/check-for-plugin-theme-incompatibility/

Thanks for letting us know!

Not your fault at all. Usually, a “no-reply” address indicates that clients shouldn’t reply to this address, which is why we use it as a default.

I guess that some hosting providers block sending from a no-reply@ address, because it is often used to send spam.

Instead of creating this mailbox just for picu, you could also change the FROM address in picu Settings to use an existing address, I think this should work as well!

Great to know that it’s working now!

Hm, ok. Could you change the email address to something else like contact@mic… (instead of the no-reply)?

Maybe you could also ask your hosting provider, if there are any special rules that could prevent those emails from getting sent?