Blackbam

Please close – was the wrong plugin.

• This reply was modified 1 year, 1 month ago by Blackbam.
• This reply was modified 1 year, 1 month ago by Blackbam.

Thanks, got it. Thought the meta value is per block, makes sense now.

Hi! Within block.php I have the following code:

<section class="full-width-container" style="background-color:<?php
echo get_lzb_meta('background-color'); ?>; padding: <?php
echo get_lzb_meta('spacing'); ?>px 0; color: <?php
echo get_lzb_meta('font-color'); ?>;">
<div class="container">
<div class="row">
<InnerBlocks/>
</div>
</div>
</section>

This basically means it is inline code, isn’t it? When having two blocks in the same site, the background color changes for all elements within the site.

Update: The problem seems to exist only for the color picker and only if using the “save in meta” option (not with $attributes). Furthermore it looks like it has nothing to do with the actually saved meta value, within the Gutenberg editor always adjusts it for all blocks (a “frontend” problem).

• This reply was modified 1 year, 2 months ago by Blackbam.

Having the same problem as @billferris. In my opinion it is great that you have implemented structured data in Yoast SEO, but you really should give the admins more control about this. Especially adding custom properties and change the values.

See the errors I have in a certain project on every page.

View post on imgur.com

How would your recommend I solve this currently and will you fix it in the future?

Great – thanks.

Great.

In this project indeed has a staging site. The process for the website like:

1. local
2. staging
3. live

So we can deploy to staging and I can send you the URL if you want? Staging environment is in heavy use though, we would have to agree on a timeframe for this.

Hi there,

indeed the schema was the reason for the unexpected output and I can get rid of the broken output by using:

add_filter( 'wpseo_json_ld_output', '__return_false' );

Also thank you very much for the great article on how to change the schema output, I might need this for other projects.

So the most important part of the problem is solved, I can make updates again. Still I wonder why the schema output is broken – is there some possibility to debug that?

Hi thank you very much for your fast answer. We have an enterprise setup with a local testing system and a lot of mu-plugins (mandatory plugins), therefore I can not just enable/disable plugins.

As the error was introduced with Yoast 11.0 there must have been some major changes in the Plugin, I guess the problem happens because some new WordPress internal function. Most probably you are using some action / filter hook which is causing the problem.

Do you have a change history for developers? A list of hooks you are using? Any idea which might cause the problem? Because if not I would have to go through the whole Yoast codebase :-/

Btw: I just noticed that all this mess happens within the (object) WPSEO_Frontend -> head (1) within wp_head at priority 1.

@purrdesign Hey there sorry for the late answer! The settings page is just working fine in my setups (recently tested with WordPress 5.1.1 and PHP 7.2). Did you resolve this isssue and do you still need this Plugin? Would love to help you resolving it.

Yet I have to inform that this plugin is not ready for Gutenberg as they unfortunatly destroyed the whole admin interface. Compatibility is planned.

Looks interesting, but not ready for highly complex projects yet. Single author again, who knows how long it lives?

The situation with this Plugin is horrible currently. It is still free and in my opinion 10 times better than its commercial counterparts.

Anyway: 100000+ installs and the author of this Plugin just disappeared. Everybody is hoping someone will develop it further.

More information here: https://github.com/qTranslate-Team/qtranslate-x/issues/476

• This reply was modified 7 years, 2 months ago by Blackbam.
• This reply was modified 7 years, 2 months ago by Blackbam.

Same here. Waiting for update …

I have exactly the same Problem. Even simple Browser zoom would be o.k. ! But no zoom makes it useless on small screens