BUG 5.1 RC1: BWS ignores the settings in the template
Comments
-
Dave
===Windows 11 & Android 13
0 -
Bump.
Mac Pro (late 2013) OS 12.6.2
0 -
Thanks to both of you for your persistence and for your long-term patience! Once you "grab ahold of" an issue, you stick with it! *smile* Many of the things you "lobby for" -- usually successfully! -- are beyond me and where I'm at; so I look upon you as my Forums Colleagues, leading the way.
Psalm 29:11
Philippians 4: 4 Rejoice in the Lord always; again I will say, Rejoice. 5 Let your reasonableness be known to everyone. The Lord is at hand..........
0 -
I am able to reproduce this issue and will create a case for Development.
0 -
Milford Charles Murray said:
Thanks to both of you for your persistence and for your long-term patience! Once you "grab ahold of" an issue, you stick with it! *smile* Many of the things you "lobby for" -- usually successfully! -- are beyond me and where I'm at; so I look upon you as my Forums Colleagues, leading the way.
I agree. fgh is doing all users a service by bringing these bugs to the attention of the company.
A big "tack så mycket" to fgh. [:D]
0 -
Thanks.
Did you google that, or did you actually know it?
Mac Pro (late 2013) OS 12.6.2
0 -
This will be fixed in 5.1 RC 3.
0 -
Kelly Flones said:
This will be fixed in 5.1 RC 3.
I've seen this note on a number of bug reports now (at least three today). It's nice to see that bugs are getting fixed, but I thought "Release Candidate" stage meant "only fix show stopping bugs, don't mess with the code anymore unless absolutely necessary: i.e., we think this is potentially the gold release unless something major comes up."
So I'm surprised to see that Development is going in and fixing so many bugs at this point instead of deferring them until 5.2 or 5.1a or whatever the next release is going to be called. It seems risky.
0 -
I knew "tack". The rest, I had to supply with some research... [:D]
0 -
Kelly Flones said:
This will be fixed in 5.1 RC 3.
I still get OpenText.
And I'm still wondering why OpenText is the default when Rick said it shouldn't be.
EDIT: Now I'm really embarrassed. I've been so busy writing posts that I've forgotten to actually download RC3.[:$][:S] I'll try again in a little while...
EDIT: Fixed for Grammatical Relationships, but not for Example Uses.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
And I'm still wondering why OpenText is the default when Rick said it shouldn't be.
Grammatical Relationships resources don't currently participate in resource prioritization, so we don't have a way to set a (user-overridable) default in the software. (Rick was probably assuming that it was possible, just as most other Cascadia resources are preferred over OpenText.)
I've made a note of this issue.
0 -
fgh said:Kelly Flones said:
This will be fixed in 5.1 RC 3.
(...)
EDIT: Fixed for Grammatical Relationships, but not for Example Uses.
Did someone notice this? It's not fixed in 5.1a RC3 either.
Mac Pro (late 2013) OS 12.6.2
0 -
Bump.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
Did someone notice this? It's not fixed in 5.1a RC3 either.
I cannot reproduce this in 5.1b Beta 1. Both Example Uses and Grammatical Relationships use Cascadia as their default.
0 -
If the default has been changed in beta 1, that's a good, but the 'unfixed fix' that I've been reporting and bumping was that Example Uses still doesn't respect my Setting. At least not in SR1:
Can you check that too in beta 1, please. (Of course, if the default has been changed to Cascadia, you will need to test with OpenText instead.)
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
Can you check that too in beta 1, please. (Of course, if the default has been changed to Cascadia, you will need to test with OpenText instead.)
My default was changed to Cascadia, so when I tested it with OpenText, I was able to reproduce this issue in both stable and beta. I have created a case for Development.
0 -
Thanks.
I don't know what went wrong here (and in dozens of other threads), but please do something so that in the future when I report that the same bug exists in two places -- Grammatical Relationships and Example Uses -- you don't fix it in just one place, report it as "fixed", and then ignore my report (and repeated bumps) that it is not. It is quite enough that I have to deal with the bug itself and the initial bug report. I really shouldn't have to spend hundreds of hours recreating and bumping threads again and again, and re-reporting bugs that are claimed to be fixed but are not. (And, believe me, I have spent hundreds of hours doing that -- if not more.)
Mac Pro (late 2013) OS 12.6.2
0 -
Angela Murashov said:
I was able to reproduce this issue in both stable and beta. I have created a case for Development.
This should be fixed in 5.2 Beta 1.
0 -
This does indeed seem to be fixed now.
Mac Pro (late 2013) OS 12.6.2
0
