marclapo1: joined #tikiwiki lindonb: joined #tikiwiki Tiki|bot: joined #tikiwiki marclaporte: joined #tikiwiki lindonb: joined #tikiwiki Gwayne: joined #tikiwiki Tiki-KGB: 03lindonb r50698 10trunk/ 10(6 files in 4 dirs)
[REF] tablesorter: make necessary preference and status checks less error-prone and easier to implement Tiki|bot: joined #tikiwiki marclaporte: joined #tikiwiki Tiki-KGB: 03lindonb r50699 10trunk/lib/core/ 10Table/Factory.php 10Table/Plugin.php * [REF] tablesorter: eliminate unused code and add a little documentation marclaporte: joined #tikiwiki lindonb: left #tikiwiki Telesight: joined #tikiwiki chibaguy: joined #tikiwiki fabricius: joined #tikiwiki redflo: joined #tikiwiki Tiki|bot: joined #tikiwiki chibaguy: joined #tikiwiki Tiki|bot: New Forum Posts: Actualización de versión - http://tiki.org/tiki-view_forum_thread.php?forumId=15&comments_parentId=51722 jonnyb: joined #tikiwiki
pom pom polom Tiki|bot: joined #tikiwiki chibaguy: joined #tikiwiki fabricius: bow bow bolow chibaguy: joined #tikiwiki Jyhem: polom jonnyb: hi Jyhem, hi fabricius Jyhem: hi jonnyb fabricius: joined #tikiwiki jonnyb: joined #tikiwiki Tiki|bot: joined #tikiwiki fabricius: hi Jyhem, hi jonnyb jonnyb: hi fabricius RobertPlummer: joined #tikiwiki
polom all chibaguy: joined #tikiwiki xavi: joined #tikiwiki
polom RobertPlummer: polom xavi xavi: hi Robert
RobertPlummer: do you remember that issue with some tracker items not being displayed in the calendar view (TrackarCalendar) when they had information in the field for the "location" (resource)? RobertPlummer: yes
xavi: xavi: the problem seems to disappear if I remove the upper case from the strings in that dropdown box for location
Reproduced in local jonnyb: hi xavi, RobertPlummer and all
aha, good catch xavi - might be able to fix that :) (resource views worked fine in my test, bet that's why) xavi: yep RobertPlummer: interesting.
trackers are a bit too advanved at times for me.
So I found a bug in wikiLingo today. If you used n*--text--n it would go into an infinit loop, because the block modifyer '-' was being used, but it was also part of the markup for strike. Took me about 10 minutes, and I fixed it with a negative lookahead. wikiLingo is getting way more solid guys. I'm so happy it is in trunk!
That we are able to break down these problems within just a few minutes is awesome. Also, I added a unit test to look for it, and ensure it never pops up again. Tiki|bot: joined #tikiwiki RobertPlummer: and tiki will reap the benifits. fabricius: robertplummer: please mind the idea of encapsulating CKE and wikilingo from each other RobertPlummer: fabricius: they don't support nesting of plugin/widgets, and they have no plans to.
That is the main issue, the other is that they modify the html that we feed it to what it feels like it should be for you.
fabricius: The focus on wysiwyg will come soon, but is not yet. Right now the focus is ensuring the foundation is as solid as possible, and getting the FutureLink-Protocol in place within it. That is nearly done/
.
fabricius: Another reason is that contenteditable="true" in browsers is getting better and better, so that a wysiwyg "editor" will not actually be needed.
fabricius: There was also a HUGE effort put into implementing a wysiwyg editor, that were somewhat like putting a square peg in a round hole. Much of it was not able to put through unit tests, to ensure, and force it to work correctly. That will not be allowed with wikiLingo. We are going to have unit tests from the beginning when we are on that initiative. So in a clean room, ie the developers computer, we can quickly u fabricius: RobertPlummer: I was not referring to WYSIWYG, but to the Either/Or activation of the two features ... using wikiLingo, CKE should be deactivated completely and no need to activate, as now ... was just a reminder ;-) RobertPlummer: lol, ok thanks, I thought I had lost you for a minute. I was thinking "Torsten, we've been through this...". ;)
fabricius: Thanks for all your support on the front, I've been working out in my mind how we are going to implement the convene plugin in wikiLingo, I'm getting excited about it.
I wish I could clone myself, that'd make this easier. xavi: jonnyb: confirmed also in the show instance: http://xavi-9794-5177.show.tikiwiki.org/tiki-index.php?page=Tracker_as_Calendar_10 jonnyb: thanks xavi - will try and investigate (later) xavi: items with a value with some Capital letters in the field "location" are not shown in the resource view
ok, thks jonnyb: :) xavi: jonnyb: quick question: is there any var_dump equivalent for jquery? jonnyb: console.log(thing) maybe?
is generic javascript, not just jquery RobertPlummer: console.log($); Tiki|bot: joined #tikiwiki xavi: ok, thks RobertPlummer: (though that may not be very affective) marclaporte: joined #tikiwiki RobertPlummer: hi marclaporte
(polom) fabricius: joined #tikiwiki RobertPlummer: fabricius: So get this, you know how in convene there is a funny sort of a markup?
fabricius: in wikiLingo, plugins can "talk". So what if we allowed this. So rather than have repeating dates and users, we had a sub plugin within convene? The plugin would be called something like an "entity", or "schema". johnnyfive: joined #tikiwiki RobertPlummer: {CONVENE()}{entity type="user" name="Robert" yes_dates="5/5/15 10pm|5/6/15 10pm"}{entity type="user" name="Torsten" no_dates="5/5/15 10pm" yes_dates="5/6/15 10pm"}{entity type="date" value="5/5/15 10pm"}{entity type="date" value="5/6/15 10pm"}{entity type="date" value="5/7/15 10pm"}{CONVENE}
fabricius: ^ for example
So, the body value is not an actual traversible structure. In this case:
Convene.user[] and Convene.date[] (both being a collection)
Visually using wysiywg this could be both designable, and easy to render to html or other structures.
lphuberdeau: What do you think of the above?
programming in wikiLingo, I'm actually liking it. johnnyfive: left #tikiwiki RobertPlummer: What is more, is that entity's could be reused, for example, in advertising and json linked data, as it is a schema created by schema.org, which is built from the leaders in advertising. But simply because it gives computers a better understanding of what sort of content you are pushing/pulling around. fabricius: joined #tikiwiki Tiki|bot: joined #tikiwiki Tiki-KGB: 03lphuberdeau r50700 10trunk/ 10(6 files in 4 dirs) * [ENH] Update auto-reply messages to be more accurate xavi: lphuberdeau: ?
I've just hit an issue in tracker field files (12x): uploading a large (4.3Mb) pdf file through Tracker Field Files fails, but uploading it through the file gallery directly (to the same file gallery as the one defined in the tracker field files) works as expected
apache error log says that the issue seems to be with mod_fcgid: stderr: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /path/lib/core/TikiFilter/PreventXss.php on line 252
and that line seems to be doing a preg_replace: $val = preg_replace($patterns, $replacements, $val);
I wonder if that preg_replace is always needed, and what workaround could be applied for large files to avoid the timeout of 30 seconds
mmmm, and I had set in htaccess that max_input_time was 90 seconds, not 30 (sounds weird) Tiki-KGB: 03lphuberdeau r50701 10trunk/lib/cache/cachelib.php
[FIX] notices - those preferences do not exist unless a plugin from mods is installed lphuberdeau: that looks a bit strange... xss filtering on a binary file makes no sense at all
in fact, all of the code is on place for it not to happen marclaporte: joined #tikiwiki lphuberdeau: xavi: got more of a stack trace? brolin_empey_: joined #tikiwiki sipherdee_: joined #tikiwiki leagris: joined #tikiwiki Tiki-KGB: 03marclaporte r50702 10branches/12.x/lib/prefs/fgal.php
Turning fgal_tracker_existing_search (Allow searching for existing files in the tracker files field) off by default, as it's a less common use case
03lphuberdeau r50703 10trunk/ 10lib/user/monitormaillib.php 10templates/comment/list.tpl 10styles/layout/design.css 10lib/webmail/tikimaillib.php
[ENH] Remove inline styles, add name to reply-to address, replace some javascript by CSS diggy: joined #tikiwiki fabricius: joined #tikiwiki Tiki|bot: joined #tikiwiki