Upgrading to 1.4.10 from 1.4.3 What's to gain?

[Bruce]

After running VersionCheck, I see only 6 areas that require upgrading. So far with 1.4.3 I have found no problems with any of the present features, and after reading all the problems people much more advanced in programming than me have had I really am in no mood to risk my present setup.

I've read the docs for 1.4.10, but I really see no big changes that would seem to benefit me going through the upgrade process and the attendent problems with my custom theme, etc.

So what really do I have to gain from this upgrade - which I have noted is "mandatory".

[Nibbler]

Not being hacked would be the major reason.

[Joachim Müller]

Here's a section of the changelog that describes what has been changed from cpg1.4.3 to cpg1.4.10:

2006-11-12 [ B ] Fixed plugin api sleep and wake actions to be scoped correctly. {Donnoman}
2006-11-09 [ B ] Fixed display of hit stats link on displayimage {Nibbler}
2006-11-09 [ M ] Updated version count from cpg1.4.10 to cpg1.4.11 in subversion repository as a preparation for a possible future release {GauGau}
2006-11-09 [ A ] Added Thai language (user contribution) {GauGau}
2006-10-30 [ M ] Release of cpg1.4.10 {GauGau}
2006-10-29 [ B ] IE/WMP video playback fix {Nibbler}
2006-10-28 [ S ] Removing SQL injection vulnerability {Nibbler}
2006-10-27 [ M ] Removing unused file include/exifReader.inc.php {Nibbler}
2006-10-27 [ B ] Adding missing checks for email address validity and duplicate email addresses to profile page. {Nibbler}
2006-10-27 [ B ] Correcting difference between schema.sql and update.sql with respect to the user_password field. {Nibbler}
2006-10-27 [ B ] Pictures awaiting approval are no longer found using the search feature. {Nibbler}
2006-10-27 [ B ] Converting htmlentities back to normal format for use in emails {Nibbler}
2006-10-16 [ B ] BLOB and TEXT columns cannot have DEFAULT values. {Nibbler}
2006-10-16 [ D ] Updated minimum requirements information. {Nibbler}
2006-10-08 [ B ] Escape queries in include/exif_php.inc.php {Donnoman}
2006-10-03 [ S ] Corrected flaw in search logic {Nibbler}
2006-09-17 [ M ] Updated credits section of documentation {GauGau}
2006-09-04 [ A ] Added Indonesian language file (user contribution) {GauGau}
2006-09-03 [ M ] Updated version count from cpg1.4.9 to cpg1.4.10 in subversion repository as a preparation for a possible future release {GauGau}
2006-09-02 [ O ] Updated brazilian language file (user contribution) {GauGau}
2006-09-01 [ B ] Reverted width="100%%" in themes.inc.php & sample theme - topic: 35701 {Paver}
2006-08-26 [ M ] Release of cpg1.4.9 {GauGau}
2006-08-24 [ D ] Added group membership section to docs {GauGau}
2006-08-22 [ C ] Corrected spelling of 'determine' {Nibbler}
2006-08-20 [ B ] Fixed sql issue with missing/incorrect user galleries {Nibbler}
2006-08-16 [ B ] Fixed SEF plugin issue with favpics meta album {Nibbler}
2006-08-12 [ D ] Added $extra_info and $install_info implementations to the sample plugin {Donnoman}
2006-08-12 [ C ] Changed pluginmgr.php to display $extra_info and $install_info clearly with its associated plugin {Donnoman}
2006-08-12 [ B ] Fixed $extra_info and $install_info repeating for unrelated plugins {Donnoman}
2006-08-11 [ B ] Fixed duplicate documentation_lnk per http://forum.coppermine-gallery.net/index.php?topic=33836.msg158112#msg158112 {Donnoman}
2006-08-10 [ B ] Removed BOM (Byte Order Mark) from Hebrew, Polish and Slovenian {GauGau}
2006-08-10 [ D ] Changed minimum requirements section in docs from PHP4.1.0 to PHP4.2.0 {GauGau}
2006-08-09 [ B ] Fixed invalid character at start of dutch language file {Nibbler}
2006-08-01 [ C ] Fixed relative positioning glitch of navmenu in IE {GauGau}
2006-07-28 [ O ] Updated hebrew language file (user contribution) {GauGau}
2006-07-28 [ D ] Fixed anchor link in docs {GauGau}
2006-07-17 [ A ] Added Albanian language file (user contribution) {GauGau}
2006-07-13 [ A ] Added Brazilian-Portuguese language file (user contribution) {GauGau}
2006-07-10 [ D ] Added documentation improvements {GauGau}
2006-06-30 [ B ] Created a new snapshot of themes.inc.php for the sample theme.php {Paver}
2006-06-25 [ B ] Removed admin from secondary group in usermgr.php - topic 32781 {Paver}
2006-06-25 [ B ] Fixed user profile fields in charsetmgr.php - topic 32491 {Paver}
2006-06-25 [ B ] Fixed theme_create_tabs call in functions.inc.php - topic 33030 {Paver}
2006-06-25 [ C ] Modified Persian label according to topic 33024 {Paver}
2006-06-25 [ B ] Added id tag for keyword field in upload.php for Firefox "insert from keyword list" {Paver}
2006-06-23 [ C ] Fixed extra bold tags for {STATISTICS} in themes.inc.php {Paver}
2006-06-23 [ S ] Fixed the security flaw in parameter cleanup system reported by imei addmimistrator @ http://myimei.com/security/2006-06-20/coppermine-148parameter-cleanup-system-bypassregistering-global-varables.html  (addmimistrator(4}gmail(O}com) {Aditya}
2006-06-23 [ S ] Fixed the security flaw in add_hit function reported by imei addmimistrator @ http://myimei.com/security/2006-06-11/copperminephotogallery148-addhit-function-sqlinjection-attack.html  (addmimistrator(4}gmail(O}com) {Aditya}
2006-06-16 [ M ] Counted version number up {GauGau}
2006-06-12 [ B ] Added table type info for all tables {GauGau}
2006-06-07 [ M ] Release of cpg1.4.8 {GauGau}
2006-06-07 [ M ] Updated version count {GauGau}
2006-06-07 [ B ] Reversed 'lastalb' fix due to stability issue {Paver}
2006-06-06 [ M ] Release of cpg1.4.7 {GauGau}
2006-06-06 [ M ] Updated version count in versioncheck.php {GauGau}
2006-06-06 [ B ] Fixed 'lastalb' bug for MySQL 4.1+ (known issue for 3.23, 4.0) {Paver}
2006-06-06 [ S ] Modified fix for usermgr security issue {Paver}
2006-06-05 [ B ] Removed filmstrip function from classic theme {Nibbler}
2006-06-05 [ S ] Fixed the usermgr security issue {Abbas}
2006-06-04 [ B ] Fixed private images showing up in lastup & random {Paver}
2006-05-23 [ M ] Increased version number in svn from 1.4.6 to 1.4.7 {GauGau}
2006-05-23 [ D ] Added missing detail in database requirements section {GauGau}
2006-05-19 [ M ] Release of cpg1.4.6 {GauGau}
2006-05-19 [ M ] Updated default table prefix {GauGau}
2006-05-19 [ B ] Fixed clickable keywords for utf-8 encoding {GauGau}
2006-05-18 [ B ] Fixed the reset of detailed hit/vote stats issue {Abbas}
2006-05-19 [ O ] Removed unneeded flush of outbut buffer in category manager {GauGau}
2006-05-19 [ C ] Replaced "report to moderator" button in hardwired theme to match the overall look of the theme {GauGau}
2006-05-19 [ C ] Replaced "report to moderator" button in eyeball theme to match the overall look of the theme {GauGau}
2006-05-18 [ B ] Added imagejpeg workaround to address bug in PHP4.4.1 {GauGau}
2006-05-17 [ B ] Created default value of $category['cat_thumb'] when not defined in theme_display_cat_list {Paver}
2006-05-17 [ B ] Fixed $cpg_show_private_album setting & use for meta-albums, topic 30894 {Paver}
2006-05-17 [ B ] Fixed hardcoding of 'iso-8859-1' in stat_details, keyword_select, xp_publish {Paver}
2006-05-17 [ B ] Fixed errant "inactive_next_tab" notice & put in commented placeholder code {Paver}
2006-05-17 [ B ] Fixed category statistics, making unapproved uploads not being taken into account {GauGau}
2006-05-17 [ B ] Fixed upload approval to personal galleries when public upload approval is turned off {GauGau}
2006-05-17 [ B ] Preventing whitespace in include/config.inc.php breaking cookies {Nibbler}
2006-05-17 [ C ] Cleaning notices caused by bridging system {Nibbler}
2006-05-17 [ B ] Fixing nuke check 'continue anyway' feature {Nibbler}
2006-05-17 [ B ] Fixing search * wildcard {Nibbler}
2006-05-17 [ C ] Avoid deleting group_name unnecessarily {Nibbler}
2006-05-17 [ C ] Avoiding php notice in profile.php {Nibbler}
2006-05-17 [ B ] Fixing edit permissions bug {Nibbler}
2006-05-17 [ D ] Changed layout of changelog (this file) {GauGau}
2006-05-17 [ A ] Added Finnish language (user contrib) {GauGau}
2006-05-17 [ S ] Fixed the obscure, misdocumented "feature" in Apache that causes the server to process the last "valid" extension in the filename (rar exploit): replace all dots in the filename except the last one with an underscore {GauGau}
2006-05-17 [ O ] Converted english_gb.php from partial translation that needed language fallback to full translation {GauGau}
2006-05-13 [ C ] Fixed visibility issue for clickable options in fruity theme {GauGau}
2006-05-13 [ B ] Fixed missing translation in batch add {GauGau}
2006-05-10 [ B ] Fixed admin recognition issue in IPB bridge {Nibbler}
2006-05-09 [ D ] Updated screenshots in docs {GauGau}
2006-05-09 [ M ] Changed coppermine version from cpg1.4.5 to cpg1.4.6 {GauGau}
2006-05-08 [ B ] Replaced $lang_displayreport_php['invalid_data'] with $lang_report_php['invalid_data'] in displayreport.php {TranzNDance}
2006-05-08 [ B ] Fixed JavaScript error messages for crop and rotate {GauGau}
2006-05-08 [ B ] Fixed bug where input field was being saved for sender's name {TranzNDance}
2006-04-21 [ M ] Released cpg1.4.5 {GauGau}
2006-04-21 [ S ] Fixed remote file inclusion vulnerability {GauGau}
2006-04-10 [ M ] Re-added config.php and server_relocate.php to overwrite the outdated files when users upgrade {GauGau}
2006-03-12 [ A ] Added Georgian language file {GauGau}
2006-03-06 [ B ] Fixed redirecting back to original url after adding to favs {Nibbler}
2006-02-26 [ M ] CPG1.4.4 released {GauGau}
2006-02-23 [ B ] Fixed bug in charsetmgr {Abbas}
2006-02-20 [ B ] Fixing issue with smilie url prefix in admin comment notification {Nibbler}
2006-02-20 [ C ] Fixed some deprecated tags like <font> {GauGau}
2006-02-20 [ B ] Fixed help pop up in batch add section {GauGau}
2006-02-18 [ M ] Increased version count from 1.4.3 to 1.4.4 {GauGau}
2006-02-18 [ A ] Added partial Portuguese translation {GauGau}
2006-02-05 [ A ] Added Ukrainian, Slovak and Turkish translations {GauGau}
2006-02-05 [ A ] Added ukrainian language string to language selector, fixed slovak flag {GauGau}
2006-02-04 [ B ] Fixed reset password bug {Abbas}
2006-02-04 [ O ] Added function get_batch_add_album_list to get the personal albums for admin on batch add page {Abbas}
2006-01-31 [ B ] Fixed bug smilies coming broken in notification email {Abbas}
2006-01-26 [ D ] Added plugin section to docs {GauGau}
2006-01-25 [ C ] Fixed typo in dutch language file {GauGau}
2006-01-25 [ C ] Fixed typo in dutch language file {GauGau}
2006-01-25 [ B ] Fixed the Search Engine friendly URLs bug in displaying multipage thumbnails and albums {Abbas}
2006-01-25 [ B ] Fixed issue "gif can't be added to favorites" {GauGau}
2006-01-25 [ C ] Fixed css class glitch ("button" instead of "submit") {GauGau}
2006-01-24 [ A ] Added Ukrainian translation {GauGau}
2006-01-24 [ A ] Added Galician translation {GauGau}
2006-01-21 [ A ] Added Russian translation {GauGau}
2005-12-27 [ B ] Internationalized ecard button titles {TranzNDance}
2005-12-27 [ B ] Fixed issue with topn images not working in keyworded albums, provided by donnoman {TranzNDance}
2005-12-26 [ M ] Removed cpg1.3.x language files {GauGau}
2005-12-25 [ B ] Fixed Duplicate keys in $lang_picinfo in english.php {Donnoman}
2005-12-10 [ B ] Fixed selecting sample theme from admin.php {Donnoman}
2005-12-03 [ C ] Fixed project_vii css style which resulted in constant horizontal scrollbar {TranzNDance}
2005-12-02 [ C ] Fixed XHTML compliance and charset missing from picEditor.php {Donnoman}
2005-12-02 [ B ] Fixed moved title after setting the charset {Donnoman}
2005-12-02 [ B ] Added fix for showing correct number of tabs and pages when viewing lastalb meta album {Abbas}
2005-12-01 [ C ] Fixed minor typo in english.php regarding "Create intermediate pictures" {Donnoman}

As you can see, there are loads of bugfixes. As Nibbler suggested, some of them are higly security-sensitive. Others just fix "reguar" bugs, i.e. stuff that was suppossed to work, but didn't.

After running VersionCheck, I see only 6 areas that require upgrading.

Huh? Running versioncheck while still being on cpg1.4.3 is not meant to show you what files need updating. The tool is meant to show you wether you upgraded all files after having done so.

[Bruce]

Okay, well all things being equal, I think I will just stay with 1.4.3, then. I can't see any reason why anyone would want to hack my gallery - surely none of our alumni either would or have the skills to do so.

For anyone else into hacking .... why? Nothing there except pictures of our group over the years and music charts. So it's not a major concern - I'd just wipe it and reinstall everything, and if need be upload the updated package.

Fact is I do not have the skills needed to get into resovling the things I've seen questioned in this board, so the things people are doing to fix their problems are not something I can easily do. Or do at all. It took me long enough to get my theme more or less the way I like it, and modifying it to work with 1.4.10 just ain't gonna happen.

Obviously the vast majority of people on the support forum are experienced programming CSS, PHP, whatever, and GauGau's sometimes curt answers to peoples questions tend to illustrate a basic impatience for inexperienced users. I plainly am not experienced, and to try and learn it with the physical problems I have is not an option - and as a single individual doing this for a group even less knowledgeable than I on my own dime .... you get the picture - paying for someone to do it for me is out of the question, based on quotes I got to modify a simple theme.

I will just plod along with the current package and cross my fingers:)

[Sami]

Okay, well all things being equal, I think I will just stay with 1.4.3, then. I can't see any reason why anyone would want to hack my gallery - surely none of our alumni either would or have the skills to do so.

here is the reason for:
1. If you are on shared server then all other sites are on risk
2. Yes they maybe not interested on your pictures but Hackers could use your server for spamming or to hack another server (zombie) and this will cost you !

see this for live example :
http://forum.coppermine-gallery.net/index.php?topic=37760.0

[Joachim Müller]

I can't see any reason for someone writing a virus that ruins other's data, yet there are people who do that . There are exploits out there that just loop through random coppermine installs and hack them. This would mean at least extra work for you, lost data, extra costs (your webhost may charge you for curing the server), loss of reputation. As Sami suggested, your hacked server may be abused to spam people, host illegal material (warez, porn). Imagine being sued for hosting child porn. It will be you who has to prove that you have done everything to avoid being hacked. Apparently, you have not done everything: there are patches available, and you're aware of this. Deciding to continue using cpg1.4.3 is not a bright thing to do. Imagine someone knowing that the brakes of his car are not working. Yet, the person decides to drive the car, saying "well, I'm not going to drive in areas where people walk on the street". Guess what will happen if the person still runs over somebody by accident...
Of course a webiste is not a matter of life and death, but you can believe us that upgrading is MANDATORY (as in "either upgrade or uninstall the gallery").
What's wrong with upgrading? It's pretty easy and straightforward, no reason to be afraid of it.

[Bruce]

I can't see any reason for someone writing a virus that ruins other's data, yet there are people who do that . There are exploits out there that just loop through random coppermine installs and hack them. This would mean at least extra work for you, lost data, extra costs (your webhost may charge you for curing the server), loss of reputation. As Sami suggested, your hacked server may be abused to spam people, host illegal material (warez, porn). Imagine being sued for hosting child porn. It will be you who has to prove that you have done everything to avoid being hacked. Apparently, you have not done everything: there are patches available, and you're aware of this. Deciding to continue using cpg1.4.3 is not a bright thing to do. Imagine someone knowing that the brakes of his car are not working. Yet, the person decides to drive the car, saying "well, I'm not going to drive in areas where people walk on the street". Guess what will happen if the person still runs over somebody by accident...
Of course a webiste is not a matter of life and death, but you can believe us that upgrading is MANDATORY (as in "either upgrade or uninstall the gallery").

The difference is I am mechanically competant to do a brake job on my vehicle - I am not competant to diagnose and modify CSS/PHP/etc. From the messages and questions I have contributed to the forum - that should be evident.

What's wrong with upgrading? It's pretty easy and straightforward, no reason to be afraid of it.

A casual glance at the messages in this topic would tend to argue that point, GauGau. There are guys there with problems who have a huge clue how to "fix what's broken", while I on the other hand do not. Just attempting to make my theme work with the new upgrade would be a major hurdle, if other comments are any indication.

This is easy for people like you and Sami and others. It is NOT so for me. Just trying to follow the "simple upgrade instructions" had me scratching my head.

If you insist I remove my gallery - I guess I will have to do that and look for another product I might better understand....

[Joachim Müller]

Just attempting to make my theme work with the new upgrade would be a major hurdle

You don't have to modify your theme at all when converting from cpg1.4.3 to cpg1.4.10.

In fact, upgrading is very easy if you haven't modified core files.
The first step you should perform is running a backup. This is not mandatory in technical terms, but it gives you the opportunity to go back in case anything goes wrong. Having a backup is not only helpful when upgrading. After all, you should backup all your data from time to time. If you're afraid from upgrading just because you shy away from doing the backup, then skip that step: it's better to have the site upgraded without the additional safety of having a backup ready than not upgrading at all.
The next steps are even easier: just FTP upload the files from the cpg1.4.10 package over the existing files, run the upgrade script and you're done.

A casual glance at the messages in this topic would tend to argue that point, GauGau. There are guys there with problems who have a huge clue how to "fix what's broken", while I on the other hand do not.

There is a huge number of users who upgrade without issues. Those who don't have issues won't post on this board, saying "everything went fine". So you can't judge from the (comparatively small) number of upgrading threads that upgrading will be hard or troublesome.

If you insist I remove my gallery - I guess I will have to do that and look for another product I might better understand....

You have nothing to lose then - just perform the upgrade and see if it works for you.

[Bruce]

Well okay. I read the Docs on upgrading from 1.4.x to 1.4.10, and this is what it said specifically:

* First, make a backup (dump) of your database.

Okay - you say that is not mandatory, which is good because I don't have the slightest idea how to do that. Other questions pertaining to this did not give me a clue.

* Backup your include/config.inc.php file, your anycontent.php file and your "albums" directory.

You don't mention this - not that I understand how to do it anyway... How does one "backup" files on my FTP server?

* Unpack the archive

Okay, THIS I can, and have, done, in my Coppermine folder/1.4.10 The only thing I did there was delete all the theme folders because I won't be using them.

* If the file install.php exists in the root directory, delete it. When performing an upgrade, it is not needed.

If I understood this correctly, all I needed to do was delete the install.php file from the unzipped archives root directory.

* Except for the "albums" directory, upload all of the new files and directories making sure not to overwrite the include/config.inc.php file, your anycontent.php file or the albums directory.

Okay, HERE you lost me. Above you say to simply overwrite the folders/files. How does one backup an entire folder? Or those specific files?

* Run the file "update.php" in the coppermine directory once in your browser (e.g. http://yourdomain.tld/coppermine/update.php). This will update your coppermine install by making all necessary changes in the database.

This too is understandable even for me. Maneuver to the root directory on my browser and run update.php. Okay.

* If you have made a custom theme, apply the changes that were introduced in the themes structure to your custom-made theme - refer to the theme-upgrade guide.

This again is confusing, in light of what you said in your message. The theme-upgrade guide does illustrate the methods to update a 1.3.x series theme - not 1.4.x series theme. But it contradicts what the upgrade directions itself says. Therein lies the confusion.

Don't get me wrong - I like Coppermine a lot and would prefer to stay with it. In time I might learn enough to improve the look of my theme more. But there are enough problems listed in this board by well-experienced programmers to cause newbies like myself to have serious concerns about upgrading. True - it may not be a significant number considering how many users there are - but even a few are enough when one doesn't know how to fix things SHOULD they go wrong.

[Joachim Müller]

Okay - you say that is not mandatory, which is good because I don't have the slightest idea how to do that.

As I said: you should get familiar with it - if not for the sake of upgrading, then for the sake of preparing against a server crash.

How does one "backup" files on my FTP server?

You download the files from the server to your client using your FTP app.

Okay, HERE you lost me. Above you say to simply overwrite the folders/files. How does one backup an entire folder? Or those specific files?

As suggested above: download the entire coppermine folder to your client using your FTP app.

* If you have made a custom theme, apply the changes that were introduced in the themes structure to your custom-made theme - refer to the theme-upgrade guide.

This again is confusing, in light of what you said in your message. The theme-upgrade guide does illustrate the methods to update a 1.3.x series theme - not 1.4.x series theme. But it contradicts what the upgrade directions itself says. Therein lies the confusion.

Forget about this - in fact, you only have to apply this when upgrading from cpg1.3.x

[Gizmo]

Bruce, no one from here wants you to delete your gallery. As GauGau said, the number of people with issues who post here are very small compared to those who have no problems. Most problems arise because people didn't follow the instructions. I followed the instructions (to make sure they were right) and upgraded in 15 minutes. Another option for you would to be post for help on the Freelance board to backup and upgrade. There's even a sticky at the top of that board for someone offering to do this cheap. Be sure to backup your customized theme then reload it after upgrading.

[Bruce]

Bruce, no one from here wants you to delete your gallery. As GauGau said, the number of people with issues who post here are very small compared to those who have no problems. Most problems arise because people didn't follow the instructions. I followed the instructions (to make sure they were right) and upgraded in 15 minutes. Another option for you would to be post for help on the Freelance board to backup and upgrade. There's even a sticky at the top of that board for someone offering to do this cheap. Be sure to backup your customized theme then reload it after upgrading.

Gizmo, that's all well and good, but you are part of the development team and it still took you 15 minutes to upgrade - so how long would it take someone like me? Especially one who doesn't fully understand the directions you had to check to make sure they were correct. As I've said, I have serious short term memory issues due to extended surgery and life support, and I am unable to retain what I read easily. This is not a simple matter for me. Yes - I understand that is not your problem, and maybe with that  handicap I should not even be doing the work I'm doing, but I am trying.

I checked the stickys you referred to in the Freelance area. Unfortunately, they all require PayPal - which I don't do and don't use credit cards. So I am out of luck there, too.

I have, however, used my FTP and copied the entire gallery setup to a networked drive on my system. I have looked at various messages on doing this "dump" mentioned, and that just ain't gonna happen for me. can't understand a word of it.

[Bruce]

As I said: you should get familiar with it - if not for the sake of upgrading, then for the sake of preparing against a server crash.
You download the files from the server to your client using your FTP app.
As suggested above: download the entire coppermine folder to your client using your FTP app.

This again is confusing, in light of what you said in your message. The theme-upgrade guide does illustrate the methods to update a 1.3.x series theme - not 1.4.x series theme. But it contradicts what the upgrade directions itself says. Therein lies the confusion.
Forget about this - in fact, you only have to apply this when upgrading from cpg1.3.x

This might get a bit confusing if I nest these quotes again, but ....
1- I HAVE downloaded the ENTIRE gallery structure to a networked drive using my FTP app just now.
2- I have read and re-read the examples given on backup up the database. Not a chance of me figuring that out. That aside, my host package with 1and1.com includes backing up my account. I assumed that would cover me should their server go tits up. If not ... well .... I retain all my files locally anyway.

[Bruce]

Well, I just read a message from a "Hanna" concerned with backing up the DB. You recommended an app named "mysqlDum", which I have just downloaded. I'll take a look and see if I can make something out of it and give this a try.

Nothing ventured - nothing gained, eh?

[Bruce]

Okay, thanks to a few pointers from a programmer friend, I have successfully and with much trepidation gotten my database backed up. One down - one to go.

I will now screw up my courage and go for the update. Wish me luck!

Thanks to Sami and Gizmo for the support:)

GauGau ... if you please, would you close this thread out? If I manage to screw this up I doubt I'll be needing further help here.