I was recently told about how to retrieve the file version from http://www.lcpdfr.com/applications/downloadsng/interface/api.php?do=checkForUpdates&fileId=YOUR_FILE_ID&textOnly=1, where YOUR_FILE_ID is the plugin's file ID.  However, when I tried using this with the LSPDFR page (ID 7792), it returns 0.3 for the version.

 

Is it possible to have this updated to reflect the latest version of LSPDFR?

This API had a special provision (it lies for LSPDFR) to deal with an LSPDFR bug.

 

I don't think this is needed or used anymore though, so I'll see if we can restore the normal behaviour for this.

On 12/25/2021 at 6:56 PM, Rich said:

I was recently told about how to retrieve the file version from http://www.lcpdfr.com/applications/downloadsng/interface/api.php?do=checkForUpdates&fileId=YOUR_FILE_ID&textOnly=1, where YOUR_FILE_ID is the plugin's file ID.  However, when I tried using this with the LSPDFR page (ID 7792), it returns 0.3 for the version.

 

Is it possible to have this updated to reflect the latest version of LSPDFR?

This should be fixed with today's update.

Please note that the best way of checking if LSPDFR is up-to-date is the assembly version. The built-in LSPDFR version checker uses this, as well as the latest up-to-date assembly version via LSPDFR Sync. This is currently not exposed through a public API, but we'll see about adding one in future.

 

In general, the build text in the public website update API corresponds to the assembly version build version, you could use a RegEx or similar to extract this out until we make the full up-to-date assembly version is available.