Brief
We have fixed the 'va_functions.php' file for release 3.5.
 
Description.
Email notifications were not sent if PHP is running in Safe Mode environment.
 
Solution.
We would recommend to download an updated version of the file from here: http://www.viart.com/downloads/va_functions-3.5.zip
 
Further, extract the above mentioned file into the 'includes' folder of your shop replacing an existing one. Don't forget to make a backup copy of the current file in case something goes wrong.
 
Important! Since the file is encoded please use BINARY mode while transferring it via FTP.

...and the full distribution has been updated Eugene?
 
:ranting:

Sorry, Ned.
We have not still came to a consensus about updating full distribution after fix issue.

Surely you mean _before_ fix issue????

Eugene, how about a link in the download area pointing new downloaders to this forum to pick up their patches.
That would allow the new downloaders to get the interim fixes as well as not confusing support about which file version what user has.
I am very happy with the speed at which patches are coming out but I see the problem where people who don't know to come to forums won't get their bug fixes.
I also see the problem of updating the download zip every other day without making it a new release. That would drive me nuts working out which version I'm on

Ive had a response from Natalia to say that ViArt are planning to rebuild 3.5 full download with all the latest patches.
 
jty - ViArt wouldn't need to update the version number each time just the appropriate files within the archive. New Users or those of us who wanted to catch up on several changes could download the full archive - otherwise if we are tracking the announcements just pick up the individual patches as they come out.
 
Do remember that one of the significant changes in the latest versions is that if you specify a "foobar" layout ViArt looks for templates first in "templates/foobar" and if it cant find one reverts to "templates/user". Thus upgrades are much easier for customised sites.
 
Whilst your idea of a link to the forum is a good one its a bit like saying "Please download our superb software from here - but to get the latest upgrades look through our announcements and download our patches and we hope you don't miss any!" Not exactly inspiring to a new user!

I downloaded Viart 3.5 when it came out and noticed there was a silent update done. First compilation was something beginning June and when I re-downloaded recently the compilation date of files had changed to June 16.
 
Silent updates like that kill a good product, I really hope Viart change this and just issue service packs which allows for controlled upgrades.
 
DickS

Sorry Dick I disagree. The upgrades have not been silent, they are fixes mentioned in Announcements and now rolled back into the full archive.
 
The whole point Ive been making here and elsewhere is that for new users (who may not have a programming background) the product you download should be the latest and most up-to-date.
 
In your case you have been tracking changes and upgrading as you go along but if you were unsure about missing something (illness/holiday/ etc) you should be able to go back to the full archive with confidence.
 
I think if (as a new user) you had to download the base package and then service packs to overwrite it you would end up questioning the viability of the product.
 
On a practical note I see that the whole zip archive now has all files with a datestamp of 20th June. Im unhappy about this because keeping the original datestamps would allow us to see the changed files and thus track changes.

I would agree with Ned.
 
As soon as the patches are released, they should be incorporated into the Final Distribution. So that the new user does not have to download the full distro and then apply the individual patches separately.

Agree with Ned and Ibn under the condition that there is a changelog. There is none, so it is hard to backtrack changes and possible implications.
 
DickS

I aggree. i must say i find it impossible to track changes as...
 
- theres no official online up to date changelog
 
- announcements made of patches are released somewhat silently (without email notification possible) in one location for various current/old releases of viart visible all on the same page
 
 
Note, the manual does have some kind of changelog... but as the manual is very very out of date it only goes to v3.1 i believe.

Question: if an update falls in the forest and nobody knows how old it is, did it really happen? In Viartland, nobody knows . . .
  
Whaaaaaaaaa? Consensus? A system for application releases, version numbering and tracking has been developing since the 1950s. The accepted standards have been pretty much set since the 1980s. Why doesn't Viart just use these accepted practices?
 
It could be THAT easy.

Hi All,
 
In order to make update process easier we have the aim to implement online Changes Log tool on viart.com, so it will be possible to view changes in files between different version numbers, e.g. between 3.4.16 and 3.5.
 
WBR
ViArt Support Team