Updates?

I am receiving the following error when I try to “check updates”…


Last checked on November 11, 2023 at 12:42 am. Check Again

Unable to determine whether a ClassicPress update is available.

You may be running a customized build of ClassicPress, or your server may be having internet connectivity problems.

My server is fine… I checked outgoing connections to ensure was nothing there… just letting you all know!

I also see the following in my http log:


[https://api-v1.classicpress.net/upgrade/1.7.1.json?version=1.7.1&php=7.4.32&locale=en_US&mysql=5.7.27&local_package=&multisite_enabled=0&initial_db_version=37965&failure_data=0&translations={"default"%3A{"es_ES"%3A{"POT-Creation-Date"%3A""%2C"PO-Revision-Date"%3A"2018-12-20+10%3A36%3A59%2B0000"%2C"Project-Id-Version"%3A"1.0.x+-+Dev"%2C"X-Generator"%3A"GlotPress\%2F2.4.0-alpha"}}}](javascript::wink:

ALSO - this page shows that the last update was quite a few days ago, on the 6th… is that correct?


Releases · ClassyBot/ClassicPress-v2-nightly · GitHub

Update api server is under maintenance for some issues. Core devs are working on it. Should be back on track soon.

@MattyRob mentioned that he had to rebuild part of it.

Just as a followup - here’s what I’m seeing now when I try to check for updates (CP 1.7):



The API server is back up and functional - huge thanks to @viktor for the assistance, very steep learning curve for me getting everything back up again.

The nightly builds for versions 1.x and 2.x of ClassicPress worked last night for the first time in a few days and as far as I’m aware then endpoints on the API server are all working again.

Please do report any further issues you encounter.

I just tried it again on both 1.x and 2.x… it’s still coming up with this message:


Current version: 2.0.0+nightly.20231111

Last checked on November 12, 2023 at 10:41 am GMT+0000. Check again.

Unable to determine whether a ClassicPress update is available.

You may be running a customized build of ClassicPress, or your server may be having internet connectivity problems.

Learn more about ClassicPress 2.0.0+nightly.20231111.

On my 1.x version, this is what the https log shows:


[https://api-v1.classicpress.net/upgrade/1.7.1.json?version=1.7.1&php=7.4.32&locale=en_US&mysql=5.7.27&local_package=&multisite_enabled=0&initial_db_version=37965&failure_data=0&translations={"default"%3A{"es_ES"%3A{"POT-Creation-Date"%3A""%2C"PO-Revision-Date"%3A"2018-12-20+10%3A36%3A59%2B0000"%2C"Project-Id-Version"%3A"1.0.x+-+Dev"%2C"X-Generator"%3A"GlotPress\%2F2.4.0-alpha"}}}](javascript::wink: 200 1.9291 17 seconds

Seems like there’s a syntax error in JSON output:

image

Here’s the raw output:

{
"offers": [
    {
        "response":"latest",
        "download":"https://github.com/ClassicPress/ClassicPress-release/archive/1.7.1.zip",
        "locale":"en_US",
        "packages":{
            "full":"https://github.com/ClassicPress/ClassicPress-release/archive/1.7.1.zip",
            "no_content":None,
            "new_bundled":None,
            "partial":False,
            "rollback":False
        },
        "current":"1.7.1",
        "version":"1.7.1",
        "php_version":"5.6.4",
        "mysql_version":"5.0",
        "new_bundled":"4.7",
        "partial_version":False
    }
]
}

It does not recognize None as it’s not part of the standard and considers it an invalid literal, as also considers False an invalid numeric literal.

By replacing None to null and False to false, it works as expected.

@stefanos82 - Brilliant - I only wish I’d seen that 2 hours ago, it took me some testing to hunt that issue down!!

I hope I have applied a fix and it should be working again now - you may need to wait for site transients to update to notice the change.

1 Like

Seems like it works now as expected:

1 Like

It IS working… thanks to all!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.