Total Updater 0.8.6.9 - Total Commander & plugin updater
Moderators: Hacker, petermad, Stefan2, white
I have tried Total Updater now.
DiskDir 1.1 on totalcmd.net is old.
Version 1.3 (32+64) on http://ghisler.com/plugins.htm
Direct link: https://plugins.ghisler.com/plugins/diskdir.zip
DiskDir 1.1 on totalcmd.net is old.
Version 1.3 (32+64) on http://ghisler.com/plugins.htm
Direct link: https://plugins.ghisler.com/plugins/diskdir.zip
Getting trusted CA certificates over unsecure http connection does not sound very secure. IMHO the least wrong approach would be to export trusted certificates from Windows certificate store. At least for non-portable TC installations.white wrote:Would updating wincmd.pem be a nice addition to your program? It could be updated using http://curl.haxx.se/ca/cacert.pem.
I noticed this information is added to the download of the Total Updater database at:white wrote:DiskDir 1.1 on totalcmd.net is old.
Version 1.3 (32+64) on http://ghisler.com/plugins.htm
Direct link: https://plugins.ghisler.com/plugins/diskdir.zip
http://www.totalcmd.net/plugring/tcplugindb.html
But the version information (and Updated date) is not adjusted. So the new database is not detected when people search for new versions using Total Updater.
I noticed tab characters are missing in the newly added lines.Total Updater - Plugin database (Update only) [569b217/19.01.2014]
..
Updated: 9.09.2013
Code: Select all
[diskdir]
WebsiteID = diskdir
ForceLatestVer= 1.3
DirectLink= https://plugins.ghisler.com/plugins/diskdir.zip
AuthorURL= http://ghisler.com/plugins.htm
* Download from http://www.totalcmd.net/plugring/tcplugindb.html
* Rename database_20140203.zip to database.db
* Copy database.db to Total Updater program folder
I noticed the setting GhislerID = <pluginID on ghisler.com/plugins.htm>
What does it do?
@white:
Thanks for noticing this issue and confirming the fix!
I missed to update the title of the plugindb entry with the actual release date (I keep only correcting the title of the entry - in this special case this is where TU gets its version information from - so a new DB update won't show up again and again on the frontpage of totalcmd.net).
You're correct, "GhislerID" is a special key that matches the name of a given plugin on ghisler.com/plugins.htm. There has been some changes in the code of TU in the recent versions to support extracting information directly from this official page, but it hasn't been finalized yet - so currently its only there for future purposes (and to let me update the db entries a bit more easier using the editor software).
About cacert.pem: it could also be added to the database, I'll consider including it in the next minor update (however a bit modification inside TU would also be needed to achieve this).
Thanks for noticing this issue and confirming the fix!
I missed to update the title of the plugindb entry with the actual release date (I keep only correcting the title of the entry - in this special case this is where TU gets its version information from - so a new DB update won't show up again and again on the frontpage of totalcmd.net).
Thanks, I'll make some changes to the db editor software.I noticed tab characters are missing in the newly added lines
You're correct, "GhislerID" is a special key that matches the name of a given plugin on ghisler.com/plugins.htm. There has been some changes in the code of TU in the recent versions to support extracting information directly from this official page, but it hasn't been finalized yet - so currently its only there for future purposes (and to let me update the db entries a bit more easier using the editor software).
About cacert.pem: it could also be added to the database, I'll consider including it in the next minor update (however a bit modification inside TU would also be needed to achieve this).
That would be nice.Bluestar wrote:You're correct, "GhislerID" is a special key that matches the name of a given plugin on ghisler.com/plugins.htm. There has been some changes in the code of TU in the recent versions to support extracting information directly from this official page, but it hasn't been finalized yet - so currently its only there for future purposes (and to let me update the db entries a bit more easier using the editor software).
Your program looks nice. I only missed better documentation about what it actually does. I feel the explanation "Total Updater is a small tool that helps you to keep your Total Commander & its plugins up-to-date" is not nearly enough. I think a detailed explanation would help users a lot.
More info here: http://curl.haxx.se/docs/caextract.htmlBluestar wrote:About cacert.pem: it could also be added to the database, I'll consider including it in the next minor update (however a bit modification inside TU would also be needed to achieve this).
If TC is open en you press F1 in Total Updater a tab in TC is opened and Lister is opened with readme.txt.
On my system if I try this the first time after starting TC, a new tab is made but before it has the change to change to the folder with the readme.txt file TC Updater tries to open it in Lister so I get a "No files selected" error.
A second try always works (so do consecutive tries).
My system is not very fast. Apparently it needs a small delay.
On my system if I try this the first time after starting TC, a new tab is made but before it has the change to change to the folder with the readme.txt file TC Updater tries to open it in Lister so I get a "No files selected" error.
A second try always works (so do consecutive tries).
My system is not very fast. Apparently it needs a small delay.
-
- Senior Member
- Posts: 276
- Joined: 2011-11-15, 06:14 UTC
- Location: DE\BN - only part time TC user after switching to Linux ;)
2Bluestar:
I used TU to update TC to RC3 on two of my computers yesterday and today. After TU updated TC it downloaded the new internal database which was also fine.
But after all the updating there was a msgbox (error type) that there was an invalid pointer operation.
I guess this has to do with the new database.
Nothing critical as everything worked..
I used TU to update TC to RC3 on two of my computers yesterday and today. After TU updated TC it downloaded the new internal database which was also fine.
But after all the updating there was a msgbox (error type) that there was an invalid pointer operation.
I guess this has to do with the new database.
Nothing critical as everything worked..
Very unlikely. The only change to the database is that the following lines were added to the "[diskdir]" section.seb- wrote:But after all the updating there was a msgbox (error type) that there was an invalid pointer operation.
I guess this has to do with the new database.
ForceLatestVer= 1.3
DirectLink= https://plugins.ghisler.com/plugins/diskdir.zip
AuthorURL= http://ghisler.com/plugins.htm
2Bluestar
TU 0.8.6.7 cannot detect 64bit plugins when there is only a .w?x64 file installed without a correponding .w?x file.
If I manually change .w?x to .w?x64 in the [ListerPlugins] section of wincmd.ini, then TU can detect the plugins. But the two 64bit lister plugin packages that I have that doesn't countain a .wlx file they both write .wlx and not .wlx64 to the .ini file during installation.
I also noticed that if I put an older version of for example imagine.wlx 1.0.8 in the same dir as a version 1.0.9 imagine.wlx64 then TU (run from TC 64bit) shows that the version of Imagine is 1.0.8 and not 1.0.9 as it should.
When TC is run under TC 64bit, TU should check for the prescence of a .w?x64 file even though the plugin is registered as a .w?x file in wincmd.ini, in order to detect that the plugin is installed.
And when TC is run under TC 64bit, TU should read the .w?x64 files and NOT the .w?x to get the version information.
TU 0.8.6.7 cannot detect 64bit plugins when there is only a .w?x64 file installed without a correponding .w?x file.
If I manually change .w?x to .w?x64 in the [ListerPlugins] section of wincmd.ini, then TU can detect the plugins. But the two 64bit lister plugin packages that I have that doesn't countain a .wlx file they both write .wlx and not .wlx64 to the .ini file during installation.
I also noticed that if I put an older version of for example imagine.wlx 1.0.8 in the same dir as a version 1.0.9 imagine.wlx64 then TU (run from TC 64bit) shows that the version of Imagine is 1.0.8 and not 1.0.9 as it should.
When TC is run under TC 64bit, TU should check for the prescence of a .w?x64 file even though the plugin is registered as a .w?x file in wincmd.ini, in order to detect that the plugin is installed.
And when TC is run under TC 64bit, TU should read the .w?x64 files and NOT the .w?x to get the version information.
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar