Does the 4.0.15 package contain the correct files?

**Alfa1** · November 8, 2016

There doesn't seem any change between 4.014 and 4.0.15

**pegasus** · November 8, 2016

You appear to be correct. The 4.0.15 package was serving 4.0.14 files. I have cleared our backend cache again, and it looks like I am getting updated files now. Please try now.

**Alfa1** · November 8, 2016

I am afraid the package is still the same. At least the update goes through without a problem and bugs slated for 4.0.15 are still there.

**pegasus** · November 9, 2016

I have checked your site, and based on some behaviors that I know were changed in the front-end, it appears that 4.0.15 is on your web site and is working. If you think some PHP files were not updated, I invite you to submit a private ticket for a more thorough investigation of the file system. It is possible that you did not upload all the files (something you have noticed in the past), that some old files are still cached, or it is possible that we missed something.

**Alfa1** · November 9, 2016

I will delete the VW files from my server and reupload. This should guarantee that no old files are on the server. I will also disable and reenable VW and re-run the upgrade script and rebuld cache.
Then I will report back.

**Alfa1** · November 9, 2016

I have deleted all 4.0.14 files from my server. Then uploaded 4.0.15
I have downloaded the files from my server and checked the version. The downloaded files list 4.0.15 as the version and the content is the exact same as the downloaded package.
After upgrade to 4.0.15 my site still has the same issues as 4.0.14
I have rebuilt all caches in admincp and also disabled/reenabled the addon.
No change.

IN a previous case there indeed was an ftp problem but deletign old files from the server fully resolve that. This seems to be another matter.

**pegasus** · November 9, 2016

Please note that not all issues that were reported in 4.0.14 are fixed in 4.0.15. Only the ones that were marked as Fixed in 4.0.15.

If there are issues that are still occurring for you in 4.0.15, then it may be a specialized case, and you should consider a private ticket if the issue persists.