hi chealer chealer: about r38898, you removed $tikilib->invalidateModifiedPreferencesCaches(). but this function is still called in lib/core/Connect/Client.php line 29 tikiwiki: 03sampaioprimo * r38900 10/trunk/lib/core/Connect/Client.php: update client code after removal of $tikilib->invalidateModifiedPreferencesCaches() in r38898 chealer: please check r38900 hi all i want to import wordpress sql dump. but when i click on import i get the error: Invalid file mime type any idea whats wrong? i use tikiwiki 8.1 Recent Bug: Tracker item: #4051 - - Crash with blank screen at starting for new users (unknown) visitor with 8.1 - http://dev.tiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=4051 Hi, Marc quite ready to come back. I have a commit for 8.x (see tracker 4051), but I can't log for commit. Because of new installation I have no more the passwords which is not, it seems the same as for login on the site. Thanks to help me Hi, I am quite ready to come back to work on dev. I have today a commit for 8.x (see tracker 4051), but I can't log for commit. Because of new installation I have no more the passwords which is not, it seems the same as for login on the site. Thanks to help me tikiwiki: 03trebly * r38901 10/branches/8.x/lib/setup/user_prefs.php: Track-4051- $prefs are set to null for null user because of not suitable array_merge with a null array $_SESSION['preferences']. A major crash make often the version 8.1 unusable with blank screen No matter, I remember that it is my sourceforge password. Thanks Hi, I commit a minor change into users_prefs.php. You will see as you are the author. please see my coomment in trk4051. I do think that an organization should be exist to prepare during the life of a version some "major-upgrade packages" particularly when such bugs are found on releases. , Hi, without errors : I do think that an organization should exist to prepare when necessary, during the life of a version some "major-upgrade packages" particularly when such bugs are found on released versions. tikiwiki: 03gezzzan * r38902 10/branches/8.x/lang/hu/language.php: [TRA] some additional hungarian translation New Forum Posts: Lingua italiana per tikiwiki - http://tiki.org/tiki-view_forum_thread.php?forumId=8&comments_parentId=42668 tikiwiki: 03pkdille * r38903 10/trunk/lib/ (4 files in 4 dirs): No changes - code styling only (seen on quality.tiki.org) polom Hi, to who knows about : update of database for 8.1. I just upgrade a site which was waiting till 7.x (7.0x) with 245 tables. After upgrade and db update there are still 245 tables. No real upgrade seems have been done. At the same time a site (which was using galeries) was 252 tables with 6.3 then 262 with 7.1, increased to 264 with 8.1... How do you check that the db upgrade have been well done ? is it safe to ask a n00b question here? polom how is everybody? Trying to figure out how to change a wiki page title is oddly fustrating but I'm excited about writing my first report using Structures. Have a good day sir. Past my bedtime again I come back to an old question: when I want in a custom-module different menus according to the actual category I am in, the must be a string like that {$if catId=XYZ}{menu=A}{$elseif catID=ZYX}{menu=B}{$endif} or so is s.th. like that existing and who could be so kind to tell me the right spelling? - next: is that smarty? or what this syntax would be kind of? tikiwiki: 03pkdille * r38904 10/trunk/ (19 files in 5 dirs): No changes - code styling only (seen on quality.tiki.org) marclaporte: available for a sec? polom Trebly: check tiki_schema Trebly: there should be 242 tables in 8.1. 245 shouldn't be a problem Trebly: I don't understand what you mean by "major-upgrade packages", tikiwiki: 03eromneg * r38905 10/branches/8.x/templates/header.tpl: [ENH] automatically assign a unique description meta tag for blogs & blog posts to improve SEO performance Ok, I create a concept without explanation. I mean that we can each of us and as team, and as most of development teams, to publish releases with important bugs that don't concerns a great system they are most of time punctual problems which were appearing (sometime ago with way to develop) during beta with users returns on experiences. The actual rhythm don't allows this anymore. So the solution is to publish what I name "important or critical updates" contained in "major-upgrade packages" as the kbxxxx of MS, generally it is one or a few numbers of programs concerned by one bug. Actually this don't exists for tiki, we publish and after we have upgrades by SVN. In such case the current version has a sub number (often the build for compiled soft). So when you have a "obsolete version" you just have to run the "upgrades packages" generally just unzip and replace files (at first run the pack is recorded and the installation level updated) Sorry it is very long for the chat, but if you agree in the problem and the idea, I will post. Trebly: sorry, I don't understand much of the proposition in particular, I don't understand what "important bugs that don't concerns a great system" means tikiwiki: 03chealer * r38906 10/branches/8.x/tiki-setup_base.php: tikiwiki: [FIX] Session cookie path was one directory too high if the install was not in the document root and accessed without specifying any script (for example as "http://localhost/tiki/"). Hopefully solves #4051. tikiwiki: Note: This would cause abnormal session conflicts which have a bad impact after 7.x (see #4051 for more information). Use $tikiroot instead of miscomputed $cookie_path. This partially reverts r30672. tikiwiki: Review welcome, a regression in this area could be grave. tikiwiki: 03chealer * r38907 10/branches/8.x/lib/setup/user_prefs.php: (log message trimmed) tikiwiki: [REF] Revert r38901. tikiwiki: Note: $_SESSION["preferences"] should never be null for anonymous at this point, tikiwiki: unless there is a session conflict. See #4051 for reference. r38906 should tikiwiki: prevent some abnormal session conflicts. initialize_prefs() has a check for tikiwiki: conflicts in the session preferences cache which no longer does what it used to tikiwiki: in 7.x and was removed in trunk. This check could be reintroduced as a general rehi back to my question I have this now: {if $objectCategoryIds eq "1"}{menu id=42}{elseif $objectCategoryIds eq "2"}{menu id=43}{else}{menu id=44}{/if} and alternatively tried this: {if $categoryId eq '28'}{menu id=42}{elseif $categoryId eq '29'}{menu id=43}{else}{menu id=44}{/if} both does not work - what do I make wrong? hmmm language ... {if $prefs.language eq "en"} works ... but how to mspell the smarty right for category (Id) categories used in templates alright is activated hmmm nobody there to give a hint? Hi :) I'm trying to use HTML in my wiki page, and it keeps stripping the tags... are only certain tags allowed? Hi, are you using the (standart) TikiSyntax editor and the Plugin {HTML()}blabla{HTML} ? Myrkul: do you have Allow HTML checked? i couldn't find that, my edit page looks nothing like the screenshot in the documentation...i guess that's v8? i'm using 7.2... i added it by clicking the html button at the top, then putting my html in the window that pops up tikiwiki: 03gta74 * r38908 10/trunk/lang/de/language.php: [TRA] and again 100 % Myrkul: Allow HTML is there since a long time. are you aware that Tiki 7 is no longer supported? no... {if !empty($objectCategoryIds)}{menu id=42}{else}{menu id=43}{/if} shows me menu 42 on a categorised page and menu 43 on a not categorised page (shouldn't that be opposit around?) it's was the newest stable version linked from the homepage when i installed it a couple weeks ago Myrkul: 7 reached end of life last week. 7.x sites should be upgraded to Tiki 8 sigh last week i was told 8 was still really buggy Myrkul: you should stay with the newest stable version -> frequent updates OR stick with LTS up to the next LTS -> 1 1/2 years circle Myrkul: 8.1 should be OK so far - isn't it chealer? i'll upgrade now then and hope my site doesn't get completely ruined fabricius: well, there are several regressions indeed ( http://tiki.org/ReleaseNotes8.1#Known_Issues ), they could be problematic for some sites ok, well, looks like none of that will affect me :) chealer: do you have some hints for me regarding to the module/menu/category issue? chealer: I want to create a single module with a condition to show different menus in relation to the actual category halfway there {if isset($objectCategoryIds) and in_array(28, $objectCategoryIds)}{menu id=42}{elseif isset($objectCategoryIds) and in_array(29, $objectCategoryIds)}{menu id=43}{else}{menu id=44}{/if} shows me menu 42 in category 28 - that's right but in category 29 and without category - no menu - that's still not what I nees need hmmmpff grrml Sorry, I meant : a default which needs an important review, the tree which was hiding the forest. Sometimes it is impossible without many changes which needs a new version to make something function well. In this case there not other solution than say don't use it, a function unusable or reduced a lot till new version. In other cases, my object, there are only some little updates... ...(in volume and complexity) which makes everything OK, in some cases one instruction creates a dramatic situation that the dev team could not see before the release. I look at the last to cases that I met : the last is in prefs_user.php my last commit, the situation with 8.1 was that a new user was always getting as blank screen... redhibitory situation which lock the use of the whole version and just one php to change for one line... can be the object of a "major-upgrade packages". The other recent example is the treatment of the compilation crash of smarty with elements of syntax of users modules no more acceptable with 8.1. This lock for me a site during 3 month with blank screens before I found that there was a smarty compilation crash. Searching, I gave to Jonny the good warning and he had added quickly a good holding of the exception, but this has been into a... ...release two month later.... Again blank screen and no solution. So to avoid this type of problems, I try to imagine a solution to make the releases working more quickly. Make that "upgrade little package" can solve great problems and have best releases with a best reactivity on redhibitory bugs. note : the SVN is not made for this, even the content covers by part this problem but only for dev. Sorry I don't find a way to be shorter. so it's 8.1 that i want? Myrkul: that depends on what you need/want - hmm I for myself go for 8.1 and pre9 depending on some personal parameters ... but I am mostly working with Daily Builds anyway well, i was just told that 7.2 is not being supported anymore... Myrkul: and I have not so much a problem with frequent but temporary bugs at the moment Myrkul: well, and you do not wanna go with 6.4, I guess ... cannot downgrade a database anyway i'd rather something more recent, yes I will not tell you what you should do - but I would go for 8 and look out for 9 in spring - then you could stay with 9 for a longer period ok for the further development you'd have the opportunity to stay with 9 LTS with the main content and combine it via Intertiki with single sign on with an up to date Daily Build development version, to give your users a view on new features i'd rather not have to update every day, seems updating is a pita like info.tiki.org, doc.tiki.org, dev.tiki.org all are seperate websites, but connected with Intertiki and having the same usermanagement against the community site fabricius: if you replace all that with just {menu id=43} does it work when you're in category 29? this isn't really a huge website network like tiki.org though :P i only have a few dozen pages Myrkul: do you have shell access? Myrkul: I would upgrade to 8.1 indeed yeah chealer: yes it's more or less hosted locally Myrkul: do you know Subversion? nope chealer: I did try different - it works for languages for example, but not yet for categories chealer: the best I could gain is to have the menu in one category and not in the other and not in no category Myrkul: if you find upgrading time-consuming, you could use Subversion checkouts rather than downloading archives each time. it's longer to setup, but very quick for minor upgrades and faster for major upgrades too well, downloading isn't the time-consuming part, that took a couple seconds... but i need to run the installer, then reapply my code changes... chealer: I've setup three testpages on my site: no category: http://fabricius.me/Test-Catmenu_0 category 28: mydomain/Test-Catmenu_28 category 29: mydomain/Test-Catmenu_29 Myrkul: I did mean the whole process, not just the download ah, ok well, is upgrading something that generally needs to be done often? chealer and Myrkul: running a site with svn is kind of cool stuff, but not possible with shared hosting providers wich (mostly?) not provide svn fabricius: add something other than the menus so that it's clear which case is chosen. for example: ah, well, i'm not using a shared hosting provider, so doesn't really apply to me CASE:{if isset($objectCategoryIds) and in_array(28, $objectCategoryIds)}IF{menu id=42}{elseif isset($objectCategoryIds) and in_array(29, $objectCategoryIds)}ELSEIF{menu id=43}{else}ELSE{menu id=44}{/if}ENDCASE Myrkul: if you organise your site(s) and the folders well and you have a decent system to save your files, then an upgrade should not need more than 3/4 of an hour, maybe 20 minutes if you wouldn't be disturbed at all (included all steps) Myrkul: it depends a bit on the branch you run. generally, about every month ok, that's not too bad, i guess ooh, the quick admin module looks actually useful now! chealer: nocat and cat29 show this in the module: CASE:ELSEENDCASE ... cat 28 shows: CASE:IF ...menuitems... ENDCASE chealer: It seems that I am a bit dump or so ... missed to categorise page ...29 so it works when a page is categorised at all but not if it is not categorised hmmm nearly there now (realised my fault, when I switched cat28 and 29 in the smarty code) Myrkul: you should save your tikifiles (file gallery, attachments etc.) neither in the database, nor in the tiki root why not in the database? that doesn't get overwritten? the database gets far too big after a short period of time so if you need safety backups (dumps) or you do upgrades with fresh installations (as recommenase migh bring you into problemsded) and keep the original site able to run instantly - big datab sorry my keyboard messed up I say again so if you need safety backups (dumps) or you do upgrades with fresh installations (as recommended) and keep the original site able to run instantly - big databases might bring you into problems Trebly: we already have minor versions. I think the problem is we don't have many minor releases because the code is not methodically reviewed, Subversion branches are not very tested and it takes time to release each one. well, i'm not too worried about a bit of downtime as i upgrade, and i don't plan on having many attachments anyway saves you pain, if you get in trouble, if you always can reset your domain to the original site and go to bed or to a party with your girlfriend, in case something went wrong let's say, I want to setup a site called A, then I'd always setup a folder /A and in there I unpack my Tiki (for ex. tiki-8.1.zip) that gives me /A/tiki-8.1 tikiwiki: 03chealer * r38909 10/trunk/tiki-setup_base.php: [REF] Oops, forget to clean this up in r38898 well, this is interesting... then in /A i setup folders like /files-filegallery /files-wikiattachements /files-podcasts /files-batchupload and so on i'm reapplying my code changes, and a file that i had changed is no longer there :P nod, makes sense then setting for file galleries: path: ../filesfilegallery mind the double dots - just unix or dos syntax for ONE folderlevel UP instead of staying in the same level once you upgrade your tiki-8.1 to tiki-8.2 or tiki-9.0 your files will not be touched and it is much safer than in the root (in respect of security) if you want to use batchupload you use /A/files-batchupload aka ../files-batchupload you could even give ftp access to this folder and let somebody upload files there - then apply the files in tiki via tick boxes and take them into tiki your db stays small just take as few as possible files into the tikiroot - respectively change things in as few folders of the root as possible mainly styles for your custom theme and maybe some templates and /img/tiki for your logo -> you even can "outsource" your logo yeah, that's all i've changed the few you have to change in the tiki root and the smaller the database, the quicker your upgrades will be tikiwiki: 03eromneg * r38910 10/branches/proposals/6.x/templates/header.tpl: [ENH] [bp38905] automatically assign a unique description meta tag for blogs & blog posts to improve SEO performance I allways take the newest dump of the db, import into a new db, same time unpack the newest tiki.zip, put in the appropriate files (css and such), do my chmod (have a list of abou 10 changes in a textfile) and then I go through the installer I'd say I could save about half the time, if I would manage it to write a small ssh shell script for unpacking and chmodding looks like everything went well :) now lets see if i can get my html page working... I agree, but when for example I commit the little change in prefs_user I solve a great problem. So previously, I was putting in join a zip file to my trackers (2 years ago). It is not the same approach than minor versions, is like kbxxxxxx of microsoft, they are quite independant and if they are thy just check the kb list to remain coherent. while I discuss with you, I imagine a solution : 1- For each upgrade if those I take as example the author creates a zip file with a tracker, but with a ref way for number to record it 2- The zip contains always data (a php file with array) 3- When installer is run it checks the "kb" the upgrades are recorded into a table of the db (so that it can't be executed twice, and new version can be declared include a kb), this maintain coherency. 4- For user into list of files there are the kb files with objects and version to apply no, it's still eating my tags :( 5- This kb never changes the behavior regardless to the defined functions of the version (just can make there are no more buggy) This make easy when a major bug is found to be able to set a kb in a few hours, set a message into a special page of the site with the list of such kb, this too is a 'fatal arm' against regressions. (I use this "kb" because it is the same purpose as MS for systems upgrades, they are often. This would give the feeling and the reality of "reactivity" for all users. We are able to do it. i guess there must just be some tags that aren't allowed? it's not eating the
s :P hehehe :-P Ok Myrkul 1st I try some HTML on my site ... you are sure, that you do not use WYSIWYG? on the wiki page editor, i clicked the html button at the top then inserted my code Trebly: if they are what? and it adds {HTML} tags to the wiki page i'm not too familiar with wiki syntax, but i assume the {HTML} is supposed to make it process html tags :P Myrkul: so is Allow HTML enabled now? yes it was before too, it's a preference apparently :P i was looking for it on the edit page page oh, it's on the page editor too, under properties...yes, it's checked Myrkul: are you editing as admin? no, but i have all permissions... tried as the actual admin account, same problem Myrkul: which tags? form, select and option Myrkul: are you writing actually IN the HTMLplugin? Myrkul: form, select? what you try to achive there? not sure what you mean... a few drop-down menus ok ... hmmm I do not know, if it would be oversised for what you want to achieve, but you know, that there exist the tracker feature? including drop down menus yeah, but i don't want a tracker :P well, actually... do the tracker items need to be inserted into the tiki database, via the tracker? or can i use a tracker as an interface to another database? i was going to write my own wikiplugin to access my database, but if i can use a tracker that's much easier oh, actually, it looks like there's an sql plugin, i can use that instead of writing my own :P but i still need the drop down menus for filtering Myrkul: trackers only work with Tiki's virtual tables nod, that's fine then, i'll use the sql plugin (tiki_trackers and company) I think Myrkul, you'd need s.th. different than trackers, to access an external database yeah, i'm not too worried about that hmm, where are these plugins stored? it looks like i will need to modify it a bit... moment, I'll check http://dev.tiki.org/Hello+World#To_create_a_new_plugin thanks :) chealer: do you maybe know an opposit of" in_array{..." fabricius: " not in array(..." ? so, any ideas about how to add drop down menus on a wiki page? Myrkul: see the HTMLPurifier preference in the Security control panel i don't see that... search didn't turn up anything either... Myrkul: make sure Advanced preferences are not filtered Myrkul: and welcome to Tiki 8... hehe, thanks :) yeah, that would explain why a lot of things seemed to be missing after i upgraded :P it works! :) thanks so much