#foswiki 2017-10-04,Wed

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
GithubBot[distro] vrurg pushed 1 new commit to Item14237: https://git.io/vdld5
distro/Item14237 07c6274 Vadim Belman: Item14237: Started documentation on basic programming concepts of v3
[03:08]
***GithubBot has left [03:08]
FoswikiBothttps://foswiki.org/Tasks/Item14237 [ Item14237: Implement Development.OOConfigSpecsFormat proposal ] [03:08]
...................................... (idle for 3h8mn)
***ChanServ sets mode: +o MichaelDaum
MichaelDaum changes topic to: Download: https://foswiki.org/Download - Logs: http://irclogs.foswiki.org/bin/irclogger_log/foswiki - Slack: https://foswiki-slackin.herokuapp.com/ - Bugs: https://foswiki.org/Tasks - Next Release meeting Monday 16 Oct 2017, 1300Z
[06:16]
........................ (idle for 1h58mn)
zak256Good morning MichaelDaum. I managed to reduce the loading time for a page with about 30 searches from more than 35 seconds down to about 15 seconds by replacing them with about 23 DBQueries!
However this is of course still too long :-/
[08:14]
MichaelDaumthen there are too many searches [08:15]
zak256So there is no way too tweak that further?
Ah... by reducing I mean: There are *no* searches anymore!
[08:16]
MichaelDaumthe idea is to prevent searching for stuff that the user might not even be looking for
that way you can delay a search to the point the user is really asking for that kind of information
[08:18]
zak256Yes I was trying to use JQueryLoader [08:19]
MichaelDaumthats not what I am saying
for example
[08:19]
zak256But that didn't work because our searches/now queries are included from another page and that broke JQueryLoader. [08:20]
MichaelDaumthere is one big overview page consisting of many dynamic tables each of which is generated by a search of its own
each table on that big overview page has got a heading such as (1) Running Projects (2) Past Projects (3) Withdrawn Projects (4) Archived Projects (5) etc
when a user visits that page he will pay for each of these searches ... even though he is only interested in (1)
[08:20]
zak256And you mean these searches need to be outsourced into extra pages? [08:23]
MichaelDaumwhat I am saying is: please review the number of searches -> are you really requiring them ... all the time [08:23]
zak256Unfortunately yes... this are usually not many information in each search/query. For example there are servers associated with some application, then there are certificates, systemusers, ...
and each server, certificate, systemuser, ... is represented by a topic
[08:24]
MichaelDaumone solution is to call the ProjectsOverview page with a parameter: %URLPARAM{"projectstatus" default="running"}% ... and use that to build one table ... instead of all [08:24]
zak256the idea is to get an overview of all the "things" which are relevant for example for this application and to show that to the user in one page.
If I for example make an extra page that informs about the servers, then an extra page for the certificates and so on, then each of this page will a) be very small, and our users don't get the overview. They have to click on each page one by one to get the picture.
[08:25]
MichaelDaumwhat if a user isnt interested in certificates. he only wants to see the servers the app is running on. [08:27]
zak256Then I could strip the certificates and its search for that user of course.
But the idea is to tell users about that information even if they are not specifically looking for it. Just to tell them "did you know? this application has this and that..."
[08:28]
MichaelDauminstead of (1) user selects app (2) system generates one big overview page with everything related to this app (3) user waits forever ... [08:30]
zak256like if you see a technical chart about a device, you don't want an extra page for memory capacity, another one for cost, yet another one for this and that...
It would be a good way to use JQueryLoader for this and hide the information in TWISTYs. The latter is already done.
[08:30]
MichaelDaumdo this (1) user selects app (2) user selects property (3) system renders one table quickly (4) user reads the information and (5) might click on another property ... etc [08:31]
zak256So he could just unfold the information he wants
yes, if I could manage to show this then all in one page, this would wokr
work
Ok, but the main thing is, I did everything I could so far. There is nothing "wrong" with 15 seconds and ~20 DBqueries.
Then I will work something out.
Another thing: I think I encountered a slight bug: If there are line breaks (encoded as %0d%0a%0d%0a) in a formfield value and that gets rendered within a table, I get the linebreak, but the table is broken, i.e. gets not rendered anymore. From the search it works, so I guess this somehow needs to be converted somehow?
[08:31]
The latter is really a showstopper for now, so I would like to help fixing that if I can. Probably some code handling this from SEARCH has to be migrated to DBQUERY? [08:40]
jastyou can work around this by, for example, using HTML markup for your table instead of TML table syntax
the alternative, I guess, is a fun afternoon of nesting escaping macros
[08:41]
zak256Yes, possible. But that would make our searches/queries even more ugly. [08:42]
MichaelDaumzak256, either use a HTML table or try $flatten($formfield(textarea))
TML tables are bad for layout ... I keep telling this people but meh... ;)
they are simply not robust enuf
[08:42]
jastthey're designed primarily for data, the traditional purpose of tables
and they work pretty well for that
[08:44]
zak256Well... we *could* people just tell to write everything in html in the first place :-P [08:44]
MichaelDaumzak256, actually true. [08:44]
zak256I have no problem with html, but we implemented the wiki *because* people should concentrate on writing documentation and not coding text. [08:45]
MichaelDaumthere are good arguments on the net why markdown is better for writing documentation than wysiwyg... [08:46]
jastpersonally I think for complex topics with a lot of dynamic content, it's reasonable to use less TML and more HTML [08:46]
zak256ok, $flatten() at least resolves the error but removes linebreaks as well
I am thinking of redesigning the whole page, so this could solve this. But for now all I want is to migrate our wiki from version 1.1.2 to something recent.
[08:46]
MichaelDaumif you dont like this then your only option is to ditch tml tables [08:47]
zak256So implementing this in code is no option? As I said, in the SEARCH it worked... [08:48]
MichaelDaumnote that for lots of cases %DATATABLES from JQDataTablesPlugin is just fine for dynamic tables that dont need extra formating per column [08:48]
zak256I write JQDataTables on my list for the redesign. [08:50]
jastyou *can* get it working with TML tables but then you need escaping macros and that's its own kind of tricky [08:50]
MichaelDaumgoes like this %DATATABLE{"query" columns="formfield1, formfield2..." ...}% ... boom
DATATABLE fetch their data asynchronously on their own ... just in case you are still wondering wtf is going on with JQueryLoader not working properly ;)
[08:51]
zak256? So you mean if JQueryLoader doesn't work from within an included page, neither will DataTable ? [08:52]
MichaelDaumerm, huh?
what I am saying is that instead of wrapping your head around dynamic search tables, JQueryLoader and pages taking too long loading... just use %DATATABLE: this solves almost all of your above problems
[08:52]
zak256JQueryLoader doesn't work when it is in a topic HereIsAJQuery and I access the page MyPage which has %INCLUDE{HereIsAJQuery}%
Ok, I will try out DATATABLE, just reading the doc...
[08:54]
MichaelDaumRead The Fine Documentation: https://foswiki.org/System/JQueryLoader how to specify the location from where to fetch the data, i.e. how to make it _not_ depend on the page it was executed from!!! [08:56]
....... (idle for 31mn)
ggodlerhey guys [09:27]
FoswikiBothey guys is there anyway to amke 'verbatin' not still turn WikiWords into links [09:27]
zak256ggodler: does <pre></pre> work? [09:27]
ggodler<pre>test</pre>
i have some questions about foswiki
[09:27]
zak256ggodler: If you don't ask a question, no one can answer. [09:35]
Ok, I tried DATATABLES now successfully, but there are for now two things: a) I want to link one form field ("Name") with the corresponding topic. So something like this: [[$web.$topic][$formfield(Name)]]
b) Sometimes the value of a formfield is another topic. Can I then display the content of a specific formfield of _that_ topic?
Is that possible with DATATABLES?
Apart from that it really looks promising.
[09:41]
ggodlerzak256 i agree :)
we have foswiki installed on one server and I copied files to another and conf setting from apache
i get error:
Not Found The requested URL / was not found on this server.
we are using fastcgi
[09:53]
zak256I am afraid that could be anything. You have to check the apache configuration [09:56]
ggodlerapache log files are empty [09:56]
jastthen perhaps there's a different web server running on that server? [09:56]
zak256maybe try this here: http://foswiki.org/Support/ApacheConfigGenerator [09:56]
ggodleryes, apache config file was generated with [09:57]
zak256The configuration file is in the correct directory? [09:57]
ggodleri think so... /etc/apache2/sites-enabled [09:59]
we have old version, how can I check which version?
my plan is to migrate and then upgrade
forget, I found: This site is running Foswiki version v1.1.9, Release Foswiki-1.1.9, Plugin API version 2.2
[10:05]
............... (idle for 1h11mn)
***ChanServ sets mode: +o Lynnwood
ChanServ sets mode: +o Lynnwood
[11:18]
......................... (idle for 2h3mn)
ChanServ sets mode: +o gac410 [13:24]
zak256Hi gac410. Do you know if there are any more examples for jqloader somewhere? I would like especially some examples for the placeholder parameter... [13:33]
gac410Hi zak256 - no I'm not really familiar with that function. I'm not all that strong in javascript. [13:34]
zak256ok nevermind, I'll figure it out somehow [13:34]
gac410hm Tasks/WebHome uses it. [13:35]
zak256no placeholder parameter unfortunately [13:36]
gac410MichaelDaum_ is the js deity around here ;) [13:37]
zak256Yeah, I bugged him just a few hours before with something else...
anyway... this is one of the not-important-things on my list
[13:38]
................ (idle for 1h16mn)
JulianLevensMichaelDaum trying to set-up Kerberos SSO
I'm getting a token created by the browser and passed thru to the KerberosLogin.pm
The error I get is: MAJOR: An unsupported mechanism was requested
The error is from GSSAPI module and not very informative
any ideas?
[14:54]
..... (idle for 24mn)
***JulianLevens has left [15:20]
zak256What is KerberosLogin.pm? I set up Kerberos with ApacheLogin and GSSAPI only. [15:25]
....... (idle for 32mn)
The only things I did were the following settings in httpd-configuration:
Require valid-user
AuthName "Userid"
AuthType GSSAPI
GssapiCredStore keytab:<path-to-keytab-file>
GssapiSSLonly On
GssapiLocalName on
GssapiAllowedMech krb5
GssapiNegotiateOnce On
and I needed to patch ApacheLogin.pm to lowercase all usernames.
If it still doesn't work I assume problems with the keytab.
[15:57]
............. (idle for 1h2mn)
***zak256 has left [17:01]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)