George Notaras

It turns out that some other projects I got running won’t let me focus on the development of the 2.10.10 release at the moment. So, chances are that this release will be delayed for *yet* another week. Sorry about that.

In the meantime, please feel free to add your feedback here or at Github.

Moreover, some strings have changed, so this delay is also a good opportunity to update the translations.

Kind Regards,
George

Oh, I see. Thanks for the explanation. Much appreciated.

Oh, you are probably right. Now I recalled that the other day I had tried uploading a bunch of PHP files while refreshing the page and had noticed that it took some more time than usual before the files were available for reading. Too bad I spent over an hour trying to find the possible bug earlier!

Update: I’m now quite certain that it’s the underlying virtual disk on a possibly network based block device. Sorry about the invalid bug report!

Hey Samuel,

Just wanted to point out that as far as I can tell I haven’t received any email notifications for posts added to the aforementioned topic. But, I have no idea if it’s related to the cause of the redirection issue I had (possibly the special characters of the topic title).

Hi Hicham,

It seems I missed your last posts.

The snippet above modifies the metadata generated by the AMP plugin. I’ll be checking it more closely at some later time tonight and keep you updated.

George

[…] I’ll be testing it shortly and have more feedback.

Didn’t manage to find the time for the test yesterday. I hope I’ll be testing it tonight. From what I’ve been reading it should work out of the box without requiring to set the COOKIE_DOMAIN option (as mentioned in the linked post):

define( 'COOKIE_DOMAIN', $_SERVER[ 'HTTP_HOST' ] );

I’ll keep you updated.

Tony, I’ll be testing it shortly and have more feedback.

Here it is, Hope this helps.

https://halfelf.org/2014/mapping-domains-without-plugin/

Great post and explanation! (Update: so the feature had been there since 3.9 and they had been hiding it from us :p)

Chances are that the web server configuration does not allow customization using .htaccess files.

You should check the virtual host’s configuration in apache and make sure that at least AllowOverride FileInfo exists in the context of the /path/to/site.co/ or a parent directory.

In order to increase the chances of getting help, posting the error message should be the way to go.

Usually, core functionality of a web application such as the account login/logout is not bound to a specific type of device. The layout may be different, but the functionality stays the same. However, there might be exceptions to this general rule.

The error message would possibly help in any case.

I’m looking for the documentation on the WordPress Codex for domain mapping in version 4.4. I’ve found a few posts in the forums and on make.wordpress about the fact that domain mapping is in core […]

Hello Tony, thanks for your input. I’m a little puzzled with this feature. I cannot fully explain the very little publicity it got.

On the other hand, I recall reading that mapping a 3rd party domain to WP was there in pre-4.4 WP releases too, but needed a small hack to make it work as expected. So, the main feature has actually been there since a long time and that might explain the lack of publicity.

Anyway, time permitting I’m going to do some research about it.

Example:

function xyz_amp_modify_json_metadata( $metadata, $post ) {
    return array();
}
add_filter( 'amp_post_template_metadata', 'xyz_amp_modify_json_metadata', 10, 2 );

Please note this is untested.

If I enable the option “Automatically generate and embed Schema.org Microdata.” the meta tags “article” will duplicate, it gives “Article 2”

This is the expected result.

In order to deactivate the schema.org metadata generated by the AMP plugin you will possibly have to attach a filtering function to the amp_post_template_metadata hook and return an empty array. Please note that this is untested. See more here: https://github.com/Automattic/amp-wp#schemaorg-json-metadata

As a general principal Add-Meta-Tags never affects the functionality of other plugins, so any customization of the AMP output must be done by the user. However, if you need any help, please feel free to ask your questions here or on Github.

Best Regards,
George

Hmm, weird. I checked with Firefox, QupZilla and curl and always could reproduce the problem. Anyway, as soon as I notice another topic with this problem, I’ll post more info.

Hi Hicham,

Have you turned on the generation of schema.org metadata in the Add-Meta-Tags settings (Settings -> Metadata)?

The JSON+LD data I see is most probably generated by the AMP plugin.

The customer needs to create A records that point to your IP. On your end you have to configure the multisite in such a way so that the customer’s domains are mapped to the relevant subsites. This can be done with the MU Domain Mapping plugin or since WP 4.4 I read that it is possible without it.

I don’t think there is any other way to do this. From what I understand about your configuration, the IP is not specific to any website.