Problem with patch v8.50

[RuralWeb]

Thankfully my upgrades all worked fine but I don't use external designs so maybe thats why! The sites disappearing is a strange one, mines all show correctly. And I could be wrong but Im sure the perl scripts will be overwritten on any upgrade, so you are using the correct verion of the scripts

Sounds like problems may be arrising because of the external design. When I tried the patch it worked until it started upgrading the site then it locked completly and I had to reinstall.

As for the scripts I dont know if every one is upgraded every time but Ive not had any problems on previous upgrades maybe Im just unlucky this time.

All my sites are now working Ok so i think its a case of the more customised your site is the more effect it will have - bit like V7 to V8.

[george]

Having said that (use the full install, not the patch), and reading of the problems with `the patch` so far, erm, why have one if its not stable to use?

[RuralWeb]

Having said that (use the full install, not the patch),

I always do use a full install but this time I thought I would try the patch just to see if it worked - obviously it seems to work ok on standard sites but has problems if you are using an external design.

So back everything up TWICE and give it a try

[george]

So back everything up TWICE and give it a try

I reckon you believe you're going to win the lottery one day too don't you Malcolm?

Mind you, I almost awarded a Goat Point for the `just sort out the forty sites I have theme`...

[RuralWeb]

you're going to win the lottery one day too

I can ditch this webdesign work then

[cdicken]

Hi chaps - I just want to provide a bit of input from Actinic's end if that's OK.

then you will need to go into programe files and rename the V8 folder that is left as the uninstaller does not work correctly.

The reason the 'Actinic v8' folder is not removed is that it still contains the 'Site1' folder, which was added after Actinic was installed - so the uninstaller doesn't remove it. I usually just rename this 'Site1' folder to 'Site1-backup' if I don't want it overwritten.

1. Any DW registered design will be lost

Not necessarily - but there are some differences between 8.0.4 and 8.5 in how the DW integration works. What you can generally do following an upgrade, if your external design is not visible within Actinic, is to go to 'Design' tab, select the outer layout and then click the 'Edit Layout Details' button. You can use the 'File Name' field there to ensure that Actinic is pointing at the correct location of your external design.

2. All sites will be removed from the file sites menu and you will need to re licence them using snapshots.

As I mentioned in the other thread, this is not a general problem with 8.5 - this is something very odd that happened with your installation. Re-installation was the best course of action to get you up and running again. Other customers will not have this happening to them. Thanks for flagging it up though - people really must take snapshots before they upgrade, and this is an example of why its a good idea.

3. External CSS files are lost

The solution I mention above (changing where Actinic is looking for the external design) will probably fix this.

4. Most perl scripts are overwritten - meaning any custom perl scripts will be lost eg checkout, norms plugins etc

Yep - this is so you can use the new shipping functionality. Unfortunately, we cannot upgrade scripts

Having said that (use the full install, not the patch), and reading of the problems with `the patch` so far, erm, why have one if its not stable to use?

I've asked for the patch to be taken off the website while we investigate the issues mentioned in this thread. Please bear with us.

[Simon Williams]

Not necessarily - but there are some differences between 8.0.4 and 8.5 in how the DW integration works. What you can generally do following an upgrade, if your external design is not visible within Actinic, is to go to 'Design' tab, select the outer layout and then click the 'Edit Layout Details' button. You can use the 'File Name' field there to ensure that Actinic is pointing at the correct location of your external design.

Chris,

If I understand you correctly (I had the problem with missing css themes, and DW missing layouts in my site folder), we need to save our custom css file, and DW design in a different directory than the site folder, and point to that folder for access to the files within Actinic?

Am I reading this correctly???

[cdicken]

You can put the Dreamweaver files wherever you want, but we have found that keeping them in the site folder makes it simpler to pass a site design from one PC to another via a snapshot.

Any additional CSS files should be saved in the same folder (at the same level) as the html design, but you can keep images in your own custom sub-folders and Actinic handles this OK.

Wherever the designs are kept, make sure that the 'File Name' field (within 'Edit Layout Details' in the outer layout) is correctly pointing to the design's location.

[cdicken]

Nick/Malcolm

Do you have the pre 8.5. snapshots still? (i.e. before you upgraded). We would like to test upgrading them and see what might have caused your issues.

If you could maybe upload the snapshot to a web site I can download it and pass it on to the team. My email address is cdicken /at/ actinic /dot/ co /dot/ uk.

Any help you could give would be very much appreciated.

[RuralWeb]

Site emailed to you.

[cdicken]

Nick - any news on getting a snapshot for me to test with?

Malcolm, one of our developers has carried out the following test on the snapshot you sent me:

*Test* *1*
Imported the snapshot to 8.0.4 GMVA.
Upgraded to V8.5.0 HBKA using the patch.
Reopened Actinic.
The DB and design upgraded without any errors.

*Test* *2*
Upgraded from v8.0.4 GMVA to V8.5.0 HBKA using the patch.
Imported the snapshot.
The DB and design upgraded without any errors.

Could you maybe expand a bit more on

it has crashed my V8 big style

What actually happened? What errors were received?

[Philip M]

Any Actual Answer to v8.05 upgrade?

I installed the patch for the upgrade and got this message - it has also informed me to use an earlier version of Actinic

What have I done wrong?

Failed to create new field [sBarcodeTemp] in table [Product] - fatal error.
Reported error was:

Too many fields defined.

Nick

HI Did anyone get around to actually answering the original problem, it is exactly the same problem that I experienced whilst upgrading to v 8.05 today, and I have uninstalled and re-installed on 3 ocassions now.
The annoying thing is that I have upgraded in order to correct an altogether diferent problem I have with cgi scripts and actininc support have told to me to upgrade from v 8.4 to 8.5 to correct the error, which ia another very long story (2 weeks)!!
New to forum but have a feeling I'm going to be spending some time here. Thank-you

[Bruce]

Philip,

Upload a copy of your v8.0.4 snapshot to your server and drop me a link with details as to what product you are using at bksupport / at / actinic / co / uk and i will take a look at this for you first thing Monday or earlier depending on when you drop me the link.

Kind regards,

[nikwak]

Chris

Site emailed to you today. Hopefully be able to find out what has caused this
Many thanks
Nick

[Bruce]

When you say, site emailed to you, do you mean you have sent me a snapshot via email? How big is it, let me know as if too big I will download this in office on Monday rather than at home.

Kind regards,