WebsiteBaker Community Forum

WebsiteBaker Support (2.13.x) => Modules => Topic started by: CodeALot on September 18, 2025, 10:34:04 AM

Title: WBLINK for modules
Post by: CodeALot on September 18, 2025, 10:34:04 AM
It's an old problem, I have asked about this before, but the solution that used to work is not 'valid' anymore.

Problem: When linking using a WBLINK, the drop-down only shows pages. It will not show entries (detail-pages) of OneForAll-modules, for instance.

This used to be fixable by editing /ckeditor/ckeditor/plugins/wblink/pages.php but it seems that file has been completely rewritten.

Is there a new way to fix it?

-------------------
Es handelt sich um ein altes Problem, ich habe bereits zuvor danach gefragt, aber die Lösung, die früher funktioniert hat, ist nicht mehr „gültig”.

Problem: Bei der Verknüpfung mit einem WBLINK werden im Dropdown-Menü nur Seiten angezeigt. Einträge (Detailseiten) von OneForAll-Modulen werden beispielsweise nicht angezeigt.

Früher konnte dies durch Bearbeiten der Datei /ckeditor/ckeditor/plugins/wblink/pages.php behoben werden, aber diese Datei scheint komplett neu geschrieben worden zu sein.

Gibt es eine neue Möglichkeit, das Problem zu beheben?

Übersetzt mit DeepL.com (kostenlose Version) Don't shoot the messenger)
Title: Re: WBLINK for modules
Post by: dbs on September 18, 2025, 10:44:21 AM
I thought that was controlled in the WbLink.php file in the module folder.
But that didn't work for me at all.
Title: Re: WBLINK for modules
Post by: sternchen8875 on September 18, 2025, 11:36:24 AM
We talk about something like this in the Ckeditor-Wblink-Plugin?

Before WB introduced the WbLink file, this was indeed done by adjusting the pages.php file, but that was probably 7 or 8 years ago, maybe even longer.
Since CKEditor is a third-party product, except for a very few custom plugins, you don't necessarily have any influence over what you get from it.

Today, this is done by the WbLink.php file, which is included with the News module, for example. I have similar files in 5 other modules that were created on behalf of clients. It has to be customized for each module. There's also a similar file for OFA, which was created years ago. I don't know if it still works today; I'm not an OFA user. I'm using the module somewhere, but without subpages, so I'd have to create a test environment first.

(https://i.gyazo.com/01fd2b2d898409baaca14ee0714ee1f5.png)
Title: Re: WBLINK for modules
Post by: dbs on September 18, 2025, 12:18:22 PM
As I have just discovered, WbLink.php works exactly as it should. It works.

Uwe has created a small zip file with the file and instructions. It only takes a few seconds.
Title: Re: WBLINK for modules
Post by: CodeALot on September 18, 2025, 12:28:58 PM
As I have just discovered, WbLink.php works exactly as it should. It works.

Uwe has created a small zip file with the file and instructions. It only takes a few seconds.

Diving into that right now. Thank you!
Title: Re: WBLINK for modules
Post by: CodeALot on September 18, 2025, 12:31:12 PM
Before WB introduced the WbLink file, this was indeed done by adjusting the pages.php file, but that was probably 7 or 8 years ago, maybe even longer.

Yeah, I know. Proudly building WB websites for over 16 years. :-)
Title: Re: WBLINK for modules
Post by: sternchen8875 on September 18, 2025, 12:33:20 PM
one word more....

this works with or without one sub-pages for OFA

if you dont use subpages ($view_detail_pages = false; in config.php of OFA), leave this entry here as it is

const ACCESSFILES_SUBDIR   = 'oneforall';

If the ckeditor is open on your backend, when you change the WbLink.php, you've to close the Editor-session. Simple way: go to another page like WB-Options etc, and the back to the Editor-Page, to reload the new settings