Bug: 4.6c Beta mucking up 5.1 custom Series

I got a ping-pong effect when I changed the name of a prioritised Logos Series in v5.1 e.g.

change the Series name of Expositor's Bible Commentary, Abridged (EBC) in 5.1
have to re-Prioritize EBC as the effect is to show the old series name with 0 volumes!
after syncing, v4 shows the original Series name in Library, but shows the custom series name under Prioritize
fix that by re-prioritizing EBC series in v4
after syncing, v5 is Prioritized with original Series name and 0 volumes
have to fix that by changing custom series to original name AND re-Prioritize (showing 0 vols)
then I have to re-Prioritize v4 as that shows 0 vols after syncing.
And then v5 also shows 0 vols...!!!!

I found that the input box didn't show that I had two spaces between the comma and "Abridged" when changing back to the original series name, because it was split over two lines as shown below:-

I know that the custom Series metadata feature is not implemented for v4, but I didn't think there would be an issue with this as the changed Series name would be sync'd to v4 as a metadata change. And the same would apply to any custom Series that I defined. ??

Find more posts tagged with

Comments

Bradley Grainger (Logos)

In general, we try hard to make Logos 4.x and 5.x compatible, but this feature is 5.1-only and will not be back-ported to Logos 4. In this case, you have two mutually-exclusive choices:

Run Logos 4.x and 5.x in parallel and sync data between them
Use custom series in Logos 5 (and upgrade all installations to Logos 5)

Logos 4 is still supported for customers who cannot upgrade (due to an inability to upgrade from XP or OS 10.5) and so that promised Logos 4 features can be delivered in that version of the software; however, we recommend that anyone who can upgrade to Logos 5 do so.

It is likely that in future Logos 5.x releases, more features that introduce minor incompatibilities with Logos 4.x will be introduced, as we continue to innovate on the latest version of the platform.

Dave Hooton

https://community.logos.com/discussion/comment/480183#Comment_480183

In general, we try hard to make Logos 4.x and 5.x compatible, but this feature is 5.1-only and will not be back-ported to Logos 4. In this case, you have two mutually-exclusive choices:

Run Logos 4.x and 5.x in parallel and sync data between them

Use custom series in Logos 5 (and upgrade all installations to Logos 5)

I appreciate the state of affairs wrt support of v4 but was hoping this issue could be addressed by simulating a metadata update of the Series name. There is another choice, though, and that is to use the Series feature and sync with v4 provided I don't make changes to a Logos Series that is Prioritized (I'll see if Hayley will accept a Metadata Correction[:D]).

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/480183#Comment_480183

Logos 4 is still supported for customers who cannot upgrade (due to an inability to upgrade from XP or OS 10.5) and so that promised Logos 4 features can be delivered in that version of the software; however, we recommend that anyone who can upgrade to Logos 5 do so.

Curious what Logos 4 features have future delivery plans ?

Personally wonder when an annoying Logos 5.# regression bug on Windows will be fixed => BUG: 5.0a Hebrew text order backwards in Visual Filter on Windows + OS X Feature Parity Issues

Keep Smiling [:)]