You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Where there are two versions above, the first is the production and testing system for 1.27 and the second is where we are staging an upgrade.)
Issue
I'm guessing this has something to do with the size of the Glossary.
I don't know how to count the number of entries, but a user reported that SG had stopped working in production (1.27) while it was working correctly in an almost identically configured test system (1.27) but not in our staged upgrade system (1.34).
After a laboriously tracking down the problem, I found reason the 1.27-test system was working was because caching was different.
Setting $wgexLingoCacheType = CACHE_NONE; and using the following diff against src/Cache/ElementsCacheBuilder.php led to it working in the production 1.27 system:
(I think 1.34 will work, too, but I'm rebuilding data at the moment... will check back when it completes.)
I ended up using the above diff because I noticed the weird if ( $page ... above. I tracked down the static to the refactoring that removed SemanticGlossaryBackend. I'm not confident that my work is correct, but at least it allows the glossary to work when Lingo caching is turned off.
The text was updated successfully, but these errors were encountered:
Oh... yeah, I say this is a problem with a large(ish) glossary because even though the original report was that it wasn't working at all, I noticed that some of the earlier entries were being loaded (up to the C's) but none of the later ones.
Setup and configuration
(Where there are two versions above, the first is the production and testing system for 1.27 and the second is where we are staging an upgrade.)
Issue
I'm guessing this has something to do with the size of the Glossary.
I don't know how to count the number of entries, but a user reported that SG had stopped working in production (1.27) while it was working correctly in an almost identically configured test system (1.27) but not in our staged upgrade system (1.34).
After a laboriously tracking down the problem, I found reason the 1.27-test system was working was because caching was different.
Setting
$wgexLingoCacheType = CACHE_NONE;
and using the following diff againstsrc/Cache/ElementsCacheBuilder.php
led to it working in the production 1.27 system:(I think 1.34 will work, too, but I'm rebuilding data at the moment... will check back when it completes.)
I ended up using the above diff because I noticed the weird
if ( $page ...
above. I tracked down thestatic
to the refactoring that removed SemanticGlossaryBackend. I'm not confident that my work is correct, but at least it allows the glossary to work when Lingo caching is turned off.The text was updated successfully, but these errors were encountered: