adamkolenda

Thanks,

Tried the first part already and it seems that this did not resulted in any improvement which would suggest the latter. I had an infrastructure engineer looking specifically at the Apache config to see whether there is anything which would interfere with this plugin but they have not called out anything specifically.

Any idea what on server configuration side could be an issue?

Thanks

Thanks, but is there any way I can verify whether it is clash with other software or simply a bug within a plugin?

Thanks Bcworkz, that has been done already. we cleared the environment including customizations on PHP and apache, downloaded fresh WordPress package and the issues with Gutenberg Blocks still happen.

As advised in the original post this is definitely something with the infra, however not really sure how to investigate it further.

Are there any tools which could help to debug this issues or at least help to find the cause of the issue?

Thanks

Hi,

I’ve thought of the same, however to eliminate potential plugin/theme clashes I have installed brand new blank WordPress instance – no plugins or customised themes but on the same environment and face Gutenberg block issues but only with “Advanced” tab.

Thanks

Hi Andres,

I hope that you are feeling better now?
I wonder if potentially you will have time to look into this problem in more detail some time this week?

Thanks!

Thanks for your prompt response Andreas,

This is much appreciated and understandable. Hope you get better soon!

The things is that the AD Administrators have been involved from the beginning and while they able to provide required parameters individually (things work when integrated using another plugin but the plugin is not as versatile as yours and does not support roles mapping), and the problems seems to appear when the URI is being put together as so far we have not managed to get it working even with it simplest functionality and error message suggest we are not even able to connect to the AD server.
I’m therefore pretty sure that the problem is in the URI sting and we have tried various combinations without a luck.

Anyway I will work with AD team in the meantime to try to crack it, but if no luck I will await until the 6th for your further guideline.

Many thanks in advance!