joined #tikiwiki
Hi there!
I have one question: We want to use LDAP Authentication in our Tiki, but our Sys-Admin needs to know first: Is Tiki altering the LDAP in any way? Does it change Users/Roles/Groups or such things? We want a Read-only integration of Tiki!
Hi pbiendl - that is configurable in Tiki and by default it does not change anything.
There are options like "Create user/group in directory, if it does not exist", that's all iirc.
Ah ok, just wanted to mention that option :) So this is the only thing that needs to stay deactivated?
In LDAP external Groups there is some sort "Sync Tiki Groups with a directory", is this read-only too?
What we want to do is: Use the LDAP Groups inside the Tiki (and of course the Users) and set the Permission on the LDAP Groups (but only the imported LDAP Groups). It's important that Tiki doesnt alter our LDAP in any way
With Permission i mean the ACL of Tiki
With LDAP Sync you mean just the Group Sync or also the User Sync?
I know the problem with Spambots... i'm a developer by myself, so i understand this step :)
Just to clarify (just in case i got something wrong): The "LDAP" Tab is for User-Authentication only and the "LDAP External Groups" is for the LDAP Groups, right? If yes, is there a reason to seperate these two? Whats the disadvantage if i only use the User Authentication without groups?
I mean, i don't want to use LDAP External Goups if i don't have to :-) The only thing i want is that our Users are able to log in with their LDAP Account... (and of course i need to specify what they're allowed to access)
Yes, that's right. There's not really a disadvantage... you don't get LDAP Groups synchronized to Tiki. The seperation into two tabs was a developers choice back then, dunno, maybe it felt more sensible to her to seperate it because the group code was added later on.
If you only need to log in users with their LDAP credentials, then just forget about the group sync. The normal LDAP login works perfectly and you can add users to groups that are stored and managed inside Tiki in the classic way.
One last question: Is there a way to change the default Group in which new Users will be stored in?
By default it's the "Registered" Group, but i made a new Group
But if thats not working, i copy the Rights over to the Registered Group
Don't know, maybe i dont want to change the default Group-Set, so if something went wrong, i still can look into the registered Group to see whats default :)
Maybe there is a way to configure that, not sure right now... but Registered tells quite exactly what they are (logged in) and all the other groups then stack on top of that.
Ah, ok, that's good thinking.
how can I retrieve my credentials in https://dev.tiki.org/Development ? There is no register nor lost your password anywhere to be found..
Oh, sweet. When I clicked at a random page that needed to be logged in, it showed me a note that I should register at tiki.org.
msaad sight
yes, that is true - registrati on and usermanagement is centralized on tiki.org - the other community sites are Intertiki slaves/clients of the tiki.org master
how you have been to the idea that you could get credentials or update your credentials on dev.tiki.org - I mean there must be a misscommunication that we should fix and mention stuff like that on appropriate places
At least we could put a register / recover pw on the login box redirecting to there
So what happened was, I went straight to dev.tiki.org and tried to login. Couldn't figure out my credentials (was already registered). The login box didn't have an option to recover nor to register.
So I tried to view something that needed to be logged in, and from there I had a note telling me that I needed to be logged in and that it should be done at tiki.org
maybe a simple textfield which can include WikiSyntax might be enough (could be used for whatever else if needed)
or a text and a link
mind the css
an appropriate Bootstrap class and maybe an Id
anyway you could/should try locally first
and please msaad contact jonnyb first wether you commit to 14 and merge to 15 (=trunk) or commit to 15 and merge to 14 or commint to 15 only.
/s/commint/commit
I'm not sure what is the DIV plugin, but about wiki syntax it's hard to position items on specific places, or to have responsive font sizes without using em
so i tihnk the best things for the "i forgot" login issue on dev etc would be to make the login module clever enough to have the right link (e.g. to https://tiki.org/tiki-remind_password.php)
Right, moved it to WikiSyntax. What are your thoughts on the content so far jonnyb, gezza, fabricius, nelsonko (and all) ? Do you like how it's flowing, should I keep the informal tone, etc
My idea is to make it easier for newcomers to have access to must read articles / key information at this first page.
I don't want to pollute with information, but at the same time I'll be linking them to different articles as they see fit.
msaad: for cross tiki community site links you might want to use this syntax: ((doc:Documentation)) to link from dev and other communty sites to page "Documentation" on community site doc.tiki.org
next msaad: we started with a new tiki.org landing page replacing the odd redirect to info.tiki.org, which eventually will be mirated to tiki.org - and thus the work with the main pages will eventually influence the other commuity sites aswell
the PHP bit is a bit imncomplete - tiki's written in PHP, Smarty and JavaScript (and a hint of XML) - but maybe that confuses things...
but it is "mostly" php (55% according to https://www.openhub.net/p/tikiwiki)
chibaguy i did not get email, when did you send?
"To make the jumbotron full width, and without rounded corners, place it outside all .containers and instead add a .container within"
I think content should be worked out first, without thinking about layout. Anyway, that's the approach I like. I prefer a kind of outline or text-only page. Then apply a layout to that. No need to spend time on layout before the content is pretty solid IMO.
And what is the purpose of the layout? What is the flow through the page, that the viewer is expected to follow? The path, with main points, etc.?
This is one way to make a page coherently without dozens of edits to refine content and layout twisted together.
Anyway, see you tomorrow.
fabricius, the solution there is to rollback, isn't it?
True, it's a wiki so can be edited freely. But I prefer to discuss something that's text since the layout can be a distraction from text ideas. But just my opinion. Anyway it's late here so I'll be back online tomorrow.
gezza: I did NOT break, sorry for false alarm - someone activated autotoc as default, which then has been shown above the big logo including the links to the featured sites. did need a few minutes to figure that out and switched off the autotoc for the page