marclaporte: Telesight: should be, if 18n.tiki.org is up to date
Lauwenmark: well some things can be fixed fast. If it's a surgical change, you can modify your instance, and the real change can be in 12.0 and 11.1 Lauwenmark: marclaporte: I found the single line to change so the 11 can work :)
marclaporte: in absolute_urls.php, the variable $url_host is the one I needed to redefine. dhazel: joined #tikiwiki fabricius: Lauwenmark: re ... nice to hear, you found a solution ... would you mind, to document that on do.tiki.org? :-)
sry doc.tiki.org Lauwenmark: fabricius: Sure, but I'd suggest making this an optionally settable variable from one of the administrative panels.
(there are several cases where autodetection is not desirable and better being user-defined instead) Tiki|bot: joined #tikiwiki Tiki-KGB: 03nkoth r47339 03trunk/lib/core/Math/Formula/Function/Random.php * [NEW] Random function for rating language chibaguy: joined #tikiwiki Tiki-KGB: 03nkoth r47340 10trunk/lib/core/Search/GlobalSource/SocialSource.php
[FIX] Followers need to be array_merge as is numeric keys to avoid disappearing items chibaguy: joined #tikiwiki laurei: joined #tikiwiki chibaguy: joined #tikiwiki rug: joined #tikiwiki
hello, anyone experienced to help me configure my tiki wiki? fabricius: experienced might be some of us :-)
hi rug
what's the problem? rug: ok i am new to the tiki
I want to create menus
I have created menus, assigned to a module, but can't display PrezKennedy: joined #tikiwiki redflo: joined #tikiwiki rug: hello
anyone to help? fabricius: sure rug
lets start easy rug: ok thx fabricius: you want to display a menu on your Tiki website rug: yes fabricius: you created a menu
Id=? rug: yup fabricius: 43? rug: yes
its 46 fabricius: ok, so it is the first menu you create in this brandnew Tiki instance (cause the first menu is the main application menu Id=42 .. active by default)
ah so you have setup a few before rug: yes fabricius: 43, 44, 45 and now 46 rug: but all dont appear fabricius: ah ok
sure, when you create a menu, it never appears - ist just exists rug: sure fabricius: which is logical and good so, after you understood a few basics about Tiki rug: ok, this means there is a syntax i am missing fabricius: mainly .. you can use the same menu multiple times
so you need to deside, where the menu Id=46 should appear rug: so in tiki, the about,home,..... how are they called and how to setthem up? fabricius: about, home? what you mean?
you mean a standart navigation menu? rug: i mean the ordinary so called menus
sure
yes fabricius: lets keep it simple - Tiki does not mind, for which purpose you use a menu - on a wikipage, as main navigation horizontal or vertical or as secondary menu or in a footer
where you want to display the menu Id=46? rug: Basically, I want to create different menus for multiple departments of my company. There will be authentication requirement to each member to access his/her dptment data. fabricius: a) which module zone (footer, header, left or right column, ...)?
b) horizontal or vertical menu? rug: i'd like horizontal fabricius: ok
I guess you want the "top bar" zone between the header and the columns rug: exactly fabricius: that is the typical zone for horizontal main navigation
cool
did you do a lot of trial error configuration yet in this instance, or is it mainly like freh installed?
fresh rug: 46 NOC NOC Department d 0 Edit Configure/Options Delete Clone this menu and its options 43 IT Department d 1 Edit Configure/Options Delete Clone this menu and its options 44 IDC IDC Department d 0 Edit Configure/Options Delete Clone this menu and its options 45 FOC FOC DPtment d 0 Edit Configure/Options Delete Clone this menu and its options 42 Application menu Main extensive navigation menu d 192 RESET Clone fabricius: normally the module zones (see: tiki-admin.php?page=look) are set to be "only visible if module" .. which is fine for us
We do not need the list for now rug: I created just as a brief of what I did fabricius: you need to go there: /tiki-admin_modules.php rug: i created modules also fabricius: ok
no custom modules?
you do not need custom modules for navigation menus
only for very advanced setups rug: it is a custom module fabricius: arrgl
no problem rug: ok can i delete that custom module? fabricius: so you did setup a custom module and wonder, why it does not appear?
just leave it like it is ... you might use it later or change it later .. just ignore it for now rug: or, can I delete everything I did and start from scratch in order to ease your help? fabricius: to display a module you need to apply it to a module zone
no ... nothing necessary to ease my help
maybe a minute to get another coffee and have a fag on the balcony :-)
so are you in tiki-admin_modules? rug: yes i am fabricius: three tabs, you see it?
use the left tab - click on it
then find a button to apply a new module rug: i can see 4
add new module? fabricius: yes! rug: ok fabricius: click on the button rug: yup fabricius: you find a drop down and there you can chosse aswell all preset modules as your custom modules rug: module name, there is a dropdown to choose from fabricius: we use a preset module
the module "menu" obviously
preset modules have advantages above custom modules, as you have preset parameters and fields to type in your values
for custom modules you have to find out your self and type in manually
so we use the preset one
the viewport must change and you have a four-tab dialogue for configuring the module
tell me when you are there or if you do not find it rug: ok fabricius: ah good
main necessary settings now:
1st tab:
drop down "topbar" instead of "top" (top=header)
2nd tab:
menu Id = 46 rug: ok
there is nowhere i can put the id
only position,order,cache time and groups redflo: joined #tikiwiki fabricius: that is tab 1 rug: sure fabricius: position: topbar rug: yup fabricius: rest is ok rug: yup fabricius: groups obviously refers to the group which can see the module
tab 2
now rug: ok fabricius: menu Id - you see the field
structure Id stays empty ... this is for "magic menus" for later on (adfvanced use with wiki structures)
-f
type = vert is default anyway, but you can set the value if you want rug: ok I can see Menu not Menu Id fabricius: ok, use that .... things evolve over times
the rest you keep empty
but for your interest: here you could define css selectors for the menu (#id for the #dom, ... etc. rug: ok, fabricius: you need the 3rd tab now
here you configure the way how the module is displayed
and optionally aplly a css selector to the menu
nesessary for a typical topbar main navigation: nobox=y rug: so, I have to find a menu Id i created and fill it. right? fabricius: you do not want a module title and decoration on top of the menu
that was already in the previous (2nd) tab ... just use the Id 46 rug: ok fabricius: then in 3dr tab prameter=nobox / value=y
3rd I mean rug: yup fabricius: everything else keep empty (meaning default)
4th tab now
no setting at this moment, but look at it to know it
here in the 4th tab you can configure, in which context the module should be visible
like depending on a perspective or a category or only when a certain page(s) is active or a theme or a feature (section like blog, forum, etc.)
for your usecase we could consider to use perspectives, but that is too advanced for the first day ... we look at this another day ;-) rug: ok fabricius: so you can save the module and it should appear
ls confirm
pl confirm rug: ok fabricius: arrgl -> pls <- rug: ok fabricius: ok means "visible"? rug: sorry Im going out for 10 mins fabricius: so I get a fag :-) -: fabricius smoking rug: I am back
sorry for it
Are u still there Sir?
Hello fabricius fabricius: ah rehi
just did some work ... yes still here and you? rug: yes i am fabricius: ok rug: i see fabricius: you have so far 4 menus for 4 workgroups, if I see it right!? rug: right fabricius: do you have any experience in user-permission management aka role-permission model? rug: yes I have fabricius: cool
for workgroups the perspectives feature can be interesting, but we leave that for later - as said
each menu need to be visible for a certain workgroup
I imagine, that there might be people which are member in more than one group
so Tiki must know, when to display which menu (module) rug: sure fabricius: and prevent to display four horizontal menus at the same time, if one user is member of all foru workgroups
so you need to setup an identifier for the Tiki objects (wikipages, articles, forums, etc.) to allocate them to a workgroup
an an identifier to allocate the users to a workgroup (or several)
you can imagine, that the identifier for users are the ... groups
and for the objects they are the ... categories
in Tiki you can use categories for different purposes
mainly identifying and group objects and secondly to apply permissions for groups of users in groups of objects (categories)
I recommend to mainly use category permissions and to avoid general permissions and object permissions (use them only in really necessary situations)
you can create several trees of categories
use one tree for permissions only and another for navigation only .... you must find out a good way of organising this for your project
as you have experience with this, you know, that this is one of the main time eating tasks rug: that's ok fabricius: for your question now, we just need 4 categories and four sample wikipages
the sample wikipages might represent "landingpages" for the workgroups
the 4 categories represent the identifier for the workgroup related content
as the admin can see everything, you can setup the 4 usergroups lateron rug: ok fabricius: step 1: create categories
ahh step 0: activate the categories feature in /tiki-admin.php?page=features
then step 1 ;-) rug: yeah fabricius: /tiki-admin_categories.php rug: the cat link was missing fabricius: yeah - it is missing, when inactive -: fabricius is back in a minute rug: ok fabricius: rehi
did you setup the 4 catgories or you need help with it? rug: oh! Im very sorry i am unable to continue. there is an urgent case i need to solve
thank you and i wish i cud meet you here for further help fabricius: so either come back another day or write to the devlist or the forum or write me an IM in the community page tiki.org - you might register there
my username there is "Torsten"
community website I mean
https://tiki.org/Community Jenser: joined #tikiwiki mlaporte: joined #tikiwiki
laurei: did you figure out how to embed Tiki content yet? laurei: hi mlaporte still no, i had a play with views but couldn't really understand mlaporte: laurei: You could use the print mode or the raw mode laurei: raw sounds nice
what's that?
mlaporte mlaporte: https://themes.tiki.org/tiki-index.php?page=Template%20Tricks&pagenum=3#show_the_content_without_columns
That page has a lot of goodies
There is also a raw mode which doesn't interpret wiki syntax but that won't help you
So for any wiki page, you should be able to get the page without top/left/right/bottom modules Jyhem_laptop_: joined #tikiwiki mlaporte: Things to check: if you click a link in the page, does it maintain the look? (without modules)
laurei: I am supposing here there is no concern with login / perms?
It's sort of like an iframe? laurei: mlaporte I am using pretty intense role based access control
iframe would be fine mlaporte: So how do you share auth between systems? Telesight: joined #tikiwiki mlaporte: Telesight: are you OK for translations or still blocked? laurei: mlaporte ldap, if the user needs to sign in in a few different places it's ok as long as the passwords are synced mlaporte: laurei: so from other system, you embed Tiki pages (without borders) but if page is protected, it should be a login box? laurei: that would be fine mlaporte until i figure out session sharing, etc mlaporte: laurei: ok, and there is a way to sync groups too laurei: tikiwiki has nice ldap group syncing mlaporte, i just create a permissions group for every ldap group mlaporte: session sharing could be done with CAS (which is configurable within Tiki, but you need to set up CAS Server) laurei: mlaporte: is cas just a session thing or is it a complete replacement for ldap plugin mlaporte: not replacement, but to manage sessions laurei: mlaporte so i can manage sessions based on the ldap users, that would be ideal mlaporte: Do you have a lot of users? laurei: mlaporte around 50
but even if it was 3, that user experience is worth weeks of messing around :) mlaporte: hehe laurei: i see your name around alot mlaporte what do you do @tiki mlaporte: http://doc.tiki.org/tiki-index_p.php?page=Tiki12 makes a nice page, but links in them go to normal pages, so you could try with Short URLs off (Maybe Short URLs is conflicting with keeping the tiki-index_p...)
I discovered Tiki in 2002 while building online communities and found it really awesome and I thought "If only it could also do XYZ as well"
11 years later, I am still thinking that :-) laurei: I had a look at the codebase once, it scared me to see so many files
but i can't find anything that is as flexible mlaporte: I think we now have the best development model in the World (well, for a vastly-featured web app)
I have analyzed many and got inspiration from them laurei: mlaporte: I'd love to see a nice template built on bootstrap.js if i can get my snippets working i might do that next mlaporte: Codebase is huge, somewhat messy and has 3 different generations of code in it, including some PHP4 stuff
Bootstrap is going to be awesome! And a good example of how Tiki has best development model
With any other web app, they have to sacrifice tons of extensions when they make a (necessary or desirable) enhancement to the infrastructure
In Tiki, because we a have a unified code base and data structure, we can make it all evolve without sacrificing part of the commmunity laurei: "...and how much would you expect to pay for all this.." :) mlaporte: And with Long Term Support (LTS) versions, site admins can upgrade at their own pace. There is a proposal currently on the table to extend support period to 5 years (instead of 3.5 years now, and 2 years we had for the 1st LTS version) starting with Tiki12 laurei: mlaporte: I guess it would depend on the figures of people sticking with old versions, i personally upgrade whenever i can mlaporte: There is a split in the community, which can even lead to tensions because of these conflicting objectives
Most of the site admins prefer LTS and don't want to upgrade. Tiki does all they need, which is why the picked it.
But most of the people committing code is to get enhancements and the new versions
laurei: you said you can't find anything as flexible. What did you compare it to? laurei: mlaporte I spent a few hours on wikimatrix, all of them, I really need RBAC, and SVG, i think i chose twiki and tikiwiki
perl ain't my thing mlaporte: Ah, how those two names are close :-)
How "iki" makes all the difference :-)
There is also an ikiwiki (!) laurei: haha, i would have chosen twiki because they claim fortune 500 companies bla bla, i think i even installed it but I wasn't going to be able to code anything for it mlaporte: http://en.m.wikipedia.org/wiki/Ikiwiki
hmmmm, do you think we should add some fortune 500 companies on info.tiki.org ? laurei: yes mlaporte it would make me more comfortable lol fabricius: hehe - which of them use Toki?
errr Tiki
sry laurei: theres a toki?
oh mlaporte: hahahah laurei: sounds japanese tokiwoki fabricius: oh noooo - there is a typo
hehe laurei: does tikiwiki use a vcs for storage, i like the idea of that fabricius: vice city story?
hhe version control system
version control in sence of history?
yes for wikipages, yes for sheets laurei: in the sense of using git or svn
its not a big deal i don't know how i'd use it like that, but i do like using standards fabricius: version control in sence of new version of files and archive old versions?
yes for file galleries
version control system in sence of downloadable source code (development)?
yes for Tiki source code => sourceforge => svn
I run myprojects via svn laurei: i mean the documents themselves fabricius: minor upgeades: shell ... svn up ... tiki-installer + upgrade database ... mostly finished in a few minutes
so files
file gallery
you upload a file into the file gallery -> either in the database, or in a folder in the document root of Tiki or strongly recommended outside the document root of Tiki
then you can upload a new version of the file, if necessary and still have the old version archived
or several old versions
but this is not via git or svn ... its Tiki internal mlaporte: When I started out, TWiki was, by far, the best wiki out there. It's the first Enterprise wiki. I considered very seriously using that. However, I felt that 1- PHP was better suited for this and more accessible 2- Storing in a DB was much much better than storing in the file system 3- Tiki's other features (blog, forums, etc.) were needed for community management and if they were not bundled, I would waste a lot of time picking stuff, ma laurei: have any of you guys used sharepoint or whatever they are calling it, how do they compare fabricius: by the way: storage in the database and storage in directory documentroot/files is only to make it working from default installation
it is strongly recommended to create a directory outside the document root of Tiki and use a path like this: ../files/gallery instead of /files, which would be inside the document root
I never used sharepoint, but I think I have to look at it, as Tiki might become a competitor after getting some missing stuff wrapped up
mlaporte: are you still thinking, that storing in the db would be batter than storing in the file system? ... I have bad experience with database, cause database grows extremely with file storage (just one point) arildb: joined #tikiwiki fabricius: long ago I did read about the recommended directory storage (outside root) and since I only do that from conviction
... I do that only ... err ... I do only store in the file system cause I am convinced .... shame, English still is a foreign language for me mlaporte: fabricius: what laurei means is to be able to edit a wiki page via Git or SVN like http://www.wikimatrix.org/show/Git-Wiki fabricius: ah - he referred to documents ... I have a look
humm would we need that? I mean we have "history" for the pages and we can compare versions and everything laurei: I have no idea fabricius it just "sounds" good :)
i guess using standards is always good mlaporte: Torsten: file system for binary files is OK. But in TWiki and DokuWiki, all the data (pages, users, page metadata, etc.) are stored as text files. For this, I much prefer a real database laurei: but i can't think of a use case except for backing up because you still have permissions, git doesn't handle that well fabricius: mlaporte: I agree
I do not think, that we would need to be able to edit wiki pages via git or svn
why involve a third party, if we have a very stable core feture for it integrated deeply in our software? ricks99: joined #tikiwiki fabricius: feature
hate these typos, but cannot really avoid them
hi ricks99 ricks99: polom fabricius fabricius: moloq laurei: actually fabricius mlaporte I just remembered why it would be good, you just don't worry about how you store the data, just simply put in the creds and transfer the data to the git system which stores it ricks99: :-) fabricius: hmm ... I do not worry about how to store the data anyway ...
I 'click edit or create' - 'edit' - 'save'
stored in the database including history and permissions and all
why worrying?
I mean, if you start coding a wiki from scratch, you could use git-wiki for versioning alright
I do not see the point for Tiki, even the idea of git-wiki might be quite cool in itself ... a nice use for git mlaporte: https://dev.tiki.org/File+Gallery+Revamp is coming so any features you see in SharePoint or Alfresco, just add
http://www.fossil-scm.org/ is an intriguing distributed SCM. I could envisage using this with Tiki for synching of profiles and perhaps to make Tiki distributed laurei: whats the difference between fossil and git chibaguy: joined #tikiwiki pianoliv: joined #tikiwiki
joined #tikiwiki nkoth|nelson: joined #tikiwiki rodrigoprimo: joined #tikiwiki Tiki-KGB: 03arildb r47341 10trunk/lib/core/TikiDb.php * [FIX] Better detection of MySQL SSL usage dhazel: joined #tikiwiki Tiki|bot: New Forum Posts: PHP Storm - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48924 marclaporte: joined #tikiwiki fabricius: joined #tikiwiki Lauwenmark: joined #tikiwiki Tiki-KGB: 03jonnybradley r47342 10trunk/styles/utopias.css
[FIX] css: Fix an arbitrary minimum page height - looked bad with really short pages (possibly should go in design.css if we want it in all themes?) aalex_: joined #tikiwiki xavi: joined #tikiwiki
polom
who is in charge of the domains *.tiki.org? only marc? maybe changi ?
Jyhem , any clue, since you were involved in the show.t.o recent domain, I guess?
bbl Jyhem: xavi: Marc is, but probably not only Marc.
Maybe even me, but I'm in a huge emergency
Gotta get spiral back up Drawenmark: left #tikiwiki Tiki|bot: New Forum Posts: Admin role for translation + "Status" - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48930 xavi: ok, Jyhem, no worries, thanks for the info.
good luck with spiral!
time to leave for me. cheers
left #tikiwiki Tiki|bot: New Forum Posts: Bad layering for edit page Help window - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48931
New Forum Posts: jQuery.sheet 3.1 RC3 - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48933 changi: joined #tikiwiki laurei: joined #tikiwiki Tiki|bot: Recent Bug: - Permissions for perspectives are not working - http://dev.tiki.org/item4720