

My recommendation if you are having trouble doing Send/Receive with these changes, and you are using FW9.0 or earlier, and cannot upgrade to FW9.1.22/24 for some reason, do the following:
At this point you should be able to Send/Receive without a problem. This setting will be remembered, so it only needs to be done once in a given project.
Ken
From: flex...@googlegroups.com <flex...@googlegroups.com> On Behalf Of Timothy Haasdyk
Sent: Monday, November 27, 2023 4:23 AM
To: FLEx list <flex...@googlegroups.com>
Subject: [FLEx] Re: New Language Depot release - November 27th
Update:
The release has happened.
Currently, everything seems to be going according to plan.
On Monday, November 20, 2023 at 5:06:57 PM UTC+1 Timothy Haasdyk wrote:
Dear FLEx and Send/Receive users,
On November 27th (next Monday) we will be releasing a brand new version of Language Depot! This is an exciting milestone in the world of lexical data!
We expect everything to just keep working unless you are using FLEx version 9.0 or older (more information on that below). However, there are some things that you should take note of.
Maintenance mode
Language Depot will be in maintenance mode between 00:00 and 04:00 UTC while we migrate to the new version. During this time Send/Receive will not work and both public.languagedepot.org (aka public.languageforge.org) and private.languagedepot.org (aka private.languageforge.org) will be unavailable.
Merging public and private
As part of this release we will be merging Public Language Depot (public.languagedepot.org) and Private Language Depot (private.languagedepot.org).
Both public and private Send/Receive configurations will continue to work.
FLEx 9.0 and older
If you are using FLEx 9.0 or older it is likely that some Send/Receive configurations will stop working.
The most reliable option will vary depending on your exact version. If you can't Send/Receive here is what you should try:
1. If you have a Bandwidth field in your Send/Receive settings, prefer using Low Bandwidth:
2. Otherwise, you will likely need to use the custom location/URL: https://[your LD-login]:[your LD-password]@resumable.languageforge.org/[your project-code]:
If something stops working
Please let us know (this thread is a good place).
Swapping out a 13 year old system is no easy task, so please be gracious if we run into a few unexpected hurdles.
Why are we doing this?
The new version of Language Depot is the first step in modernizing the Send/Receive and language data tool set. Freeing ourselves from the current/old site will allow us to rethink how language data is stored and synchronized. It will also enable us to expand the feature set of Language Depot.
Warm regards,
The Language Depot development team
--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/7036bbb0-b6cc-4a9a-88c0-d9adc47c5e54n%40googlegroups.com.
Hi all,
I’m working on several collaborative lexicon projects and we do send-receives between different users in different locations quite frequently. I do need to use older software for various reasons, and while this custom URL worked for me as the project manager, it did not work for those listed in LD as having “editor/contributor” status. They keep getting the same error message that mentions they lack authorization, regardless of whether they change the URL or not.
Is there a solution to this? Would giving the contributors manager status solve the problem?
-Elaine Scherrer
2. Otherwise, you will likely need to use the custom location/URL: https://[your LD-login]:[your LD-password]@resumable.languageforge.org/[your project-code]:
If something stops working
Please let us know (this thread is a good place).
Swapping out a 13 year old system is no easy task, so please be gracious if we run into a few unexpected hurdles.
Why are we doing this?
The new version of Language Depot is the first step in modernizing the Send/Receive and language data tool set. Freeing ourselves from the current/old site will allow us to rethink how language data is stored and synchronized. It will also enable us to expand the feature set of Language Depot.
Warm regards,
The Language Depot development team
--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/7036bbb0-b6cc-4a9a-88c0-d9adc47c5e54n%40googlegroups.com.
--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/55a3cd08808e7c97cae4a3fd7d38af3c%40mail.gmail.com.
I don’t think that’s it, we’ve tried it multiple times with changing to https. It’s strange because it worked totally fine for me, but the others did exactly the same thing with no result, which is why I’m wondering if it has to do with member status in the project.
-Elaine
2. Otherwise, you will likely need to use the custom location/URL: https://[your LD-login]:[your LD-password]@resumable.languageforge.org/[your project-code]:
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/e0dbfcff-b525-43c5-85a7-1ed6b7577883n%40googlegroups.com.