gavsterau

Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter gavsterau

    (@gavsterau)

    Thanks very much for your replies.

    The ID (datestamp I assume) on my JS files is 1546968199, not 1543941426.

    1543941426 == GMT: Tuesday, December 4, 2018 4:37:06 PM
    1546968199 == GMT: Tuesday, January 8, 2019 5:23:19 PM

    Will above still work?

    Thread Starter gavsterau

    (@gavsterau)

    Hate following up my own post.

    In one browser I’m getting the correct date format (dd/mm/yyyy), but in another I’m getting the wrong format (mm/dd/yyyy).

    Any ideas on how to debug this?

    Ta, Gavin

    Hi, I hit the same issue.

    I see the reply above says that Automattic are looking into a fix, but I don’t think we’re there yet.

    In my case the Jetpack file ./wp-content/plugins/jetpack/modules/geo-location/class.jetpack-geo-location.php has the following at line 252

    echo PHP_EOL . 'xmlns:georss="https://www.georss.org/georss" xmlns:geo="https://www.w3.org/2003/01/geo/wgs84_pos#
"' . PHP_EOL;

    and Geo Mashup has the follwoing at line 1972 of ./wp-content/plugins/geo-mashup/geo-mashup.php
    echo 'xmlns:georss="https://www.georss.org/georss" ';

    This broke the feeds due to the duplicate georss namespace as mentioned in the reply above. I edited the jetpack file to fix… but this’ll break next upgrade.

    Can the WordPress devs look at managing the namespaces for the plugins? The plugin devs could add their namespaces to a php collection, which could manage/ignore dupes, and then emit a sanitised list of namespaces when required?

    Happy to test any enhancements in this space.

    Ta,
    Gavin

Viewing 3 replies - 1 through 3 (of 3 total)