tszt

Thank you for your reply.

I have attached two screenshots. I meant the use case when I input data into these fields in the Sendinblue form builder in the WordPress plugin (see images). If these input boxes contain one or more accented characters, the changes are not saved, and the form reverts back to the last successfully saved version. (The screenshot examples contain accented characters, because I used HTML entities beforehand, like “ampersand”aacute;, because in that case the new text is saved. Not if I type “á” instead of that.)

(“ampersand”=& in the example, but I cannot type that out here because it automatically changes to the accented character, so I would not be bale to demonstrate what I mean for you)

https://ibb.co/qN8RVzg
https://ibb.co/KjJS7MS

• This reply was modified 1 year, 7 months ago by tszt.
• This reply was modified 1 year, 7 months ago by tszt.

Thank you for your reply. I am afraid there is a misunderstanding here. I am talking about the Sendinblue form design panel in WordPress. Whenever you try to input text (for instance for field labels, error messages, any text in the contact form field, accented characters are not accepted and the changes ara not saved in the subscription form. (So, I am not talking about entering data in the subscription form, I am talking about entering text when designing the form in the WordPress Sendingblue plugin, or writing the text for ‘Success message”, ‘General error message’, etc. in the WordPress plugin interface.)

Spotify in this regard is becoming a huge problem. Obviously, it displays the ‘extract’ tag content form the podcast feed if there is something present in it, and the first few passages of the blog post if there is no extract.
That means, if you compose extracts (usually some kind of very short teasers), you are fu**ed on Spotify.
Why?
Because Spotify seems to offer related content based on the keywords present in the extract!
That means, if you use Powerpress for podcasting and blogging, and use extracts on your blog, you are at a huge disadvantage. (Your short extracts are clearly not ‘dense’ enough information-wise to get your content promoted as related content.)
That is a very serious issue in my opinion. I would not shrug it off so easily.
Is there any chance for podcast providers to cooperate on this with Spotify dev teams?

Szabolcs

Hey Mike,

Thanks for the quick reply.

My guess is that Spotify might use the excerpt if it is present and the blog post (or part of the post) if it isn’t.
Or I do not know. (As I mentioned, the whole blog post is present in the RSS feed, between the right tags.)
It would be worth investigating how it works in this regard as it is becoming an ever important podcasting platform and currently, as I understand, show notes will not show up for those podcasters who use Blubrry.

Also, as Blubrry time stamps work in some podcast apps but seems like they won’t (at least they are not clickable) in Apple Podcasts and Spotify, then that is an issue again, while a lot of work goes into putting them int the post. (This seems like a formatting issue to me.)

In all other aspects Powerpress is a great plugin, Blubrry is a nice service.
Thank you for your attention.

well: an important addition. The Apple Podcasts app does show the shownotes and links correctly on iPhone. However, timestamps are not clickable there.
Sorry for the wrong info, the show notes garbled appearance used to be a problem in iTunes, but not anymore in the new Apple Podcasts app on the iPhone.
Shownotes, however, are completely missing in Spotify.

ok, in fact the shortcode works only if Newspaper comment count element is also present in the single post template, which makes me suspicous that it is messing with something t should not. so lets say, the shortcode does not work either ??

a useful addition:
when I use your shortcode in the single post page template instead of the comment block, the conflict is not there!
So, as a temporal solution, the DCL shortcode can be used.
Seems like the DCL plugin has a conflict with the Newspaper comment block that it replaces.

As I have already reported in the other thread, the new update works great, and has fixed the problem.

Thank you!

I have updated the plugin on the site. And it WORKS!

I have tested it in Podcast Addict on Android, the time codes now are displayed in the show notes inside the app (pulled from the RSS feed), and they work as intended (clicking on them positions the player at the location given in the time code).

That’s great!

Thank you so much!

• This reply was modified 5 years, 5 months ago by tszt.

Hello!

Sorry for the delay. I am planning to update the plugin tonight or early tomorrow. Will report back immediately on the issue.

Thank you for your help,

Szabolcs

• This reply was modified 5 years, 5 months ago by tszt.

Thnak you for your prompt reply and help. Great plugin, great customer service.

• This reply was modified 5 years, 5 months ago by tszt.

Hello,

I am sorry to say, but this problem does not resolve for me with the plugin updates.
The time codes are not displayed in the podcast feed (and consequently, they are not displayed in the podcast players). Though they appear on the blog posts on the website.

Here are the links:

My podcast feed url:

https://azeletmegminden.hu/feed/podcast/

iTunes listing url:

https://itunes.apple.com/hu/podcast/az-%C3%A9let-meg-minden/id1393849643

I enter the shortcode in a Gutenberg shortcode block, as follows (example):

[skipto time=”0:05:11″]

Thank you for your attention!

Szabolcs

Thank you! Will try this soon on my staging site first and let you know how it went.

Thank you, that is very kind of you.

Of course, I can install it from a zip file.

I am looking forward to the link!

Thanks again,

Szabolcs

Oh, that was quick, you are great, thank you very much.

Szabolcs