Author Topic: Updiag 1.1 (Read 31642 times)

datahell · « **on:** December 09, 2006, 21:27:15 »

Updiag became more powerful!

Version 1.1 is a must for any Elxis site and a powerfull tool for all site administrators.
Download and use it. It's free!

Update version 1.0 to version 1.1 by overrding old 1.0 files with those of version 1.1.

Haic · « **Reply #1 on:** December 10, 2006, 01:30:12 »

Hello Datahell,

I have yesterday upgrade the script to Elxis 2006_4 and the database poll execute.
Now have i upgraded this tool but he giver more then 300 files to need to update.

How is this happens?

dot°NETt · « **Reply #2 on:** December 10, 2006, 02:45:46 »

Hi datahell,

first of all I wish to say 'tank you' for this tool.

But: it is as in version 1.0 too >> updiag can't be used in InternetExplorer 7.0 (surly, I use Firefox) because the menu isn't accessible.

dot°NETt

eliasan · « **Reply #3 on:** December 10, 2006, 08:48:12 »

Quote from: Haic on December 10, 2006, 01:30:12

Hello Datahell,

I have yesterday upgrade the script to Elxis 2006_4 and the database poll execute.
Now have i upgraded this tool but he giver more then 300 files to need to update.

How is this happens?

For sure, not all the files contain code changes. A file is considered new and need to be updated even if it contains changes in headers.

The check algorithm finds changes in files. It cannot distinguish if these changes are in the code part or in the headers part.

Also, it will also report a file as needing update if that file has been modified locally by the end user. For example, if you modify a language file to suite your needs, then during the next update, this file will be reported as needing updat.

That is why we suggest not to modify the original core files.

datahell · « **Reply #4 on:** December 10, 2006, 11:16:01 »

To dotNeTt: Did you update to version 2006.4? If yes the problem with the appearence of administration menu in IE7 should be solved. For the updiag I dont know, I have never tested it on IE7.

To Haic: Attention, Updiag does not makes mistakes. What you see is the true situation of your filesystem. What happens: between versions 2006.3 and 2006.4 we changed the header in about 370 files. These changes are concern only the copyright notice and nothing more. For simplicity we did not included these files in the update patch for not having you to update 450 files! The only problem for this is that these files looks outdated in Updiag, although they are not (they contain exactly the same code).

Solutions:
1. Update all the files that Updiag tells you that needs to be updated in order to be binary equal to those of version 2006.4. Take the files from the elxis_2006.4 package.
2. Leave it as is.

Haic · « **Reply #5 on:** December 10, 2006, 13:22:33 »

Thnx Datahell,

The problem is solved

datahell · « **Reply #6 on:** December 10, 2006, 13:29:32 »

Glad to hear that Haic

Having your filesystem intact is a great advantage as you can easily any time check if any file modified even by a little (just one more space is enough, Updiag will track this change). You will be able to restore affected files after a possible hacker attack, or remember manual changes you have made in any file.

dot°NETt · « **Reply #7 on:** December 10, 2006, 17:55:36 »

@datahell,

yes, the problem with the appearence of administration menu in IE7 is solved - it works for me in IE7 too.
I wrote about the updiag-menu - and I only meant this dhtml-menu.

dot°NETt

datahell · « **Reply #8 on:** December 10, 2006, 18:13:51 »

I don't have IE7 installed, so I can not check to see what causes this problem in IE7, it's of course a CSS issue.

Edit file: /administrator/tools/updiag/css/tabmenu.css
Play with it till you fix it.
Post us here a CSS hack for IE7 if you solve it.

dot°NETt · « **Reply #9 on:** December 10, 2006, 21:35:11 »

Hi datahell,

it's not only a CSS-issue.
Parts of the code in /administrator/tools/updiag/js/tabmenu.js are not compatible with IE7.
If I find a liitle bit time, I'll try to find a solution.

dot°NETt