Recent Posts

21

General Help & Support / Re: Make /admin forbidden for one particular user (user_id ==2)

« Last post by crnogorac081 on September 18, 2025, 10:40:59 PM »

Can you be more specific ? You want them not to be able to log in to /admin/preferences/index.php ? Put your code there

22

General Help & Support / Make /admin forbidden for one particular user (user_id ==2)

« Last post by CodeALot on September 18, 2025, 07:42:04 PM »

A new little problem:

I have a website that is not accessible without logging in first. Nothing top-secret, but there's only one group of people that are allowed to see the website.
I made a user ("visitor") that has access. Works fine.

Problem: I do NOT want them to be able to access /admin. There's nothing there for them, they are not allowed to change the profile (since many people use that login). All login-stuff is handled on the front-end.
I tried stuff with

Code: [Select]

if ($_SESSION['USER_ID'] == 2) {  header('Location: https://www.homepage.nl'); exit; }
in several places but it doesn't work...

I do not have a fixed IP for myself, and to make things more complicated: there ARE more users (ID 3, 4, 5) who DO need access to /admin. So the only user that needs to be kicked out of /admin is user_id 2

Any idea where I should look or how I should handle this?

---------------------

Ein neues kleines Problem:

Ich habe eine Website, auf die man nur zugreifen kann, wenn man sich vorher einloggt. Es handelt sich um nichts Geheimhaltungsbedür ftiges, aber es gibt nur eine Gruppe von Personen, die die Website sehen dürfen.
Ich habe einen Benutzer („Besucher”) angelegt, der Zugriff hat. Das funktioniert gut.

Problem: Ich möchte NICHT, dass diese Benutzer auf /admin zugreifen können. Dort gibt es nichts für sie, sie dürfen das Profil nicht ändern (da viele Personen diesen Login verwenden). Alle Login-Angelegenheiten werden im Frontend abgewickelt.
Ich habe an mehreren Stellen Folgendes ausprobiert:

Code: [Select]

if ($_SESSION[‚USER_ID‘] == 2) {  header(‚Location: https://www.homepage.nl‘); exit; }
an mehreren Stellen ausprobiert, aber es funktioniert nicht...

Ich habe keine feste IP-Adresse für mich selbst, und um die Sache noch komplizierter zu machen: Es gibt weitere Benutzer (ID 3, 4, 5), die Zugriff auf /admin benötigen. Der einzige Benutzer, der aus /admin ausgeschlossen werden muss, ist also user_id 2.

Haben Sie eine Idee, wo ich suchen sollte oder wie ich damit umgehen sollte?

23

Modules / Re: WBLINK for modules

« Last 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

24

Modules / Re: WBLINK for modules

« Last 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.

25

Modules / Re: WBLINK for modules

« Last 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!

26

Modules / Re: WBLINK for modules

« Last 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.

27

Modules / Re: WBLINK for modules

« Last 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.

28

Modules / Re: WBLINK for modules

« Last 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.

29

Modules / WBLINK for modules

« Last 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)

30

General Help & Support / Re: Feature Request: Hide pages in the backend

« Last post by CodeALot on September 18, 2025, 10:29:02 AM »

So, in principle, it's not a problem, but if you need a solution that's ready tomorrow, then that's not possible. However, it might be possible for the next WB version, technically speaking.

No not at all, it's not something for 'tomorrow'. But it would sure be nice if that will be an option in future versions!