Re: Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed, posted by Stefan Ritt on Mon Apr 30 21:01:49 2007
|
| Alan Stone wrote: | We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan |
Have you tried to delete your cookies in the browser and try again?
The location of top.html has been changed from the ELOG root down into the loogbook directory. If you want to keep it in the original location, you have to specify the full path. See the documentation for where to put the file for "Top text". |
Re: Upgrade to 2.6.4 broke quick search, posted by T. Ribbrock on Tue Mar 6 17:03:43 2007
|
| T. Ribbrock wrote: |
[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back [...]
|
Apparently, this must have been some session-oddity - I just logged out and got an error message about a bad URL. I then went to the base URL of the logbook (i.e. http://server:8080), chose the correct logbook and logged in again. Things work fine since. No idea what went wrong the first time round... 
Regards,
Thomas |
|
Re: Upgrade from 2.3.8 to 2.6.0 logbook problem, posted by Stefan Ritt on Mon Dec 5 17:11:33 2005
|
| Jesse Wodin wrote: | | Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow? |
No. The last change in the logbook format was for version 2.0.0. So something else must be wrong. Just creat one entry with your new elog, and see where it's created on the hard disk. Put your old logbooks there. If you start elogd manually with the "-v" flag, you will see it indexing all logbooks. Check that you see all your entries there. |
|
Re: Upgrade from 2.3.8 to 2.6.0 logbook problem, posted by Jesse Wodin on Wed Dec 7 02:32:00 2005
|
Thanks, you were right, it was just a permissions problem on the logbooks, which I had copied over as root.
j. |
Re: Update request for Admin Guide, posted by Stefan Ritt on Thu Nov 20 17:51:53 2003
|
Thanks, I added a note into the admin guide. |
|
Re: Update, posted by Andreas Luedeke on Tue Jun 30 17:15:18 2020
|
When you update from a version 2.* to a version 3.* then all elog entry files will be moved in subfolder for each year. But non of the entries are lost.
Only if you afterwards try to start an old version 2.* with the newly converted data directories, then the old version will not find any of the entries.
I've updated the ELOG version many times now. The only data I once lost was a modified CSS style file and a "hand modified" configuration of the ckeditor.
| Lahreche Abdelmadjid wrote: |
|
Hi,
How to do the last update with out losing any data ?
Regards
|
|
|
Re: Up to date windows version, posted by Antonio Bulgheroni on Thu Oct 20 10:10:12 2022
|
I'm also supporting this request.
> Dear Developers
>
> I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the linux binaries. Have anybody been able to compile a windows versions since 2018?
>
> Kind Regards Finn |
|
Re: Up to date windows version, posted by Laurent Jean-Rigaud on Thu Oct 20 13:13:16 2022
|
> Dear Developers
>
> I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the
linux binaries. Have anybody been able to compile a windows versions since 2018?
>
> Kind Regards Finn
Hi,
We discussed on windows build some weeks ago and i tried to make one to check if it’s possible.
The result is in https://elog.psi.ch/elogs/Forum/69491
This could help you up to official new build.
.
Laurent |