Some new information:
After some reboots the old portal is on all DC’s available, but not editable. Also not directly in LDAP. No Timeout, no Error. If i had a look in the logs:
Apr 05 11:47:07 dc1 univention-portal-server[6632]: INFO:univention.portal.css:Writing CSS file /var/www/univention/portal/portal.css
Apr 05 11:47:07 dc1 univention-portal-server[6632]: Writing CSS file /var/www/univention/portal/portal.css
Apr 05 11:47:07 dc1 univention-portal-server[6632]: INFO:univention.portal.css:No CSS code available
Apr 05 11:47:07 dc1 univention-portal-server[6632]: No CSS code available
Apr 05 11:47:07 dc1 univention-portal-server[6632]: INFO:univention.portal.css:Adding White Header
Apr 05 11:47:07 dc1 univention-portal-server[6632]: Adding White Header
Apr 05 11:47:07 dc1 univention-portal-server[6632]: INFO:univention.portal.css:Writing background image
Apr 05 11:47:07 dc1 univention-portal-server[6632]: Writing background image
I’am able to add a new portal in LDAP, this is accessable, but the same, not editable. I have tested this in an completly new fresh domain. And this this the same behavior.
Also the old portal on my Environment is only editable via plain ldap browser in umc, because the new faulty gui was not remove with the downgrade.
So if understand this right, new entries in my existing portal do not work because there are no reference to this portal. The reference can’t be made because the portal cannot be edited.
So how i can refer to an existing portal?
Workaround for me this time:
I’ve created a new portal with all my entries in LDAP. I also added 10 more empty entries. I have not activated these. So I don’t have to recreate the portal completely when I want to make changes. A change of the portal itself, background, color, name… is of course no longer possible.
At least you can work with it that way.