mumbomedia

I know, the warning can be confusing.
The plugin works fine, even with the latest version of WP.
Have tested it myself.
So there is no need for an update, but the author should update the info, so the warning will disappear.

As far as I understand, you need to be a registered user to edit the shortcode. Therefore, only registered users can edit this. If only the necessary users have access to this and appropriate passwords are used the risk should be very low. Or did I miss anything?

As it seems there was an issue with the overridden blocks since they used the class attribute instead of inline-class.
I’ve correct this and now the style are applied as they should.
Sorry for the inconvenience.

I looked at the blocks that show the links in green.
They have inline CSS as in your documentation https://www.thenewsletterplugin.com/documentation/developers/dev-composer-blocks/#css-inliner.
But for some unknown reason these styles are not applied inline, so the corresponding elements have no style attribute and therefore only the styles from the all.css file are applied.
The problem seems to be that the custom blocks are no longer rendering as they did before. Perhaps this will help you investigate the problem further.
If you need a backup of one of the affected systems let me know so that I could send you a file link to that backup.

have tried with the latest version 7.6.6.
The problem with the green links is still there.
The mentioned /wp-content/plugins/newsletter/admin/all.css is included and therefore, among other things, all links are displayed in a green color.
I don’t understand why there has to be general styles at all and even if they are necessary, why there is no setting to change them according to the website so we can achieve a corporate identity.
Currently we are using the older version 7.5.9 of the plugin where the problem does not exist. For the sake of security, I would use the latest version, so I would appreciate if the problem could be solved as soon as possible.

I could indeed adjust the CSS file. But this adjustment would be overwritten with the next update , so this is not a sustainable solution in my humble opinion. If I knew how I could prevent the inclusion of this file or replace it with a file that is not overwritten with each update, this would already help me a lot.

So I hope you could fix this issue asap so that our customer can continue to use your fantastic plugin in a safe environment.

Indeed after exporting, changing disable-post_format from 1 to nothing and reimporting the settings the tab is showned as expected.
Even after disabling this archive via its tab it is shown as expected.

@twentyzerotwo That is exactly the issue I’m facing.
Great to read that it is fix with the next version dated for Feb. 7th which is next week.

I installed one of the affected system on my test server and disabled plugins and also changed the theme both once to twentytwentytwo and twentytwentythree. Still I get the error when I try to call /wp-admin/admin.php?page=wpseo_page_settings#/format-archives.

So now I can say with 100% certainty that something about the new UI is not working as expected. However, since the JS files are all minified, it is impossible for me to debug even further. Also, I lack the necessary knowledge of which JS functions should be called and how they in turn interact with other JS functions. Therefore, I would like to kindly ask you again to check and fix the bug as soon as possible. Otherwise I have no choice to replace your great plugin with a different working plugin which would caused a lot of extra work for me and this would be the last I want.

@maybellyne
I’m aware how to do a debugging.
I’m a professional webmaster.
But as I mentioned already this problem occurs on different customer system with different themes and different plugins.
Also as @twentyzerotwo mentioned it also occurs if only acf is installed alongside the yoast seo plugin.
The plugin works well since ui was changed.
Now the plugin isn’t usable anymore and if the issue isn’t fixed asap I have to replace it with another plugin causing a lot of work since I had to do it on ~ 80 installations.

@twentyzerotwo Glad to hear that it is indeed a common issue.

get the same error.
Already tried the RC1-version, but the issue persist.

Unfortunately the developer portal wasn’t helpful at all.

Therefore I had to search through the source code and found the hook I was looking for wpseo_schema_organization_social_profiles because in my case the output is for an organization. This filter is defined in src/generators/schema/organization.php

If someone needs it for a person it is possible with the hook wpseo_schema_person_social_profiles which is defined in src/generators/schema/person.php

Thanks for fast reply.

I wasn’t aware of the developer portal.

I investigate it further and found out, that there is already a blue background for active sliders. But due to the missing height setting for .slider the element has a height of 0 and therefore the background isn’t visible. Setting the height to 20px resolve the issue.

Hi @arnaudbroes,

glad to hear that I could help you improve your great plugin.
If I only have to add my fix one more time, that’s fine with me.

Have a nice day and keep up the good work.