arildb__: joined #tikiwiki arildb_: joined #tikiwiki Tiki|bot: joined #tikiwiki arildb_: joined #tikiwiki fabricius: joined #tikiwiki arildb__: joined #tikiwiki Tiki|bot0: joined #tikiwiki Tiki|bot: joined #tikiwiki jallen: joined #tikiwiki goj_killedByISP: joined #tikiwiki jallen: Can someone tell me specifically how to add items to horizontal black bar area......menu bar Tiki|bot: joined #tikiwiki jallen: Can someone tell me specifically how to add items to horizontal black bar area......menu bar....anyone here Tiki|bot: joined #tikiwiki Tiki-KGB: tikiwiki 03kstingel r44261 04users/kstingel/PHPdocProj
tikiwiki [FIX] removed empty project folder Tiki|bot0: joined #tikiwiki goj_killedByISP: joined #tikiwiki arildb: joined #tikiwiki arildb_: joined #tikiwiki arildb__: joined #tikiwiki Tiki-KGB: tikiwiki 03kstingel r44262 03users/kstingel/PHPdocProj
tikiwiki [NEW] created private branch for PHPdoc commits kstingel: joined #tikiwiki
joined #tikiwiki fabricius: joined #tikiwiki arildb_: joined #tikiwiki fabricius: joined #tikiwiki arildb__: joined #tikiwiki gour: joined #tikiwiki kstingel1: joined #tikiwiki rinnan: joined #tikiwiki Jyhem_laptop: polom kstingel: joined #tikiwiki rinnan: polom kstingel: joined #tikiwiki
how do I make the background of content in pluginTabs white, but retain the coloured tabs and border? -: gour is very pleased with tiki's relocability features j0n3: joined #tikiwiki vmachine: joined #tikiwiki ravi: joined #tikiwiki
when try to delete some user and click on delete button the page became blank Guest81577: how to solve this error arildb: joined #tikiwiki vmachine: left #tikiwiki rodrigoprimo: joined #tikiwiki panamaus: joined #tikiwiki vmachine1: joined #tikiwiki Guest81577: can someone help me? vmachine: joined #tikiwiki j0n3: Guest81577: are you using local server? Guest81577: no live server
in local system it's working fine
but in my live server whole page became blank when try to delete user vmachine: left #tikiwiki j0n3: Guest81577: can you check and set php memory_limit to higher value on php.ini? Tiki-KGB: tikiwiki 03kstingel r44263 10users/kstingel/PHPdocProj/tiki-setup.php
tikiwiki [REF] just re-aligned the comment block so the box looks pretty j0n3: it was my problem using some shared vps, so I decided to set up a local server at home
i mean, i wasn't able to increase memory_limit Guest81577: ok
it's 10GB j0n3: joined #tikiwiki jonnyb: joined #tikiwiki
poloooooom vmachine1: joined #tikiwiki ricks99: joined #tikiwiki DarkCalf: joined #tikiwiki vmachine1: left #tikiwiki ricks99: polom y'all gour_: joined #tikiwiki redflo: joined #tikiwiki sandroandrade: joined #tikiwiki ricks99: joined #tikiwiki ravi: joined #tikiwiki Guest1695: i want to delete user but when click on delete logo.......whole page became blank in tikiwiki version 9.1 dhazel: joined #tikiwiki amette: polom marclaporte: joined #tikiwiki amette: I'm a bit stumped on what to do with images... File Galleries are not really good enough for them, but plugins like carousel don't work with Image Galleries... looks like kind of a catch-22 situation to me... anyone has a best practice to deal with this? Guest1695: can anybody solve my issue? amette: Guest1695: have you checked php memory_limit? white pages sound like that Guest1695: it's 10GB amette: WHAT?!?!?
sorry
what? Guest1695: every action work fine but when try to remove user,group create problem amette: that's a bit massive perhaps, but certainly not too small ;)
can you test http://doc.tiki.org/Server+Check ?
also 9.2 LTS is out which has a lot of fixes, you might want to upgrade dabright: joined #tikiwiki Guest1695: sorry memory_limit is 2GB amette: still quite a lot - 192M should be fine
256M if you want to make sure
although I don't think this will solve your problem marclaporte: joined #tikiwiki USlacker: joined #tikiwiki
god day all
good day all :-)
I posted to the mailing list then realized I might find help here.
my tiki-based blog came to a slow crawl recently
I think I traced it down to a cached wiki page
cached wiki link
I've stopepd the cacheing with nocache, but the post still takes forever to load marclaporte: joined #tikiwiki USlacker: would removing the cached rows from the db help?
polom, Marc DarkCalf: joined #tikiwiki ricks99: joined #tikiwiki dennmans: joined #tikiwiki creativetux: joined #tikiwiki
joined #tikiwiki kstingel|away: not having had much to d with theming (yet) ... is there a quick and simple way to make the {tabs()}stuff{tabs} plugin have a border and a white background?
^ * to do jonnyb: joined #tikiwiki kstingel|away: jonnyb: polom jonnyb: hi kstingel|away
probably now away then :)
now/not ricks99: kstingel|away: easy with css kstingel|away: depends which screen I'm facing ... Ubuntu hasn't got IRC loaded yet :)
ricks99: don't suppose you know off-hand which class I need to over-ride? ricks99: you want a border around the entire tabset? amette: oh, ricks99 - hi! :) ricks99: .tabset {border:1px solid #000000} amette: Can you tell me how you got the carousel on smarties link anywhere? ricks99: and hi amette amette: :) Tiki|bot: joined #tikiwiki ricks99: amette: need to use jq manually -- not the plugin. amette: I don't need a different link on every image, just link to the gallery they are coming from.
aaah, thought so - I will probably have to do that anyways as I need to use Image Galleries kstingel|away: border around each 'page' (and tab itself if possible) but content of page on white bg ricks99: ah... then could enclose the entire carousel in a div with a onclick action -: ricks99 really effective today.. answering 2 qs at once ;-) amette: :D ricks99: kstingel|away: ah. each tab is in its own "tabcontent" class kstingel|away: was thinking perhaps I should place content into a {div(class="white")}tab content {div} wrapper amette: ricks99: Sounds good, I'll try that... you use the jquery plugin, right? ricks99: amette: yup amette: ricks99: ok, thanks! I'll try that! :) ricks99: kstingel|away: try this:
{TABS(...)}
{DIV(class="custom")}content here{DIV}
{TABS}
then syle the .custom { } as needed kstingel|away: ricks99: thanks, will try that in sandbox (where I'm doing the re-write) :) Tiki|bot: joined #tikiwiki marclaporte: joined #tikiwiki Tiki-KGB: tikiwiki 03jonnybradley r44264 10branches/10.x/lib/jquery_tiki/tiki-maps.js
tikiwiki [FIX] maps: Set numZoomLevels for google maps so you can zoom in further (thanks marclaporte) ricks99: Q: in 9.2LTS (but not 10), the PLUGINS tab on the Admin: Text Area no longer shows all the plugins (and ability to enable/disable)
is this by design? or a bug? jonnyb: hi ricks99 - sounds like a bug - that one often runs out of memory ricks99: recall a discussion about that, but i'm not getting any such error. jonnyb: seems fine for me here (locally)
could it be theme related? ricks99: 9.2
?
you see the list of plugins on the PLUGIn tab? -: ricks99 maybe accidently customzed something he shouldn't have jonnyb: yup - on 9.x svn ricks99: ah. svn
im 9.2 jonnyb: this rings a bell, think i found one theme that doesn't show some things -: ricks99 using fivealive default jonnyb: is the list there in the DOM? (or source?) amette: quite a coincidence, just on the admin plugins page in a tiki 9.x from SVN two days ago and the plugins work here, too jonnyb: hi amette amette: heya jonnyb :) jonnyb: been meaning to add a search option there for sites on 64M shared hosting (i seem to have a few) ricks99: i'm running 9.2 (not svn)....
ahh. the <fieldset id="plugin" is set to display:none
ah....
ah ha!
it only shows if you filter the Experimental options
looks like it was a PICNIC error. Not Tiki. Thanks all jonnyb: PICNIC? ricks99: Problem In Chari -- Not In Computer
*Chair jonnyb: :) -: ricks99 needs more coffee kstingel|away: ricks99: cafe fabricius: joined #tikiwiki RobertPlummer: polom all
anyone wanting to participate in the aloha editor discussion?
all^ jonnyb: hi RobertPlummer RobertPlummer: hi jonnyb
I'm seeing if the discussion can come to #tikiwiki rather than all of us go there. That way we log it all. gour: +1 RobertPlummer: gour: You have interest in the editor? gour: RobertPlummer: well, something has to be used for adding content, right? RobertPlummer: *Is glad we have someone so interested in tiki*
gour: Is your recent month or two your first taste of tiki? gour: for now discovering problems...yes it is RobertPlummer: gour: My desire is the same. To make tiki a solid content editor that is easy to use. Drag and drop ajax plugins, and to make new syntaxes possible.
and easy -: gour nods RobertPlummer: *turns on Eric Clapton radio to go into developer mode* gour: "tears in heaven" ? RobertPlummer: lol
"Watch Yourself"
A little peppy blues to get into the zone... dabright: joined #tikiwiki RobertPlummer: gour: You'd be interested in the new parser system too as it is what gives wiki syntax and plugins the ability to be dynamically edited.
gour: It is maturing, but still has a few bugs. gour: RobertPlummer: who is tiki's server-guy understanding server-releated code? RobertPlummer: gour: Bugs are generally easy to fix though, and it is passing all tests associated with it now, both wiki -> html and wiki -> wysiwyg(html) -> wiki.
gour: I don't understand, explain.
gour: Talking about changi|away perhaps (server wiz)? gour: RobertPlummer: there is bug in absolute_urls.php and i fixed my problem with a ugly workaround, but it would require proper patch
..to make tiki work properly behind reverse-proxy RobertPlummer: gour: I'm not sure who would be the best candidate would be for that, are you a experienced developer? gour: RobertPlummer: not really and especially not with php...those were my 1st php lines :-) dabright: I missed most of the namespace separator discussion. Is there some concise explanation of why / or // couldn't be used? I would have thought that context would allow distinguishing those from external (e.g., http://) links. -: gour did not write web code so far RobertPlummer: gour: What languages are you familiar with if any?
gour: Any forms development? deliminator: joined #tikiwiki
hello dabright: The / might have led naturally to a sub-page syntax, too, rather than just a one-level (namespace) hierarchy. RobertPlummer: deliminator: Welcome from the team at Tiki
deliminator: Would you like to introduce yourself (he is from Aloha Editor)? gour: RobertPlummer: well during the university and later i learnt several (fortran, pascal, C/++...familiar a bit with python, played with haskell a bit), but my career was not going towards developer-route which is only a hobby for me now...considering to learn ada or something for a general desktop gui app...otoh, i've needs to put together some sites as well - that's why tiki ;) deliminator: Hello, I'm deliminator, sometimes also called Tobias, and I work at girigiri and I'm on the aloha core team -: gour waves and greets deliminator RobertPlummer: deliminator: We are glad to have you and your expertise! deliminator: Always glad to help if you have any questions gour: huhh..now i'm being called for a dinner :-/
bbs...hopefully RobertPlummer: deliminator: May I just say that my recent work to get Aloha editor working, has actually been very pleasant :). I am very much liking how you are using a dynamically typed language in sort of a strongly typed manner.
deliminator: My first question is about integration, you have stated there are some changes coming down the pipe that will provide an easier integration, can you explain? deliminator: Not sure what you mean, but glad it is positive :-) RobertPlummer: deliminator: I was referring to the namespaces, and plugins, makes it much more organized. deliminator: I have been working on the aloha-modular branch RobertPlummer: Ah ha! That explains why I didn't see the changes yet. deliminator: https://github.com/alohaeditor/Aloha-Editor/issues/737
https://github.com/alohaeditor/Aloha-Editor/blob/dev-modular/src/demo/boilerplate/index-modular.html
The first link points to the relevant issue
The second link is an example
Essentially, you just include the script tags. You don't need to know anything about requirejs any more
requirejs is still working of course RobertPlummer: deliminator: Exactly what I would look for. I started the xml request method in jQuery.sheet, and it ended up just taking too long to load everything.
So to get aloha editor working in tiki, what would be needed? I apologize if this is a repeat, but I know some code has changed recently. deliminator: I don't know what you mean with starting a xml request. RobertPlummer: I see <script src="../../lib/vendor/jquery-ui-1.9m6.js"></script> for example, will that conflict with our jquery ui?
deliminator: I should say http request.... or better, an ajax call. deliminator: you can use jqueryui 1.9 or up
What has the AJAX call to do with Alhoa? RobertPlummer: deliminator: < script src='' data-aloha-plugins='common/ui,
common/table,
common/list,
common/link,
common/highlighteditables,
common/block,
common/undo,
common/image,
common/paste,
common/commands,
common/abbr,
common/format'></script>
THose are called in via an ajax call after the point of loading aloha editor, but seems that is done away with in your branch.
which is good! :) deliminator: Are you working with the minified aloha? RobertPlummer: deliminator: No, I was working with master deliminator: These files should be compiled into aloha.js, and should not have to be loaded lazily
OK, that explains it. You have to compile aloha to get best performance RobertPlummer: deliminator: ok
deliminator: Are their directions on how to build? deliminator: You compile it by customizing the build profile in build/aloha/build-profile-common-extra.js
http://aloha-editor.org/guides/develop_aloha.html
4.3 Customized Builds:
The simplest thing is to copy the existing build profile somewhere in your own project RobertPlummer: Ok, very good. I will experiment with today. deliminator: then edit it and only include the plugins that you need to keep the size as small as possible
you also have to adapt the appDir url
in the build profile
and also startFile and endFile
otherwise the paths are incorrect since the build profile is in a different folder RobertPlummer: How does one use custom language files with plugins? deliminator: i18n should just work
If you have a german browser, the german i18n files are downloaded by requirejs
if you have an english browser, the english files are downloaded RobertPlummer: We have that implemented, but I believe we use a function tr('Words') to do our translations. deliminator: you can also set the locale option in the build profile to compile a specific language into the output file
i18n.t()
You can use the requirejs i18n loader plugin RobertPlummer: Could we just not include a language file and use tr() throughout the plugin?
For custom plugins we have them already translated for other parts of tiki, would be nice to reuse our code. deliminator: I don't know how your mechanism works
I suppose you could, couldn't you? RobertPlummer: We will have to. deliminator: Do you see any problems with it? RobertPlummer: deliminator: Don't think so.
deliminator: Next question is on line breaks. We need a way to be able to use <p> OR <br> depending on the situation. If we updated the code to know when to use one over the other, is there any problem in how aloha tracks position, line height, etc?
deliminator: This would be without using shift. And we need to modify what shift does as well on insert of those elements. deliminator: <br>s are supported via shift+enter RobertPlummer: deliminator: I know, but tiki has a setting (default to <br>) that allows you to switch from one to the other.
deliminator: We need aloha to follow suite. deliminator: so it's just a question of which keystroke inserts a br - once they are in the content, they are supported RobertPlummer: deliminator: ok, because ckeditor has a host of issues apparently with such a content. Could you point me to where to find how that is handled in aloha? deliminator: http://aloha-editor.org/guides/functional_description.htmlI
There is some info at this link
There is an I at the end which is incorrect
But there is no out-of-the box functionality to just flip a switch and have brs inserted
you'd have to build that yourself
pull requests welcome :-) RobertPlummer: deliminator: How about where that is handled within the code?
deliminator: Pull requests are my speciality! jonnyb: hi deliminator - i did some of the work getting creditor into tiki a few versions ago...
it sounds like aloha works in what we call "wiki_paragraph" mode, which i think is the "right way" and made a requirement for wysiwyg in tiki
personally i've never spent any time supporting the rather weird "html 3.2" default way tiki uses <br>s instead of <p>s deliminator: markup.js preProcessKeyStrokes and processShiftEnter and processEnter RobertPlummer: jonnyb: I think the idea would be to support both, we want to remain backward compatible with wiki content. deliminator: It should end up in engine.js with execCommand('insertlinebreak') and execCommand('insertparagraph') for both behviours RobertPlummer: great! deliminator: Hello jonnyb, by default Aloha will create or split paragraphs when enter is pressed. When shift+enter is pressed, <br>s are inserted instead Tiki-KGB: tikiwiki 03jonnybradley r44265 10branches/10.x/lib/jquery_tiki/tiki-jquery.js
tikiwiki [FIX] comments: Remove previous comment form when opening a new one, confusing to have multiple textareas (thanks Bsfez) jonnyb: yes, that's the usual convention
we're not great on following conventions round here ;) RobertPlummer: deliminator: My next question is on contenteditable="false", how does that propagate to the element's children?
deliminator: CKEditor has a nasty habit of not inheriting this setting to the elements children, thus something we don't want edited is editable farther down into it's hierarchy. deliminator: it should propagate to all descendants of the editable, until contenteditable="true" is encountered, which again should propagate to all descendants until contenteeditable="false" is encountered
in aloha you would solve the problem of having blocks of non-editable content inside an editable with the block plugin RobertPlummer: deliminator: That is music to our ears, any browsers have difficulty with this?
deliminator: The reason I ask is that in Tiki we have some pretty cool plugins that need to be rendered, but static only. When you go to double click, a popup comes up, and then you can edit the plugin. Each time though we want to (ideally) show the output of the plugin. So after a plugin is edited, we want to update the contents of the element representing the wysiwyg plugin. Which also leads to my next question, upon updat
e, will there be a problem? Tiki-KGB: tikiwiki 03jonnybradley r44266 10branches/10.x/lib/jquery_tiki/tiki-jquery.js
tikiwiki [FIX] comments: Use the "on" event handler instead of "live" which was deprecated (ages ago) deliminator: http://aloha-editor.org/guides/plugin_block.html RobertPlummer: deliminator: For example, if I just have have setTimeout(function() {updatePlugin();}, 1000); will this contenteditable still propigate if the element has changed since aloha loaded? deliminator: http://aloha-editor.org/builds/stable/alohaeditor-0.22.6/aloha/demo/block/
The second link has a simple demo with a few blocks RobertPlummer: deliminator: Our aim is to eventually have ajax updated plugins in real time while the user is editing the page. deliminator: Open the sidebar on the right and you will be able to control the block content
you can also drag the blocks around
You can have your own ui with modals that interact with the block content, since you can directly access the DOM elements inside the block
and you can update it however you want without problems, since it's basically a black box for aloha RobertPlummer: oh wow deliminator: you can also have editables inside the block that are interpreted by aloha RobertPlummer: jonnyb: You gotta check this out! jonnyb: coo, sounds interesting RobertPlummer: That is really exactly where we want to go. Very nice! deliminator: there is an implementation in a cms that I worked on
demo.gentics.com
you can log in with node/node
and edit the page RobertPlummer: deliminator: Next question, when is genetics moving to tiki?
:)
j/k deliminator: in the demo you can insert custom "tags"
which have been implemented with the block plugin
I work at Girigiri
Actually, I'm also working on a wiki product
wikidocs.com RobertPlummer: Cool deliminator: Seems we are competitors
:-) RobertPlummer: deliminator: I've looked at it somewhat, but not really closely, Tiki has a custom way of building toolbars, how is integration will aloha be in this regard? deliminator: Have you looked at wikidocs.com recently?
it now has a new UI RobertPlummer: deliminator: competitors, no, common interest of others, yes. We work together to make software better. If there were just one of everything, we'd rarely see a need to make it better.
looking deliminator: The toolbar is completely custom
but with static HTML embedded in the page
so, we don't use Aloha's out-of-the-box UI at all RobertPlummer: deliminator: Nice deliminator: The code we use is available on the dev-ui-a-la-carte branch
It's relatively simple
we override the ui-plugin and some components modules via the requirejs path mechanism RobertPlummer: deliminator: How up to date is that code though? deliminator: and hook them to the static html via class attributes
The ui-a-la-carte? Fairly up to date I would say RobertPlummer: deliminator: For example the added logic for loading jQuery ui as <script/> rather than via ajax? Do they update dynamically?
deliminator: I guess what our aim is to code as little "glue" as possible, but have a solid editor. deliminator: You can keep Aloha from loading jqueryui dynamically by defining it
I understand, but if you want your own UI, you will not get around some glue unfortunately RobertPlummer: deliminator: Right, but then your jquery ui failes, jQuery.ui.events.event doesn't exist. Is that a 1.9 thing?
deliminator: Understood.
or maybe it is jQuery.events.event deliminator: You say "your jquery ui" fails, BUT if you have defined it, it would not be Aloha's jqueryui it would be your own.
jQuery 1.9 is required if you want to use Aloha's out-of-the-box ui
If you override the ui-plugin, as in the dev-ui-a-la-carte branch, then older versions will probably work RobertPlummer: deliminator: ok, very good deliminator: The alacarte branch depends on bootstrap by the way RobertPlummer: ok deliminator: And jquery ui as well
But only for the autocomplete plugin
which could be migrated to bootstrap typeahead RobertPlummer: deliminator: I guess now we are interested in where Aloha is headed, what things do you have for us on the horizon? deliminator: That is a good question arildb: joined #tikiwiki deliminator: I'm not sure whether I can give a good answer
dev-modular, dev-ui-a-la-carte, accessibility, undo/redo
Those are issues I'm working on
When I have the time to do so RobertPlummer: is undo redo not working right now? deliminator: That, again, is a good question... Apparently it works for some people
It isn't working for me RobertPlummer: :) deliminator: Or are my expectations too high?
I single undo and you don't know what you'll get acceptable? jonnyb: ah, 1 more q - we'd need a special license right? is that easy? deliminator: Not sure whether you need a special license...
Is your product open source? RobertPlummer: deliminator: lgpl
2.0v (I think) deliminator: GPLv2
... Aloha is jonnyb: yup - also MIT & BSD compatible deliminator: so that should be fine, no?
Aloha? No, just GPLv2 jonnyb: no, GPL is different RobertPlummer: deliminator: You guys changed? deliminator: Yes, from AGPL to GPLv2
Because Drupal needed it to integrate it into v8
And they are GPLv2 RobertPlummer: From license.php - "With a FOSS license exception you may be allowed to redistribute Aloha Editor along with other open source projects that are MIT, BSD or similar licensed." deliminator: So, they don't need a special license -: gour is back deliminator: Hmmm... I suppose it's because MIT etc. allows someone to make changes and not open source the changes RobertPlummer: deliminator: From communications with the coordinators for Aloha Editor they've said we don't need an exception, BUT we would feel a whole lot better about investing our time and money if we did :):):).
deliminator: Especially if we are going to be adding some of the integration components that will make it better compete against editors such as CKEditor via pull requests. deliminator: Those are the people to talk to jonnyb: sounds like we need an exception to me, and not much point going further until that's guaranteed to happen (i'm afraid) deliminator: (Hmm, maybe not a good idea to post email addresses on irc) RobertPlummer: This is a logged channel fyi. deliminator: Oh well :-( RobertPlummer: deliminator: It has been a pleasure working with you thus far and we look forward to seeing where Aloha + tiki go. I will start coordinating with the previously mentioned people to see about getting an exception. deliminator: ok. good luck to you and the tikiwiki team. Let me know if you have any questions or problems that I can help with. RobertPlummer: http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility jonnyb jonnyb: thanks deliminator RobertPlummer: tahnks deliminator
thanks
jonnyb: I'll start a new page on dev.tiki.org Aloha-Editor and put some of the useful information there gained today. marclaporte: deliminator: LGPL is a more suited license for Aloha RobertPlummer: marclaporte: polom! marclaporte: LGPL was originally called Library GPL with the idea of libs included in other apps. And Aloha is mostly to be included in other web apps jonnyb: hi marclaporte - never knew that RobertPlummer: LGPL gives you more ownership, every developer (or company hiring developers to develop) has ownership of the code they integrate. That is how I understand it, correct marclaporte? deliminator: I don't make license decisions. marclaporte: "The GNU Library General Public License (as the LGPL was originally named) was first published in 1991, and adopted the version number 2 for parity with GPL version 2. The LGPL was revised in minor ways in the 2.1 point release, published in 1999, when it was renamed the GNU Lesser General Public License to reflect the FSF's position that not all libraries should use it. Version 3 of the LGPL was published in 2007 as a list of addi
RobertPlummer: I try to avoid interpretations as I am not a lawyer RobertPlummer: But I am not a lawyer :)
Thanks marclaporte *speaking around his own foot* deliminator: I read something once where it was explained that the GPL is preferred, except when there are multiple competing implementations of a library, in which case it is acceptable to use the LGPL
The idea is that you want to keep other people from using another commercial closed source library over the LGPL library
At least that's what I read once long ago kstingel|away: left #tikiwiki j0n3_: joined #tikiwiki RobertPlummer: http://dev.tiki.org/aloha-editor
http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility states:
"I want to release a project under: LGPLv2.1 only" + "I want to copy code under: LGPLv2.1" = "OK" so license is compatible as an exception.
nope, nm, thought this was aloha specific.
"OK: Convey project under GPLv2 or later [7]"
So jonnyb & marclaporte: This would mean we would have to amend our license unless they give us an exception?
"7: LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (as noted in the table), you can make this combination." marclaporte: The best is for Aloha to license as LGPL v2 or v3 RobertPlummer: marclaporte: I'm not a magic man, are you willing to work yours? jonnyb: sorry RobertPlummer, just gibberish to me - maybe send a mail to legal@tiki.org? RobertPlummer: marclaporte: I know you have a log going on. changi|away: polom jonnyb: hi changi changi: apparently i've fixed email notification :)
is there any thing else which isn't working properly ? jonnyb: yes getting emails now - in fact two types :) gour: changi: hiya, i'm told you're expert for tiki's server-related code? changi: gour: it depend what do you mean by server-related code rodrigoprimo: joined #tikiwiki gour: changi: the code is lib/setup/absolute_urls.php is too simplistic and does not take into account when tiki is working behind reverse-proxy and therefore tiki wrongly attaches local port of the webserver listening behind reverse-proxy to each URL...so somet reverse-proxy detection should be added...no proper idea. maybe checking for X-Forwarded-For header or something to discern if tiki is behind
reverse-proxy and then set http_port appropriately? marclaporte: RobertPlummer: what do you think of http://createjs.org/ ? gour: "co-funded by the European Union" RobertPlummer: marclaporte: What is it? Just a gui for those two editors? changi: gour: HTTP_X_FORWARDED_FOR can be used marclaporte: It's related to : http://bergie.iki.fi/blog/decoupling_content_management/ gour: changi: any idea how to detect server is behind reverse-proxy? checking that header is just my wild idea knowing that front-end server is adding it RobertPlummer: Would be neat to see modules + Aloha changi: if you're behing a reverse proxy you will have 3 more header variable : HTTP_X_FORWARDED_FOR HTTP_X_FORWARDED_HOST HTTP_X_FORWARDED_SERVER gour: hmm jonnyb: off now, see you tomorrow... gour: changi: ok..i'll think about it RobertPlummer: ok guys, the race is on. using the new dev-modular branch, I'm working to get Aloha editor loading by days end. changi: gour: just tested it with nginx and apache, both add the header gour: changi: i also see those headers in hiawatha's logs
but not HTTP_X_FORWARDED_SERVER
..header fabricius: joined #tikiwiki changi: gour: it's the same value as _HOST gour: ok USlacker: joined #tikiwiki dabright: joined #tikiwiki RobertPlummer: WOOOHOOO, aloha editor works!
This time no javascript errors
It is a hollow shell, but it works.
I will commit in the morning, finally progress! -: gour sends a cookie to RobertPlummer RobertPlummer: :)
Before it would load, but I got errors of out javascript failing, I'm sure there will be other things affected, but it looks to be loading perfect.
And what is more, I already have a custom ribbon!