Uh, yeah, when working with setup, there were errors. I know the difference, and realize that it was not setup that was showing me Internal Server Errors, but rather my host. If I tried the permissions dropdown, it would go to an Internal Server Error page. If I tried to hit Go at the bottom, Internal Server Error page. Only solution is to not ask setup to do anything, go back in via FTP and change back all the permissions, and tiptoe lightly out of setup without waking the slumbering beast. Host problem. Got it. OK. Though I still wish I could get setup to leave permissions alone completely.

As far as the theme goes ("day one" being October 2007 for me), if I should have upgraded to a newer version of default-dark at some point... again, might that have been noted in the upgrade instructions somewhere? You guys remind people an awful lot to go by your instructions explicitly and not use other scripts/etc, but at no point do I remember a suggestion to update "officially supported" themes - only to replace the home directory files and zp-core. Maybe this was dumb of me, but I had assumed (since they aren't mentioned) that as with cache and album folders, the rest could be left alone. I don't update with every new release, but I've updated a few times.

I mean, it's not like I was trying to carry forward some iffy third-party theme.

So, if I can scrap my old theme folder and replace it with a new one from the 1.3 package without everything going berserk, that's fine. I have been using default-dark with absolutely no modifications. I'll backup my current installation and give it a go. The theme does work as-is, but I wouldn't want setup to be unhappy about it. Or maybe I should stick with "don't fix what ain't broke."

I just wanted to explain the setup warnings once again..;-) The internal server error probably should not happen. We will see if sbillard will have any idea to prevent this.

Themes. You are right that the upgrade instruction do not tell to replace the standard themes. We should add that. But isn't it quite obvious that from 2007 to 2010 something might have changed, especially for standard themes, especially improvements or new feature support?
Not even all former standard are included anymore (example theme was thrown out) and Zenpage theme is actually newer as well (since somewhere 2008).

Especially custom/customized themes may nor work fully (that is why many on our theme section are marked as incompatible). If you use an old standard theme without any change just try and if it still works good for you that is great. We of course don't test older standard themes with newer releases.

Besides, setup did warn you about the themes even if the instructions were not explicit!

Umm, no, considering that the date on the default theme info page lists 12/12/07, it isn't "quite obvious" that anything at all has changed with it since just after I first downloaded Zenphoto.

I guess what I'm trying to express is that I do exactly what you recommend, I read the difference between warnings and errors, between a Zenphoto problem and a host problem, I check my compatibility (ok, so I stupidly assumed that my host had already moved me to PHP5, but I think that's forgivable), I read the directions, I search the forums before hounding you about problems, and yes I even went in to the themes page to make sure I wasn't clinging to some hopelessly outdated theme from yesteryear.

Default still comes with the full installation package (the very definition of "default"), still marked as officially supported, and maybe I'm being dumb again, but if something is dated 2.5 years ago on your official pages I tend to suspect that it has not been modified since then and there's no need to go against your written upgrade instructions and replace the themes folder, considering that the convention with any other bit of software I've ever downloaded - patches, full installers, drivers, etc - is to mark the information page with a version number or at the very least a modification date.

What is most amazing is that you mention that you "of course" don't test your default theme with new releases. What's the point of having a default, included theme at all then?

The date of the theme is the date of creation of the design itself actually, not necessarily all the code... I admit that is a mistake and agree we should update those dates. I appreaciate that as I actually have never thought about that. Sorry.

[i]What is most amazing is that you mention that you "of course" don't test your default theme with new releases. What's the point of having a default, included theme at all then?[/i]
No, I actually said "We of course don't test [b]older[/b] standard themes with newer releases" and meant "older versions" of those themes. We of course test the theme but just the current version of it. (Just to note that English is my 2nd language so sometimes I am thinking in my 1st....)

Generally we try to make most things backward compatible by not changing standards but not always that may work out.

Well, like I said. I'm trying to follow what's on your pages and forums - your comments and contributions, not other users, who may have completely different factors to their problems. I am not slamming through dumb guesses and kludgey homebrew workarounds - as I mentioned I am not a programmer and do not understand the consequences of making it up as I go along. So I don't do it. Instead I've been reading and following steps religiously.

At any rate, the permissions thing still bugs me when I run setup if anyone has any thoughts on that. I am about to rip out my themes folder and move in the new one, hopefully that will be fine.

Thank you for all the help, and as for "Besides, setup did warn you about the themes even if the instructions were not explicit!"... yeah. I know. That's why I asked about it in the first place. I guess I just didn't realize that I was supposed to assume unwritten upgrade steps, since the rest of the documentation is pretty clear and concise.

We appreciate your notes about our instructions not being clear in parts. It's too easy to leave out things for others if you are too used to them yourself.

Thanks - I noted the revisions in the upgrade instructions. Hope this doesn't feel like you had to dumb it down too much, but with the small mods it is much more clear (to me, anyway).

I had also this error when migrating from v1.2.4 to v1.3.
In my case, I only had to change PHP version (from v4.xy to 5.2) on my webserver (done throw a code in .htaccess at the root)
No more problem now.

Just an FYI, in the nightly builds there is now a check for PHP5 to make sure that this error won't occur.

Please help !!! I just upgraded to 1.3 and got exactly the same error:

Parse error: syntax error, unexpected ',', expecting '(' in /homez.65/patrician/www/albums/zp-core/lib-Imagick.php on line 79

I am quite desperate, especially since I cannot understand exactly from the discussion above what has to be done to correct this error.

Thanks a lot in advance

The script checks for PHP5 in the nightly builds. lib-Imagick.php should be able to be independently updated from Zenphoto's core files, so you could either try using the nightly or simply replace the aforementioned script.

It is possible, however, that your server is lying about having PHP5 and Imagick available, in which case only your provider can alleviate this problem.

Thank you very much for your quick answer.

I uploaded the nightly build, but unfortunately got the same error:

Parse error: syntax error, unexpected ',', expecting '(' in /homez.65/patrician/www/albums/zp-core/lib-Imagick.php on line 92

Where can I find out whether I am using PHP5?

I just re-read the technical details given my provider. It says for my subscription:

PHP 4 Inclus
PHP 5 Inclus
PHP 5.3 Inclus
PHP 6 Inclus

Your provider may give you the option to switch between PHP versions. I would assume that you're currently running PHP4, though your server reports it's running PHP5. I know that my provider allows me to switch PHP versions through CPanel, for instance. If that fails, you will need to contact your provider about the issue.

Contacting the host is the best (mine allows switching via htaccess, just to add).

Thanks for your advice.

I changed the htaccess, writing SetEnv PHP_VER 5, according the host advice.

I manage now to open the setup but I get flowing message under "htaccess"

Error!
The .htaccess file in your root folder is not the same version as the one distributed with this version of Zenphoto. If you have made changes to .htaccess, merge those changes with the zp-core/htaccess file to produce a new .htaccess file. Click here to have setup replace your .htaccess file with the current version.

If I click I get again the same error (imagick...).

You should do as the error message says. Compare the .htaccess file you have with the template in zp-core. (That one does not have the period in front of the name.) Make sure that all the lines from the "template" are in your new copy.

If you have never modified the .htaccess file before then you can just add your line to the template, move it to the root folder of your installation and rename it .htaccess.

I managed this. The error message for the htaccess disappeared, but now I get an error message for MySqlSetup

Access denied for user 'adminXXXX'@'10.0.70.30' (using password: YES)

Well, at least that is progress

This error indicates that the user id and password you gave Zenphoto for access to your database is either incorrect or the user had not got the priviledges to let Zenphoto access the database.

If you belive the user/password is correct you will have to contact your provider to see what might be wrong.