perqa

Trying to save the settings, I get:

Notice: Undefined index: [email protected] in /var/www/html/wordpress/wp-content/plugins/wp-ses/wp-ses.php on line 131 Notice: Undefined index: [email protected] in /var/www/html/wordpress/wp-content/plugins/wp-ses/wp-ses.php on line 142
Notice: Undefined index: [email protected] in /var/www/html/wordpress/wp-content/plugins/wp-ses/admin.tmpl.php on line 34

I also keep getting:
“Amazon API Keys are not valid, or you did not finalize youy Amazon SES registration.”
even though the API keys are valid.

Please check out this issue as well: https://github.com/GoogleCloudPlatform/appengine-wordpress-plugin/issues/13.

I ended up setting both width and height to zero instead, in class-fire-init.php. That way no scaling at all occurs.

Thanks for reaching out so quickly! I have found the cause of the problem: I blindly followed the config instructions provided by Google. Inserting the batcache config *in the right place* in wp-config.php, solved the problem!

More details provided here: https://stackoverflow.com/questions/21666550/why-is-my-wordpress-site-on-gae-not-being-cached/21749209#21749209.

I get a warning when trying to do this:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, first array member is not a valid class name or object in /Users/per/google-cloud/my-app/wordpress/wp-includes/plugin.php on line 199

This issue has also been reported on https://github.com/Automattic/batcache/issues/22

Update:
There are two problems here: 1) Invalid URLs and 2) http instead of https.

#2 has nothing to do with Customizr, it’s a GAE issue
#1 can be partly fixed in Customizr by a) either disabling “full-width slider” in the admin section OR by b) modifying the file wp-content/themes/customizr/inc/class-fire-init.php

Option b) will give you a full-width slider, but the images will cropped and scaled incorrectly. Anyway, here is the modification:

Row 70: $this -> slider_full_size = array('width' => 99999 , 'height' => 500, 'crop' => true );

Replace the ‘width’ value by a smaller number, like 9990 (note: four digits instead of five, and less than 9999).

It would be great with a proper fix for this problem.

I have a similar problem: the plugin generates http URLs, but they are also invalid. The solution above did not help, neither for the https nor the validity.

Example URL: https://lh4.ggpht.com/uDWdZWCSAQ1eJmix54cnCMd-X4KhdG7GPADYsHS_qOzwIgHjpiFQ3TH5xjXL4IC9Yit_qxkPjzFg0v5DpP6W5O_4KUHddLE=s99999-c

Hello,

This is great! These modifications helps me a lot, but is there any way they could be made a part of the official software? Or is there any other way to make the changes stick? Otherwise, next time I update my software, I suppose the modifications will be overwritten?

As I understand it, you have made modifications in two files: functions.php and wp-seo-metabox.js, where the first one belongs to WordPress itself and the second to the SEO plugin. Is that correct?

All the Best,
Per Q A

Yes, I can confirm that sfradel’s solution works really well! Thank you!

Naturally, if you enter multiple languages in Yoast fields that are limited by number of characters, you will get some warnings. But just ignore them. The limits are not applied when you save the data, so the full strings will be in the source code anyway (as long as each language stays under the limit)

Example usage:
Meta Description:
<!--:en-->Cross-platform mobile apps and IT consulting. Mobility solutions.<!--:--><!--:sv-->Mobilappar och IT-konsult. Mobila l?sningar. kdfjhskdfjhksfhskfjhskjfhksjfhdsfsdfssdffdssdj 1234567890<!--:-->

You get the following warning in the SEO admin:

The meta description will be limited to 156 chars, -11 chars left.

However, the full text strings are printed on the web site in each language.

Sorry, but thanks for the reply.
/Per Q A

Hello,

Does Buddypress/Courseware support a multi-site setup of WordPress? When I installed Buddypress it “took over” all my sites. I never saw the option to tell in which sites I wanted it to be active. I am not very experienced with WordPress, so perhaps this is a general plug-in problem?

Best Wishes,
Per Q A