Recent content by Sooty57

seem to be several of us having problems with this automatic upgrade failing :(

Same problem here. I cannot find any reference to the part of custom_functions.php in up.php, up2.php or the upgrade section of docs.htm. Went back to support for clarification but, so far, no response.

Just received the following message from ISP Tech Support: I don't feel so silly now 😆

I had cleared browser cache (chrome) without success. Tried using Safari, and all ok. Boy, do I feel silly 🤭

My hosted server PHP version was updated from v7.4 to 8.2, and I can no longer log in to dadbik. The error log shows: It seems that the script is still looking for session dat in the old path. As the common_start.php file is understandably encrypted I do not see how I can resolve this without...

Not sure what caused this, but the guys at Dadabik seem to have sorted it out now :)

I notice that the warning does not display the date that the licence supposedly expired (see attached)

Your current DaDaBIK version You are using DaDaBIK version 11.9-Elba monthly, installed on Apr 3, 2023 (installation code: 1866763ed0809c9e54), the latest version of DaDaBIK is 11.9-Elba released on Mar 23, 2023 System info PHP Version: 7.4.33. mysql version: 5.5.5-10.3.38-MariaDB. Web...

That works :)(y)

Looking again, I agree with Martin68 - i.e. all fields shifted up from labels.

dadabik.com/dadahelpdesk_demo/index.php?tablename=requests&function=edit&where_field=id_request&where_value=7939 The problem appears to be with select single fields only. Safari 16.3

Would it be possible to use a hook to prevent login button or full header if user = public?

Can I ask how you achieved item 5 please. I have the same problem.

I have managed to successfully create publicly visible pages, but how can I prevent the header and login button from displaying? I don't want my public users to ever get to the login screen.

Same issues here when using Safari on Mac - I switch to Chrome when using DaDaBIK