Geoffrey

Hello @christophe971 ,

Thank you so much for taking the time to open a ticket, and sorry for the inconvenience.
Let me ask or confirm what you tried:

1. you have activated the cache system for 6-hour cache, right?
2. have you tried loging-in using e-mail address at least? (I’ve checked with Bluesky Handle, it works only on their platform)
3. have you tried using the App Password system? https://bsky.app/settings/app-passwords
   it will generate a unique pass that you can use for this plugin only instead of your account password. Like that you separate your password from this unique pass, and you can kill it whenever you want.
   I also have the feeling the Bluesky system works better with it.
4. About your PS : would a “styles” section in the settings be a good feature in your opinion?

Thank you again for your time.
Have a good day!

@christophe971 ha ha no worries ??

@abiraghi thanks for the further tests and feedback. I’ll definitely double check that and fix the issues.

Probably a cache issue for the number of posts. I’ll fix that too.

I’ll keep you posted!

@abiraghi you should now see an update available for this plugin. This will bring some edition in the admin page of the plugin, and its description in the plugins page. Multiple places to get the useful info on how to use the shortcode.

Again, sorry for forgetting about it in the first place.

Hello,

Thank you for your question.

That’s on me. I totally forgot to add it in the description of the plugin.

You have [bluesky_last_posts] and [bluesky_profile] shortcodes. I’ll add them in the description.

Thank you again.

• This reply was modified 2 months, 1 week ago by Geoffrey.

Hello Raquel,

Thank you for your honest feedback. That’s a good usecase you have here. You can find all the “hidden” (system) custom field in different places but you have to know a bit of development techniques.

The custom field is called _juizl-hreflang

The issue I see is that the URL(s) are all saved as a structured table in this custom field. Which should make it difficult to extract. Unless ACF is smart enough to handle that case, but I’m really not sure about that.

Tell me if I can help more.

Bonjour Virginie,

La nouvelle version publiée à l’instant reprend vos points.
Quelques erreurs de conception autour de WP_mail() avaient été introduites, notamment une mauvaise utilisation du premier paramètre, mais l’e-mail était bien envoyé en Bcc (vous ne pouviez donc pas voir les différentes adresses mais le mail était bien envoyé)

Le Bcc est maintenu, le From est correct (vérifié que ce n’est pas votre environnement local qui remplace ce paramètre, j’ai le cas chez moi) et, si aucun message n’est écrit par l’utilisateur, alors le titre et message renseignés dans l’espace d’administration sont utilisé. Le titre l’est dans tous les cas d’ailleurs.

Merci pour vos suggestions, et bonnes fêtes.

Geoffrey

That’s a lovely review and feedback Valérie.

Thank you so much for this, and thanks for your support question and help on solving the WP Job Manager weirdness ??

My pleasure Valerie,

If you have a bit of time to rate the plugin, it would be lovely ??

Thanks again for the suggestion and patience ??

Hello,

Sorry for the inconvenience.
I need to dig a little bit on this to reproduce and fix the issue for this specific case.

I’ll get back to you as soon as I had time to solve this ??

Bonjour Virginie,

Merci pour ce feedback.
Je vais pousser quelques tests supplémentaires pour confirmer ces bugs.

Cependant la deuxième partie mentionnée sur les textes de personnalisation sont le comportement voulu : si jamais le support de JavaScript n’existe pas chez le visiteur, le bouton mail devient un mailto: précomplété avec les informations de personnalisation.
Autrement ces informations de personnalisation ne font pas sens, puisqu’on invite l’utilisateur à personnaliser les contenus directement dans la modale.

Mais peut-être est-ce un biais de conception de ma part et qu’il serait plus logique de l’intégrer dans le message initial dans la modale, si c’était votre suggestion ??

Merci par avance, et navré pour le délai de réponse, pas facile de suivre les demandes de support.

Hello Valérie,

The last update should add the support for WP Job Manager.
This plugin uses a weird way to get the content of the post for their CPT, and I think this issue is not an issue, but a design decision for keeping a strong control on the way the content is displayed.

I had to explicitly add the buttons to the WP Job Manager content thanks to their hooks. Classic hooks on post_content simply don’t work.

Tell me if everything works for you.
Geoffrey

Thank you,
can you try deactivating the counter option to see if something’s wrong with Safari interpreting the script for the counters? Don’t forget to refresh your cash. If it fixes the issue, that means I need to do something for Safari iPad/iOS specifically for this script.

I’ve tested it on my website again yesterday with and without this option, and it was all right. But indeed in can reproduce the bug on your website on iPad.

Sorry for the inconvenience.

Hello Valérie,

thank you for warning me about this issue.
It’s actually a well known problem for 2 months or so, I think it’s a regression I need to work on.
Unfortunately my plate is full lately, but I’ll try to give it a bit of my time this week-end.

Thank you for your understanding and support ??

Hello mowikan,
As I say in the plugin description, open a support request when something doesn’t work, otherwise I can’t help. Most of the time it’s not an issue with the plugin, but with the context of use.

In your case, it’s weird, because the buttons are basic links. A link is supported natively by iPad and iPhone for years now since it’s the way hypertext links work for ages on the web.

Can you give me more information about your context, your website, etc.?
Your theme must be adding event with JS, which has nothing to do with my plugin working or not ??

Thank you.