I have 4 zenphoto installation, but I don't like upgrading each one, one by one.

Is it possible to have a single zp-core, and symlink the others to my 'main' one? Or will this cause significant issues/problems in the present and/or future?

I tried to search for this question, but I was not successful in finding an answer.

-felipe

No.

We think this is possible for the zp-core folder. All data is stored in the zp-data folder so there should be no conflicts. However, this is not something we have tested. The only possible issues would be with third party code we have used that may be storing things locally.

Please keep us posted on your efforts here.

The only possible issues would be with third party code we have used that may be storing things locally.

By 'locally', do you mean inside the zp-core directory?

I would be worried that the data contained in "global-definitions.php" file (inside the zp-core folder) would point in a wrong direction if you do that.

Besides, if things work the way you hope, you would need to upload all files once (instead of 4 times), but you would need to run the setup script four times anyway, so that each installation refers to its own Albums folder and database.

../zp-core/global-definitions.php have the same md5sum hash .... ( ? )

About the upgrading, yes, you are correct, would need to run "setup" 4 times. But this might make things easier ... ( ? )

anyways, thanks for replies, I shall create a test env to play around with.

I would be worried that the data contained in "global-definitions.php" file (inside the zp-core folder) would point in a wrong direction if you do that.

There is actually no "data" contained in any script file. The data the script might create is part of the PHP execution state. That state will be different for each install.

By "locally" I do mean witin the zp-core folder. I have not seen any of these plugins actually generate any such local storage. AjaxFilemanager did once-upon-a-time do this but we have configured it to store its things in the zp-data folder now. Other code might do similar tings under circumstances that we have not created. But probably not. We do "notice" when unexpected files are made--setup tells us of their presence. So I guess that as long as setup does not suggest any files to remove you are safe.

I have been doing some experimentations with the shared code concept. First, it does not work out of the box. Not because of any improper writing to the core, but because of the way symlinks and PHP interact.

That is the bad news. The good news is that it probably can be made to work. The dev branch of tonight's build has the first pass at fixing all the places that get confused by symlinks. Seems to work for me, but really needs more testing.

So, this is a request for anyone with an interest in the feature to put the development build through hoops to see what shakes out. Use the ticket system to report problems.