Actinic v7.0.6

[jont]

But would the upgrades not be part of version 8, ie have to be encountered sometime anyway?

v8 will be a true upgrade and will bring along its own unique problems... I don't imagine a full rebuild of the main program (as it has been confirmed will still be static HTML and not database driven - may be wrong) so it is likely some of the issues of patching between say 7.0.4 and 7.0.5 could be carried over into v8.

In most software patching is a temporary fix - when a new version is released it is sometimes possible to build it from the ground up so some issues are resolved that patching cannot sort. With a program as complex as Actinic and the inifinite number of variables (as well as infinite variations on the machines it has been installed on to) someone somewhere is going to experience a problem when upgrading or patching.

My main site is so heavily patched and modified I will keep that in v7.0.4 (just not worth the risk of patching or upgrading as it is working perfectly) and the others will be upgraded or created in v8 when available. With the web sites being a great generator of revenue I fully subscribe to the "If it ain't broke don't fix it philosophy"

[Duncan Rounding]

I have Developer and have one site running at 705 that I'm reluctant to upgrade as it's working fine. However I want to work start work on another site - can I do that at 706 without affecting my site running on 705?

The answer to this was no - the upgrade would affect the other site.

Then jont mentioned:

My main site is so heavily patched and modified I will keep that in v7.0.4 (just not worth the risk of patching or upgrading as it is working perfectly) and the others will be upgraded or created in v8 when available.

Does this mean that V7 sites and V8 sites could co-exist with developer?

[wjcampbe]

Should be yes, different full version = different installation folder (e.g. Actinic v7/Sites etc) and different registry keys.

It's the keys that kill attempts to have multiple minor versions (7.0.2/7.0.4/7.0.6) on the one machine - all these use the same registry keys, so you end up with only one installation registered and the others are orphaned.

[pinbrook]

my motto is always - unless you need the fix in the new patch don't upgrade until everyone else has as then you will know about the knock on effect.

As Jont says there are always little suprises packed inside a new patch that may break something that did work before.

Negative attitude I know, but I think that all seasoned developers work this way, and that is a reference to all software and not just actinic.

[Nige]

Upgrade to v7.0.6

I upgarded my site yesterday to the V7.0.6 and have now been having a number of problems including Actinic freezing up and then having to shut down when trying to send an e-mail to a customer.
It may be coincidental but wondered if you can remove the patch and go back to v7.0.5 ?
Wish I had read this forum before upgarding just assumed that everything that a patch does would be for the better.

[cdicken]

I upgarded my site yesterday to the V7.0.6 and have now been having a number of problems including Actinic freezing up and then having to shut down when trying to send an e-mail to a customer.
It may be coincidental but wondered if you can remove the patch and go back to v7.0.5 ?
Wish I had read this forum before upgarding just assumed that everything that a patch does would be for the better.

It isn't possible to install a 705 on top of a 706. The closest you could get to this is by uninstalling 706, reinstalling 705 and then importing the backup 705 snapshot you took before upgrading. You'll lose everything you have done since upgrading though, so I understand if that is not a real option.

Failing that - I suggest you take a backup snapshot of your 706 and then uninstall Actinic and reinstall a full version of 706 (not a patch). Then import your 706 backup snapshot into it.

[george]

Thinking aloud, would that mean, in my case for example, it would be best to download the full version of 7.0.6 then import my 7.0.2 snapshot to see how it goes? That would maybe reveal some issues BEFORE going live with the new version and old version snapshot? Without touching the download/update commands obviously.

Hope that makes sense.

[cdicken]

Hi George

That does make sense, and sounds like a good idea. If you do that, you could use the 'Web | Switch to Test Mode' function to upload your 706 store to a sub-folder on the server for testing purposes and leave the current site alone.

You can then always re-install 702 and go back to it in case anything is a bit weird.

[richardh9999]

Working now - thanks Chris.

Doesn't seem to be working for me. Still only shows 7.05 details.

[Duncan Rounding]

You're right, the link seems to have reverted back to the old page. It was working for while.

[cdicken]

I just get information about Actinic when I click on the link! How strange.

I have attached a zipped up copy of the 7.0.6 release notes to this post so you can see the changes.

[TraceyHand]

any upgate on how 7.0.6 is going in use?
I have daily problems with the shipping in 7.0.5 and would be very interested to know if this is really fixed now? (and what, if anything, suffers as a result!)

[cdicken]

Hi Tracey - I've put an answer to your questions here:

http://community.actinic.com/showthr...7130#post97130

Let's continue the thread there.

[bekyed]

If it aint broke don't fix it

Enough said i think.

Wayne.

[TraceyHand]

yeh, but fact is Wayne, for ME, it IS broke!!