Klenkes

@MarcC Got by any chance the module EMO EmailObfuscation installed? I once had the same problem and it was EMO.

You could always add your own stylesheet in /site/init.php like this: $this->addHookAfter('ProcessController::execute', function (HookEvent $event) { $this->config->styles->append("/site/templates/css/adminstyles.css"); });

@FireWire I had to logout and login again. Then all fields were visible in the module config. At first the Language Associations fieldset wasn't there, and Fluency Options. Now it works as expected!

@FireWireSorry, but the DEV Version doesn't work at all for me... After the upgrade I went to the modules settings page and configured everything. After I hit save the following error message appeared: There are no translation buttons in page edit shown. No other error messages. The fields for the default language like in previous versions is missing? Mhh...

@FireWire In my case it was a new install with Fluency 1.0.9. No module update!

@markus-th You are correct! A downgrade to 1.0.8 works!

Hey @FireWire Probably a great module...? I finally had the time to explore your module but I keep running into the same Deepl API errors and I don't know where to look for a solution or what to do next. This is PW 3.0.229 on PHP 8.2 Fluency 1.0.9 on a pretty basic PW testsite. Deepl API key shows as valid and active and in my Deepl account it says: Access to DeepL REST API When I click on translate the following happens: The error log shows: Engine: DeepLEngine /Error: BAD_REQUEST /Message: Invalid request: Expected 'text' parameter to be an array of strings /Response: {"message":"Invalid request: Expected 'text' parameter to be an array of strings"} The TRANSLATION modal shows only the word undefined in the target language. It's just a testsite, so no rush. I would be greatful for any advice.

Thanks for the extensive explanation. That explains a lot. After a little bit of thinking I remembered(again) that in PW everything is a page. My own small admin module fixed it.

Thanks, but I'm pretty sure there is some hook that goes into admin.php that does the job. If not... the client probably won't pay for anything more time consuming ?

My clients website has a lot of categories and subcategories and editors mainly use ADD NEW. The sort order of categories there don't represent the sort order of the page tree (sometimes) and editors are complaining... (it's a looong list) The first item is Balken -> Nadelholzbalken, but there are a few item more. They are way down at the bottom. I couldn't figure out the existing sort order. It's not by ID. There has to be a way to hook into this function and change sorting somehow?

@Marco Link Sent you a message.

Hi @CraigThank you very much! Seems to work fine now.

Hi @Craig On PHP 8.1 and 8.2 the module throws a fatal error (at least with 3 different hosters) after install: In short: Fatal Error: Uncaught Error: Non-static method WayFathomAnalytics::getEmbedConfig() cannot be called statically in /site/modules/WayFathomAnalytics/WayFathomAnalytics.module.php:76 EDIT: removing static from the function seems to work (line 61 in WayFathomAnalytics.module.php) But I don't know enough about PHP functions ...

@bernhard RPB seems to need at least PW 3.0.232 when the Version Module was introduced. I updated to RPB 5.4.0 and it now runs without errors.

@bernhard, sorry but after the update to RPB 5.4.0 the site is broken... I had to revert back. A missing dependancy? PW 3.0.226 | RMig 3.35.5 | RockFrontend 3.11 | PHP 8.2

Hello @bernhard Since yesterday I am unable to login to download the latest release. Endless loading... (different browsers)

I like it too. Helps to unclutter the backend.

Yeah! It works! In my case there were 6 RPB fields on one page in the backend. I'm sorry I couldn't be of much help in finding the culprit...

Hi @bernhard Sorry, but commenting out these functions had no effect... ? (I did a module refresh and cleared compiled files, just to be sure)

RockFrontend loads uikit.theme.less and default.less in /site/templates/_init.php via $rockfrontend->styles() Probably from installing the UiKit profile? I commented it all out and now it's fine. Took me long enough... sometimes you just have to wait a day or two and have a nice cup of tea(like the British do) ?

@bernhard Any news on this? Funny thing... on a new project it only happens when a block is opened(uncollapsed) and then you do a reload. If you don't open a block the javascript message isn't shown, and everything is okay.

Sorry to UNSOLVE this... but for me it doesn't work at all. When adding a new block in the frontend and the modal is closed immediately an orphaned block exists. No saving in the backend resolves this. Am I missing something? PW 3.0.229 RPB 5.2.0

Other than in another website, in this one uikit.css ist always included in main.css, and it screws up my own css. Especially headings and it's anoying... I couldn't find where it is included, I certainly didn't do it. Is this an action of RockFrontend or RPB? PW 3.0.29 RF 3.11.0 RPB 5.2.0 PHP 8.2

Exactly. It has nothing to do with hideTitle, it's removing the title field from a block. With RM 3.35.5 the error is shown.

Send to your office@