Florian Ziegler

Hi @nyoz,

sorry for the delay. Let’s add a request for translations editors to review your translations:

If someone could review and approve the translations @nyoz recently added for #fr_FR, that would be awesome! ??

Cheers
Florian

• This reply was modified 5 months, 1 week ago by Florian Ziegler. Reason: Forgot to add the link

Hi @pleasure94,

we haven’t heard back from you via email, so I post my suggestion here as well:

My guess is, that another plugin or your theme is using the same filter (display_post_states) in a way, that is not providing the necessary post->ID, which causes the warning.

To figure this out, please follow this guide. You can delete (or rename) the debug.log in between tests to figure out, when exactly the error is logged.

Please let me know, what you find out.

Cheers
Florian

Hi @pleasure94,

that’s a bit weird. This part of the code is responsible for showing the “— Closed” state behind the collection title. (Like “— Draft” is shown behind a post title.)

Can you pinpoint when exactly you get this warning?

You may also send your debug info (found under “picu > Settings > Tools/Debug”) via email, which would provide us with more context.

Cheers
Florian

Hi @pleasure94,

Thanks for getting back to us! Glad it is working – albeit it could be improved on our end. (Working on it!)

About the translation: picu is translated via www.ads-software.com by volunteers from the community. All translations need to go through a vetting process, where a so called “translation editor” needs to approve all of the translations before they go live. (We can help with contacting a translation editor, after you added some translations.)

Here’s the Bulgarian translation of picu. It is always a good idea to check the style guide and glossary for your language (in this case I linked the Bulgarian versions), before adding any translations, so they have a better chance of being accepted by the translations editors.

Please let us know if you have any more questions about the translation process!

Cheers
Florian

Hi @lualiza!

In your WordPress Admin, can you please go to “Settings > Permalinks”? Just open this page once, and it should flush the rewrite rules, which might already resolve the issue.

If that does not resolve the issue, please copy the debug info, found under “picu > Settings > Tools/Debug” and send it to [email protected].

I am sure we’ll be able to find a solution. ??

Cheers
Florian

• This reply was modified 8 months, 1 week ago by Florian Ziegler. Reason: typo

Hi @sfredb,

sorry for the confusion.

If you uncheck the box in the security settings, the email field will still be visible, but your client can just enter a name and leave the email field blank. They will forwarded to the collection right away and can start selecting images. If they enter an email address, they will receive a link to access the collection.

If you do not want to use the self-registration feature at all, you can deactivate it by using this filter.

Please let me know if you have any more questions about this.

Cheers
Florian

Hi @mika121!

Yeah, sorry for that. We introduced a bug while fixing another redirect issue with the last update.

We just released version 2.3.1.1, which should resolve this issue.

Please let me know if it still happens for you after installing the update.

Cheers
Florian

Yes it has.

In previous versions it looked like this:

From version 2.3.0 on it looks like this:

We made a couple of changes on how the approval process works, especially the way you can share collections in the Pro version. You can read about the picu 2.3.0 release on our blog.

I also created a snippet to add a preview column with a random image from the collection, which will look something like this:

You can learn about how to use this snippet here.

I hope this is helpful. Let me know if you have any more questions!

Hi @paulpetch,

I am not sure I follow… picu never showed thumbnails in the collection overview. Have you maybe used another plugin to add this function to the overview?

Could you please send your debug info (found under “picu > Settings > Tools/Debug”) to [email protected], so we can take a look?

Cheers
Florian

Hi @malowz,

We fixed the original issue with picu 2.1.3.

There was a change made back in WordPress 5.6 where the status of an untrashed post would always be “draft”. You are right, this does not make any sense for picu collections. So, we will update the plugin so that when you restore collections from the trash, they will be assigned their original status. (This will be part of the next release.)

Cheers
Florian

Hi @malowz,

Thank you for bringing this to our attention!

I just did some testing, and found a bug, which was introduced with version 2.1. We will release a fix for this issue later today with version 2.1.2 Stay tuned!

Cheers
Florian

Hi @rajcz,

We just released version 2.0.3 of picu, which should resolve this issue.

Cheers
Florian

Hi @danieleweb!

There is definitely something wrong with the way the collections are displayed.

Please go to “picu > Settings > Debug Info” and send those infos to [email protected].

I am sure we can figure out, why this is happening and how to fix it. ??

Cheers
Florian

Hi @robertosalemi,

we found something else. It has to do with the quotes you are using in your custom filenames.

Version 1.11.0 will be released tomorrow, which will fix the bug.

Cheers
Florian

Ok, thanks for checking. Please send your debug info, found under “picu > Settings > Debug Info” to [email protected].

Cheers
Florian