Page history: old look in BlueSpice 4.5.4?

Describe the issue / Steps to reproduce:
In the latest BlueSpice 4.5.4 (free version) the page history looks like it did in BlueSpice 3.

Expected behavior:
There should be a new look from version 4.4.

Is there a configuration setting I could change?

Hello Bachti,
does the page history look like a table/ a grid, or does it look like a bullet list? A screenshot could be helpful = )

edit:
the history layout bundled in BlueSpice Free 4.5.4 should be a basic one. To evaluate an advanced layout you can manually install Extension:EnhancedStandardUIs - MediaWiki, after which you should additionally define in your LocalSettings.php:

$GLOBALS['wgEnhancedUIsVersionHistoryToolbarOffset'] = 153;
$GLOBALS['wgEnhancedUIsAllPagesPaginatorOffset'] = 64;
$GLOBALS['wgEnhancedUIsAllPagesOverride'] = true;
$GLOBALS['wgEnhancedUIsFilelistOverride'] = true;
$GLOBALS['wgEnhancedUIsExtendedFilelistOverride'] = true;
$GLOBALS['wgEnhancedUIsSpecialSpecialPagesOverride'] = true;

Hello!
It looks like the bullet list I have known from Bluespice 3 (as shown for example in

) and not at all like it is shown for Bluespice4 in

Hello again,
the documented interface took reference from BlueSpice Pro, where this advanced feature is not bundled inside BlueSpice Free 4.5.4. Still it is possible to evaluate the interface by manually installing the extension using its open source code, as mentioned above = )

Thank you!
I will possibly try this in the future when other things are solved.
I personally don’t like that “no support for free version” means not telling what is actually bundled with the free version and what is not. Did I miss something?

Hi,

changes and differences of different versions (free, pro, farm) are always mentioned in https://en.wiki.bluespice.com/wiki/Setup:Release_Notes, though in this case there is actually a mismatch:
Most of the features of EnhancedStandardUIs are mentioned as part of the free bundle in the documentation, but in the published code the extension is missing.

Thanks for your feedback that helped to reveal this issue! Let me consult my colleagues and see how we can correct this in the near future.