emmills3

EDIT: Disregard. Your update seems to have worked. My testing environment was cached(?). Still receiving the error, but not possible considering that file no longer goes up to line 162.

Used updated version on a different site with success. Thank you.

ORIGINAL:
Updated and still receiving same error:

Fatal error: Can't use function return value in write context in /var/www/vhosts/awpserver.com/subdomains/staging/httpdocs/z_wordpress_boilerplate/wp-content/plugins/wp-seo-structured-data-schema/lib/classes/KcSeoHelper.php on line 162

• This reply was modified 8 years, 4 months ago by emmills3.

***UPDATE***

I was able to resolve the conflict:

File Path:
/wp-seo-structured-data-schema/assets/js/admin.js

Starting at line 10, I added select to the jquery selector. So it went from this:

$(".select2").select2({
        placeholder: "Select an item",
        theme: "classic",
        dropdownAutoWidth : true
    });

    $(".field-content .select2").select2({
        theme: "classic",
        dropdownAutoWidth : true,
        width: '100%'
    });

To this:

$("select.select2").select2({
        placeholder: "Select an item",
        theme: "classic",
        dropdownAutoWidth : true
    });

    $(".field-content select.select2").select2({
        theme: "classic",
        dropdownAutoWidth : true,
        width: '100%'
    });

I’m sure there is a more elegant solution, but this at least resolved this conflict for the present. I tried added a class of kcseo_select2 to the <select> output in the KcSeoSchemaModel.php file, but wasn’t able to call it properly. I’m sure the developer can implement this solution (or a better one).

I am getting the same error:

Uncaught query function not defined for Select2 s2id__schema_product_availability

If i turn off the Advanced Custom Fields plugin, the Schema tabs function normally. To the best of my knowledge, this plugin was compatible with ACF up until the update around 4/25/2016.

Everrrettt, are you using ACF as well?

I’m looking through the plugin to see if I can find the source of the conflict and look for possible solutions. I’ll post any updates I find.

I can’t speak to every instance, but it turns out one of the programmers had locked down the permissions on the tmp folder on at the root of the server. Opening the permissions up fixed the issue on our server.

I am having the exact same problem. I cannot log into a site I was in previously, and on top of that a website I was in this morning will not update.