Yasir

Just an update for you, I added space before and after the comma and an audio file is generated for both post and press.

press , post

We are not looking to use S3 option just we want to hide from media library, so just help us with some variable and we may do our custom development or create a filter in function.php

Hi Tomasz,

Do you mean to open this link to verify my AWS account?
https://console.aws.amazon.com/polly/home

When i open the above mentioned link it redirects me to the another Link where this is shown:
https://www.screencast.com/t/Yqqdwf77qpE

Does it any issue related with my AWS Account?

Regards,
Yasir

Hi Kazuya Takami,

I have not heard from you, I believe you are busy with other things so decided to go in some more detail about my request.
At the moment, there is a single check for Front Page and Blog’s Homepage. Can you please add 2 checks on backend.

Front Page
Blog’s Homepage

By default, these checks can be enabled so, those users who wants to disable any check can do that and if it looks difficult so, you can add a simple filter in wp-structuring-display.php which helps user to make these changes from their functions.php file.

Just replace line no. 94 with the following lines in wp-structuring-display.php:

`

$filter_data = apply_filters( ‘structuring_markup_schema’, ‘__true’, $output, $row->type );

if ( array_key_exists( $output, $output_args ) && ‘__false’ != $filter_data ) {

This filter allows user to disable any schema on the specific pages as shown here:

function yasglobal_markup_schema( $value, $arg1, $arg2 ) {

if ( ‘home’ == $arg1 && ‘local_business’ == $arg2 && ! is_front_page() ) {

return ‘__false’;

}

}

add_filter( ‘structuring_markup_schema’, ‘yasglobal_markup_schema’, 10, 3 );

`

I hope, you can apply any of the above mentioned change in the coming version or anything else which give us ability to stop the SCHEMA on specific pages specially for the Front Page and Blog’s homepage. In this way, we can use your plugin with the updated release otherwise we need to stop your plugin updates for our site.

Hi Frank,

Thanks for your quick responses. I have tried v2.2.2 of the plugin and everything looks fine on this VERSION But when i apply the v2.3.1 or v2.3.2 then it starts degrading the performance of my website.

I have checked the changelog of the plugin and found that you had applied workaround for Redis, Memcached in v2.3.2:

workaround for stale options-data in external object cache such as Redis, Memcached (core bug) resulting in Autoptimize continuously………

Maybe, this is causing the issue as my website is using Memcached but not sure…

Hope, you can figure out something. I’ll update you if i found anyother info related to the plugin. For now, it looks a like this bug starts from v2.3.0 and still exist…

Thanks,
Yasir