Warning: readfile(layout/footer.html): failed to open stream

[GoogleCodeExporter]

What steps will reproduce the problem?
1. patch_102.zip
2. Update from 1.0.1
3. http://website/calendar/setup

What is the expected output? What do you see instead?
Should load the setup page

What version of the product are you using? Which browser / php version are
you using?
It's now showing 1.0.2 on the calendar itself but I did not run the update.
Chrome

Please provide any additional information below.

Original issue reported on code.google.com by try...@gmail.com on 23 Nov 2013 at 7:42

[GoogleCodeExporter]

i have brought it back to 1.0.1 in the meantime

Original comment by try...@gmail.com on 23 Nov 2013 at 7:53

[GoogleCodeExporter]

The patch does not contain all setup files, only those which changed. Make sure 
to copy the setup folder from 1.0.1 before applying the patch or use the setup 
folder from the full 1.0.2 package.

Please note that patches do not require a database setup unless the second 
number in the version changes. So 1.0.x to 1.0.y does not require a database 
update, while 1.x.x to 1.y.y does.

Original comment by arne.cl...@gmail.com on 23 Nov 2013 at 8:00

[GoogleCodeExporter]

Please confirm if the error persists with a correctly patched setup folder.

Original comment by arne.cl...@gmail.com on 23 Nov 2013 at 10:44

• Changed state: NeedsMoreInfo

[GoogleCodeExporter]

Still have an issue.  

Copied only the setup directory from the Full 1.0.2 and then copied the patch 
1.0.2 over.

When I load website/setup  and click the update button; 

it says
Database connection Ok
Detected version 1.0.0
No update necessary.

Though on the login page itself it shows 1.0.2

Original comment by try...@gmail.com on 24 Nov 2013 at 12:17

[GoogleCodeExporter]

Unless I understand that is all that is needed and the update does not need to 
be ran as it's not affecting the DB as you say.

Just thought it would show 1.0.2 rather than 1.0.0 in the Detected version

Original comment by try...@gmail.com on 24 Nov 2013 at 12:20

[GoogleCodeExporter]

The database version will always be pinned to "major.minor". The last number in 
the version string denotes the patch level which does not affect the database. 
The fact that the patch level is still displayed in the update dialog is a 
relic from the pre 1.0.0 versions where patch levels DID change the database.

I guess I will change the strings in the setup tool to avoid future confusions.

Original comment by arne.cl...@gmail.com on 24 Nov 2013 at 9:11

• Changed state: NoBug