Perhaps I am missing something but I could not find a "New To You" option for the Classic Commentary Bundle in the Christmas sale - https://www.logos.com/product/129643/the-complete-classic-commentaries-bundle-30
I would love to know which resources I'm missing -
I don't know if it's a new trend or an oversight to leave off the Individual Titles section for some of these sale bundles, but it's been occurring more frequently.
The lack of details currently make it harder to determine what's new, and more importantly, total up the individual costs of resources within the bundle.
I hope FL will get back to providing more disclosure on the product pages, instead of making it appear that there is something to hide.
Still, at $41, you're probably missing more than $41 of resources. It might be faster to buy it, look in the library to see which resources were added, then ask for a refund if not satisfied, instead of waiting for the product page to be fixed.
They're in there. You have to scroll as all the way to the bottom, click on the link that lets you see all the resources, then find the couple with the New To You medallion/icon next to them. It's a little obscure, but it's there.
I was looking for the actual button but I guess I can do it the old fashioned way. What a pain, but is works.
They're in there. You have to scroll as all the way to the bottom, click on the link that lets you see all the resources, then find the couple with the New To You medallion/icon next to them. It's a little obscure, but it's there. I was looking for the actual button but I guess I can do it the old fashioned way. What a pain, but is works.
That's been the trend, making it difficult to price the new items, as you now have to visit each page, and sum up the prices by hand.
The two sections have to be configured independently by Faithlife. (The new method shows products contained in the bundle, the old method shows resources contained in the bundle.) We've only ever had the new method for small bundles (easy to configure), or popular products (e.g. base packages). They really need to do a complete re-architecture of the entire store to make it possible to add this facility to every product, as it's too much manual work at the moment. I don't know if that's likely even in the medium-term, but it will have to happen eventually.
That's been the trend, making it difficult to price the new items, as you now have to visit each page, and sum up the prices by hand. The two sections have to be configured independently by Faithlife. (The new method shows products contained in the bundle, the old method shows resources contained in the bundle.) We've only ever had the new method for small bundles (easy to configure), or popular products (e.g. base packages). They really need to do a complete re-architecture of the entire store to make it possible to add this facility to every product, as it's too much manual work at the moment. I don't know if that's likely even in the medium-term, but it will have to happen eventually.
That's either a design problem with the store, or a performance problem where they can't afford to query the store to show dynamic data.
I agree that there's too much manual work involved. All this should be as streamlined and automated as possible, to remove and eliminate human error, or delay resulting from human need to fix human error.
They really need to revamp how things are done, as independently configuring any (static) data for each page only leads to errors since it becomes challenging or impossible to keep different sections/sources in sync.
I never worked for Microsoft, like Bob did, but I used to be an MCDBA and MCSE+I, and still tinker around with schemas as a hobby now. I suppose it makes it more frustrating, since I can't fix things myself, and am at the mercy of FL to resolve it.
Programmers, administrators, we're all a lazy lot, preferring to get the system do as much as possible for us, to monitor, handle, and report on any tedious/repetitive tasks. Even if FL doesn't re-architect everything, I know they still could catch and fix problems before these collections are live (or courses/resources are released to the public).
I still regularly write Perl scripts, mostly for reports or to wrangle data to import into persistent stores. I suppose that's why I love Logos so much, because someone else did all the hard work I'm routinely familiar with to allow us to perform so many different queries, and return such a wide variety of Biblical results.
It's a design issue. The store has really outgrown its design constraints. When it was first designed there were very few bundles/collections. Most users bought individual resources. That's all changed, and although there have been significantly developments to better support bundles/collections and everything that goes with it (dynamic pricing, "new to you", etc.), the underlying architecture is creaking. It will be a massive project to re-engineer it.
That's either a design problem with the store, or a performance problem where they can't afford to query the store to show dynamic data. It's a design issue. The store has really outgrown its design constraints. When it was first designed there were very few bundles/collections. Most users bought individual resources. That's all changed, and although there have been significantly developments to better support bundles/collections and everything that goes with it (dynamic pricing, "new to you", etc.), the underlying architecture is creaking. It will be a massive project to re-engineer it.
I am sympathetic regarding the amount of time, money, and effort it will take to future-proof a new architecture, and I can appreciate that FL came a long way from its simpler beginnings. But they waited a long time, and we have to wait longer for them to eventually fix it for good. In the meantime, I hope there will be an interim solution to eliminate a) the tediousness of us having to figure out pricing or some such, by hand, and b) us having to stumble on and report issues with product pages, especially in regard to pricing.
I also hope they won't use any current (or future) production store to work on bundles they're still testing/configuring. If the have to take products down before they truly were ready to go live, they really shouldn't have been put up in the first place.
It's not a test bed; we shouldn't be exposed to these different sorts of issues. In short, I'd just like to be a (happy) customer, the program is great, but when it comes to getting product/pricing issues resolved, it's been more like death by 1000 paper cuts.
