Tiki-KGB: [FIX] webservices: Store and index tracker webservice fields properly when using an "index" type of service (as set up on tiki-admin_webservices) which allows formatting and filtering of data from the response object.
03jonnybradley r62321 10trunk/lib/core/Tracker/Field/WebService.php 10trunk/lib/pdflib.php 10trunk/lib/core/Search/ContentSource/WebserviceSource.php 10trunk * [MRG] Automatic merge, branches/17.x 62316 to 62320
03luciash r62322 10branches/17.x/lib/prefs/feature.php
[ENH] User messages: add missing description to the feature checkbox with a hint to admins that tiki_p_messages permission is required for new Registered users (thanks marclaporte)
03montefuscolo r62323 10trunk/ 10(6 files in 5 dirs) * [ENH] Use tablesorter plugin from maintained repository on packagist.
03patrick-proulx r62324 10trunk/lib/wiki-plugins/wikiplugin_img.php * [ENH] Added functionality to the IMG wikiplugin to allow for responsive images
03montefuscolo r62325 10branches/17.x/templates/comment-header.tpl * [fp/r62044][ENH] forum: Add anchor links to forum headings.
03rjsmelo r62326 10branches/17.x/tiki-check.php * [FIX] Fix warning when tiki-check is run as standalone
03rjsmelo r62327 10branches/16.x/tiki-check.php * [ENH] Backport tiki-check.php to all supported versions
03rjsmelo r62328 10branches/15.x/tiki-check.php * [ENH] Backport tiki-check.php to all supported versions
03rjsmelo r62329 10branches/12.x/tiki-check.php * [ENH] Backport tiki-check.php to all supported versions amette__: left #tikiwiki
joined #tikiwiki
left #tikiwiki nelsonko: joined #tikiwiki
left #tikiwiki redflo: joined #tikiwiki fabricius: joined #tikiwiki ironwarning: joined #tikiwiki
Hey all is MyISAM or innoDB better to use Padlock: joined #tikiwiki
Polom everyone ! jonnyb: joined #tikiwiki Padlock: So, one of my colleagues produces documentation in word that uses the "math equations" tool in word. So his docs are chockful of math stuff. Is there a way to transfer that into the tiki as is ? or will i have to screenshoot all these equations ? RadoS: joined #tikiwiki jonnyb: polom polom Padlock: polom jonnyb ! jonnyb: hi Padlock
re the maths stuff, someone once added latex to tiki, i never got it to work and no idea if it still works but tht's does mathematical things i think luciash: polom pom pom pom jonnyb: hi luciash luciash: hi jonnyb and Padlock
hi ironwarning ironwarning: hello luciash: ironwarning: i prefer innodb as it never crashes my tables ironwarning: just having some many issues upgrading luciash: i had lot of trouble with myisam in the past Padlock: hi luciash Caarrie: joined #tikiwiki luciash: innodb is heavier on resources (disk usage) though afaik ironwarning: I just get it moaning it cand find stguff in indexs etc Padlock: I'm just reading that jonnyb... So i just need to install Latex ? lol
there's not much info on this. Doc.tiki.com points to a "mods formula" and the link doesn't seem to work
is the mods.tiki.org site still up ? jonnyb: as i said Padlock, it's pretty old Padlock: I don't mind old, as long as it still kinda works lol luciash: hmm, marc wanted to take it down... is it down already? Padlock: it looks down Caarrie: joined #tikiwiki Padlock: Or there's mathjax ? i'll try that luciash: Padlock: yep, there might be some JS solution too Padlock: luciash: thanks. I trie everything that's described here https://doc.tiki.org/MathJax. So i pasted the mathjax script bit in the custom head content
I can actually see the script's called in the header of my page now
and I copy-pasted bits of equation from the doc.tiki.com page into my own wiki page to check if script works, but it doesn't seem to :/
Did i do something wrong ? could someone try that in one of their own wiki pages ?
Oh i found the reason ! the script snippet was not up to date, I got a new one from the mathjax website and it works :-) jonnyb: looks like we've had another spam flood on tiki.org - did someone clean it up already? (400+ forum posts) amette__: joined #tikiwiki jonnyb: hi amette_ Bsfez: joined #tikiwiki ironwarning: guys im at a massive road block in upgrading the ysstem i
When searching i get Parsing search query failed: "Field wiki_content does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_wiki_content."
when i go to control panel IndexMissingException[[tiki_pref_en] missing] for index /tiki_pref_en jonnyb: hi ironwarning - have you rebuilt your admin index? ironwarning: index:rebuild ? jonnyb: which version are you on? in the old days you eneded to do it separately
on the little filter menu on the admin pages ironwarning: anything yo to and including 15.3 is fine
just get errors in control panel IndexMissingException[[tiki_pref_en] missing] for index /tiki_pref_en
15.4 and above i get "Field wiki_content does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_wiki_content." jonnyb: yes, that's an annoying new feature added to try and help people work out how to use the list plugin, was a bad iadea imho ironwarning: it stops the search running jonnyb: so did you do "Rebuild Admin IOndex"? ironwarning: php console.php database:update and php console.php index:rebuild jonnyb: it will take you to?: tiki-admin.php?prefrebuild
no
on the little filter menu on the admin pages ironwarning: page wont load jonnyb: how do you mean ironwarning? A white page, or an error? Or just taking a long time? ironwarning: page cannot be displayed
This is in the test enviorment however the live just returns me to the admin panel jonnyb: which search index type are you using? ironwarning: elastic jonnyb: and the other index works ok (usually called tiki_main)
? ironwarning: ok im gonna sound stupid
do you mean what search engine? jonnyb: yes, i mean "unified search engine" pref, elastic, mysql or lucene
tiki uses two indexes, one for the prefs called tiki_pref_en (or whatever other language) and a tiki_main one for all the wiki pages etc
it sounds like you need to rebuild the prefs one ironwarning: The main was set to eleastic i will just set it to another and find out jonnyb: thewy will both use the same engine ironwarning: i have rebuilt it no change chibaguy: joined #tikiwiki
polom jonnyb: polom chibaguy ironwarning: Im completly lost jonnyb: ironwarning: what is your "Elasticsearch index prefix" pref set to, i presume it's the default tiki_ ? chibaguy: Hi jonnyb and all ironwarning: yep jonnyb: can you get to your elastic search in a browser?
oh, what version elastic search are you on?
it will say at http://localhost:9200/ if you can see that ironwarning: {
"status" : 200,
"name" : "Heimdall",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "1.7.2",
"build_hash" : "e43676b1385b8125d647f593f7202acbd816e8ec",
"build_timestamp" : "2015-09-14T09:49:53Z",
"build_snapshot" : false,
"lucene_version" : "4.10.4"
},
"tagline" : "You Know, for Search" jonnyb: ok, quite old but should still be supported (we're having trouble with es v5) ironwarning: i did try to upgrade to latest but had to roll back jonnyb: what does this say? (a summary will do, or pastebin etc) http://localhost:9200/_alias/?pretty
for me i have tiki17_pref_en and tiki17_pref_en-uk as well as a few _main ones ironwarning: gives loads of lines
should that be in the list?
its in there jonnyb: but it still says "IndexMissingException[[tiki_pref_en] missing]"
weird, if it's not missing... ironwarning: yep in the controlpanel and the other errors while searching
the pref error doesnt really stop it working its the Field wiki_content does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_wiki_content. that is stoppign the search working is the show stopper jonnyb: hmm, do you have any wiki pages?
and where exactly does the "Field wiki_content does not exist" error appear? ironwarning: over 1200
tiki-searchindex.php - If you just press search it shows all pages but when you enter test in the search field its shows the error above in red box - 'Parsing search query failed: "Field wiki_content does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_wiki_content."'
-- this is using elastic search jonnyb: can you upgrade to elastic search v2.x? (2.4 i think was tha last) ironwarning: I can give it a go jonnyb: the only thing i can think of i'm afraid, i don't have any es 1.x installs around to test on anymore amette__: left #tikiwiki ironwarning: ok willsort the upgrade and come back to you jonnyb: sorry about that, it should "just work" :) Padlock: joined #tikiwiki
guys, there's something wrong with my tiki :(
When I try to display a structure it says : Invalid compiled template for '/var/www/html/tiki/templates/structures_toc-startul.tpl'
Oh. Clearing cache solved it. Sorry wrong alert ! chibaguy_: joined #tikiwiki fabricius: joined #tikiwiki amette__: joined #tikiwiki Tiki|bot: Recent Bug: - http://dev.tiki.org/item6328 amette__: left #tikiwiki
joined #tikiwiki
polom jonnyb: pompom amette__ amette__: heyho jonnyb jonnyb: been meaning to do a mail to devs about nextdoc (and check if those dev pages were gone) but still wading through bugs (and spam) - you had a look yet? amette__: more harddisk fun last night at elastichosts. and of course we were again affected. no data loss though as it seems.
I start to wonder, if that happens more often at theirs and we just had bad luck to have been affected that hard and twice. *sigh* jonnyb: really, that sounds really bad amette__: Yeah, I haven't yet... I first realised that the encoding issue happens before the elastic-resuce, so your script seems to be fine in this respect.
Then I did the import, but that took quite long and then I forgot about it last night. But yes, it was only fivehundredsomething. jonnyb: once doc is back online again we need to do some sort of investigation, i can't believe they are that unreliable (and still in business)
504 is good :) amette__: yeah, I guess we just were unlucky. We had the rotting file system and then the virtualised hardware fail, that's a bad combo. jonnyb: ah, the encoding thing you mean the modules that aren't happy? amette__: yep, that one jonnyb: good (but also bad ;) ) amette__: but I really was a bit in disbelief, when I received the e-mail about having had hdd problems again - first I thought they wanted to inquire about how our disaster went, but no, it was another one.
this time they said something about malicious intent though, well, never mind, waste of time, let's focus on getting this straightened out again! luciash: :-o amette__: heya bro! nelsonko: joined #tikiwiki jonnyb: polom nelsonko luciash: wow, did you know page/with/slashes is possible in Tiki? jonnyb: :O luciash: https://demo.luciash.eu/tikitrunk/page/with/slashes amette__: luciash : yes, I noticed that two weeks ago when discussing with a client... but she said she doesn't always manage to create a page with slashes... haven't figured out yet, when it fails and when not.
I'm actually wondering, if that is a bug or a feature. luciash: see my link ;)
I would say a feature ;)
there is just notice while creating the page it might not be good idea but it works! amette__: yeah, I can't really see any disadvantage to it... but somehow it feels weird, because a slash has a special meaning in a URL... so who knows how this will come back in the future to bite you ;)
ah, see... the dude implementing it thought the same :P
LOL : wiki_badchar_prevent <- says all! *GG* jonnyb: i've been using rewite ruiles with slashes in for a while now on some sites, i guess you cold restrict page names to not have slashes in if you wanted to?
you need the base href pref enabled too, right? amette__: feature_html_head_base_tag according to luciash demo page luciash: yes, as i wrote on the page amette__: luciash : can you have a look at nextdoc.tiki.org please, if the dev.t.o pages you found there are gone now? luciash: amette__: sure amette__: cool, thanks Jyhem: polom
luciash: nice! -: Jyhem can't figure out if it's good or bad, but definitely interesting :) jonnyb: hi Jyhem Jyhem: hi jonnyb, hi amette__ amette__: heya Jyhem luciash: amette__: looks good to me
Jyhem: even the wiki links seem to work correctly amette__: Well, there is nothing preventing it from working... luciash: i would maybe limit it to the slash character (new pref) amette__: ... but create a wiki page named /templates_c/myPage luciash: yes, i will test
if it prefers the real path or links to the wiki page amette__: one is totally broken and the other will save new wiki pages into oblivion luciash: but one needs to count with that while creating the wiki pages names that some paths are Tiki reserved so they will not work probably - can rename the page if that happens anyway kotten: joined #tikiwiki amette__: so there should be a test, if the wiki page name clashes with a directory... but then again people can add directories after the wiki page... so either way it is dangerous
sounds like something that should be optional depending on being admin or not ;) luciash: yup yup, but... it is already optional :D
nobody knows about it! :D
amette__: heheh, it still works just fine! :-p amette__: luciash : ok, then do it with some proper static content, like img/ luciash: https://demo.luciash.eu/tikitrunk/templates_c/this_should_fail
amette__: that shows the image, right :) amette__: well, yes, use a full image path luciash: well, enough testing for me, try it yourself :D amette__: as soon as I have a finger free -: chibaguy_ thinks page names with slashes is somehow unnatural, if not evil ;-) chibaguy_: www.example.com/unnatural and/or evil amette__: *g*
hi chibaguy_ :) chibaguy_: hi amette__ (and all) luciash: *g*
the purpose is to address same feature urls Wordpress or Drupal has
https://dev.tiki.org/wish4947 and simmilar
hi chibaguy :) amette__: There surely was a reason why we didn't use slash as a workspace seperator..!? chibaguy_: hi luciash luciash: yes, but that could work too i think when the base tag is enabled
amette__: ^
amette__: as you can define your own one
or namespace rather? amette__: default one, I mean luciash: yup
i bet the reason was that the base tag preference is not enabled by default amette__: hmmm... what would be so bad about enabling it by default? montefuscolo: joined #tikiwiki amette__: hi montefuscolo :)
Nope, haven't found time for Docker yet. How's Rancher? Giving new possibilities? luciash: amette__: yep, i think it should not hurt... hmm tchiwam_: joined #tikiwiki amette__: I wasn't really involved in that namespace-seperator discussion, but I gathered that it was pure comedy gold. And the result proves it, a totally butt-ugly design-by-committee weirdness in the middle of a URL. Anyway... there was lots of discussion on the devel-list, why different things don't work. And I'm sure someone brought up, why a slash can't work... and I guess that this will be the best reason for why a slash is a bad idea in a page name. The
e was lots of brainpower on that discussion... would be a pity, if it is all lost in the deepness of the devel-list.. a wiki page with the reasoning would be good. Would help us in this situation right now, too. luciash: Agreed, there must be reason... I am just guessing. jonnyb: bbl
joined #tikiwiki luciash: amette__: btw, namespaces work with the / here too when defined amette__: yes, I know
that wasn't the point luciash: ok ironwarning: getting issues woth eleastic now patrickproulx: joined #tikiwiki amette__: left #tikiwiki kotten: PluginSQL --on my tikis db -- would give me the syntax to manually populate the tiki?
Like wiki pages and trackers
"manually" parse info and throw it in to the tiki. I guess files and stuff would work differently but this should work or is it "a big no-no"?
for just pure data, text and items Jyhem: kotten: Not quite sure about what you are attempting, but I guess you could start creating a page, then you dump the database with option --skip-extended-insert
then you save the page and you dump again with option --skip-extended-insert and you can do a diff of both dumps to get an idea of how to populate a page amette__: joined #tikiwiki Jyhem: Just ignore everything in the index table: this one is rebuilt with php console.php index:rebuild
example dump command: kotten: Jyhem some convenient way to autopopulate the wiki and trackers with data. F.e. "found new item -> push it into the wiki" and also possibly to manually do some kind of ugly import of a mediawiki Jyhem: mysqldump -u "dbusername" --password="dbpassword" -Qqf --skip-extended-insert "dbname" > dump01.sql kotten: Jyhem yeah but I was hoping to use this plugin...
https://doc.tiki.org/PluginSQL#Plugin_SQL
but well.. no.. I don't really need that one
There are some place/setting I should be able to set to see all the sql queries the tiki does Jyhem: I don't know about this plugin. I prefer command line :) kotten: Jyhem amen on that :)
I know about dump
But I want to find out what INSERT statements are done by tiki when it creates a tracker item or a wiki page
So that I can do that myself using automated tool when something show up
*shows up
Jyhem you get what I am after? Jyhem: Yes. I feel the diff from both dumps will give you the syntax
option --skip-extended-insert is for having one INSERT per line. This way you get the new inserts kotten: Jyhem yeah very true but I am fairly sure there are some debug option to store queries and insert statements. It will probably clarify more to me if I am messing around
<Jyhem> Havn't done a mysqldump in a long time (atleast looking at the content) but so --skip-extended-insert will more make it 'one insert statement per thingy' instead of like some unreadable bulk of data per table?
I was looking for something like this: https://doc.tiki.org/Programmer
"like Log SQL" parameter
But I am unable to locate(just doing search in control panel view - and rebuilding it's index) neither "Log SQL" or "Programmer"
aha now it's called Include Smarty notices Jyhem: sorry, need to leave kotten: Jyhem nice talking to you take care Telesight: joined #tikiwiki kotten: Okay so I have gotten all the data that I was currently looking for but there is just one field I am worried about in the tiki_pages: page_size ironwarning: joined #tikiwiki kotten: Data of the wiki is "wc" to 69 charachters and the page_size = 68
What really is it? and does it matter if it is wrong
I've been trying to compare to my other tiki_pages but it is d*mn hard to mark and compare fabricius: joined #tikiwiki jonnyb: joined #tikiwiki patrickproulx: joined #tikiwiki kotten: The pagesize doesn't seem to matter(it goes well with clearly wrong values in it
Thanks Jyhem for before btw patrickproulx: joined #tikiwiki ironwarning: joined #tikiwiki nelsonko: joined #tikiwiki amette__: left #tikiwiki