Photo Gallery Forums

Hi

I am French. I would like to buy a imagevue license. I tried the trial version before to be sure and see if everything works well on my NAS.
i have an error that you can see here : http://adrien-floch.com/imagevue/
You can also see the imagevue-checke.php here : http://adrien-floch.com/imagevue-check.php

As you can see the open_basedir is not desactivated but i desactivated it
All files are in CHMODE 777
my web server run on NAS Synology 210j with DSM 4.1

I don't understand why i have this error, if you could help it will be very very nice.

Thank you very much

I could take a look if you can provide the ftp login to your server.

I sent you private message with all information for ftp

Thank you very much for your help

There seem to be some hidden @eaDir folders everywhere. Imagevue tried to move it to iv-config/themes since it thinks this is the theme from the old version. Then it tried to upgrade the XML inside what it thought is a theme folder and failed.

So after commenting migration out it works but full of @eaDir's now:

http://adrien-floch.com/imagevue/

Also iv-config/themes is not accessible from ftp so you might experience issues in the future with themes.

Thank you very much Nick

Yes lot of @eaDir folders everyWhere. It's folders make by Synology System i f delete them they build again by the system. So i delete @eaDir in Manage section in the administration and it looks work well. They are not really delete but not reade by Imagevue. Yes in theme i have a @eaDir them i can't delete it but i think it's not a big problem.

Thank you again.

Now i am testing and i think buy it soon

We have already added a workaround for the migration issue, so this won't be a problem in the future. The @eaDir folders will be visible though.

Hi imagevue,

I face the same problem when i host my website on Synology 212J. Same error appear.

How to fix it.??

HELP!!

Since I couldn't login with the credentials you have provided I can only assume you are uploaded the fresh copy of Imagevue on this NAS and the migration issue got back. You can try to upload the iv-include/migration.php from the previous NAS, or even better - simply replace it with an empty file.

If this is the same problem - this should solve this. And, by the way, we have added the workaround for the next update.