<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style> fabricius: joined #tikiwiki robertokir: joined #tikiwiki gour: joined #tikiwiki robertokir: Polom! <br> We're upgrading dev.tiki.org right now! <br> The site will be closed for some minutes, please come back later! Thanks! Jyhem: o/ chibaguy: joined #tikiwiki <br> polom jonnyb: joined #tikiwiki <br> polom robertokir: polom! jonnyb: ho robertokir robertokir: hi jonny <br> We actually completed the upgrade of dev.tiki.org, tested, were happy, and opened the site again. Then bang! Error 500 in all *.tiki.org sites. luciash: pompom all jonnyb: pompom luciash luciash: what a bad coincidence... makes us look like suspects ;) robertokir: yes, I actually had the impulse of looking at my hands to see if they were in a different color ;) jonnyb: :P <br> So has anyone got to the apache logs? luciash: yep, nothing obvious there of course <br> 500 errors suck robertokir: I'm trying to, I'm not very familiar with the logs on a ClearOs <br> Are these supposed to be the ones? /var/log/httpd/error_log luciash: I checked /var/log/httpd/error_log jonnyb: more likely in /var/www/etc i think luciash: /var/www/etc? robertokir: no such dir jonnyb: sorry, i didn't mean that as an actual patch, /var/www/something... <br> e.g. /var/www/virtual/dev.tiki.org/logs/dev.tiki.org_error_log luciash: <u>jonnyb</u>: no worries, we do not have the logging working again yet ;) <br> iirc <br> afaik <br> :-p <br> or is it back? Tiki|Log? robertokir: Jonny if you have some time to spare, I'm logged in the server right now, we could do some screensharing; From the last messages in /var/log/httpd/error_log I couldn't come to any conclusion... jonnyb: ok, can do luciash: oh yes! :-o it is back! <br> thanks Jyhem or whoever revived the Tiki|Log! jonnyb: woot woot! :) gour_: joined #tikiwiki xavi_: joined #tikiwiki <br> polom <br> error 500 in themes.t.o jonnyb: pompom xavi_ <br> indeed, they're all down :( xavi_: but thanks to the log of irc.t.o I see that this has been reported already :-) (thanks heaps to whoever helped to resurrect irc.t.o logs :-) ) <br> hi jonnyb jonnyb: yes, nice to have the logs back, thanks whoever fixed it (Jyhem maybe?) fabricius: joined #tikiwiki xavi_: I'm afraid we have a topic to raise somewhere (efficiency vs resilience in the tikiverse infrastructure setup) <br> (almost) all eggs in the same basket means some risks when shit happens <br> whatever shit has happened this time to trigger error 500 chibaguy: nextdev,nextdoc, and nextthemes are also WSOD. Is this a known problem? <br> next.tiki is ok. xavi_: wohoo, some are back (themes.t.o is back) <br> hi chibaguy <br> jonnyb & chibaguy, I'm afraid we need to update instructions about the usage of profile "https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll" <br> current instructions are at: https://profiles.tiki.org/hidable_top_navbar_inst_page <br> and they say "Site layout (in Control Panels > Look and Feel) will be set to Fixed top navbar 1 (uses "top" module zone)" <br> however, I don't see that option in Tiki19 <br> What I see as default there (even after profile has been applied): "Control Panels > Look and Feel > General layout > Site layout: Single container" chibaguy: hi xavi_. Yes, the number of layout templates was reduced in Tiki 19, and the names changed. xavi_: so I presume that we need to clone that profile in profiles.t.o and adapt the new one to the Tiki19 peculiarities chibaguy: That sounds right. xavi_: I can do that, to prepare the work to have the instructions ready to tiki19 by whoever has the knoweldge (not me, currently) <br> chibaguy, I'm setting up a prototype of site for work, using Tiki19. And I wanted to add some theme which uses that parallax effect that you added to some themes <br> is any of those parallax-ready themes in themes.t.o (or zukakakina.*) ready for Tiki19? chibaguy: I need to test it in Tiki 19. It should work the same as far as I know. <br> Also there's PluginLayout for an easier way to remove the side columns and have the page fullwidth, if you need that. xavi_: ah, nice, thanks for the info chibaguy: I'll try to set up a demo page about the parallax scrolling as soon as I can. robertokir: Problem in *.tiki.org solved by Fabio luciash: <u>robertokir</u>: coolio <br> <u>robertokir</u>: what was it? any idea? <br> ;) robertokir: nothing too sensitive to tell here <br> favio restarted FPM luciash: ah, dunno how to do that... good he knows <br> <u>chibaguy</u>: hello! any idea why we have that rule for Chrome browsers which makes the buttons look ugly grey? <br> button, html [type="button"], [type="reset"], [type="submit"] { -webkit-appearance: button; <br> } chibaguy: hi luciash. No idea but I will check into it. luciash: <u>chibaguy</u>: it was also causing the Tiki Project Sites dropdown contrast issue as there was type="button" set in the custom module (I removed it) chibaguy: I'm afraid I usually use Firefox while working on themes and don't check with Chrome much. luciash: <u>chibaguy</u>: me too <br> <u>chibaguy</u>: you can still see it with Chrome on https://doc.tiki.org/ if you want to investigate (code inspect) <br> <u>chibaguy</u>: the buttons should not appear grey but green as in Firefox <br> (Search and Go) <br> but because of this rule they appear as the -webkit browser renders buttons chibaguy: Ok, I'll check. luciash: <u>xavi_</u>: hola! the code for the profile needs to be updated too to match Tiki19/BS4 classes <br> <u>xavi_</u>: I can do that if you prepare the profile for BS4 chibaguy: luciash, there must be other reports of this problem with Chrome. Somehow it should be overridden. fabricius: joined #tikiwiki xavi_: hi luciash <br> thanks, all yours: https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll+19 <br> I attempted to replace the name of the layout to "basic=>social" (an educated guess) but it didn't work :-) <br> all yours (all these is far beyond my skills) :-) <br> s/is/are <br> bbl (lunch) luciash: <u>xavi_</u>: thanks chibaguy: luciash, I removed "type='button'" from the Tiki Project Sites module's dropdown btn, and that fixed the color for Chrome. <br> I guess there's no problem removing that especially for btn-link. luciash: <u>chibaguy</u>: that is what I did on dev and themes too but there are buttons everywhere in Tiki which are affected <br> like the Search and Go button I pointed out <br> on doc <br> for the search module chibaguy: yeah, it's not really the solution. luciash: is it coming from Bootstrap4 actually? <br> this rule chibaguy: I'm not sure. luciash: I see, same here :) <br> btw, I have a fix for the topbar menu dropdowns I think: <br> .dropup, .dropright, .dropdown, .dropleft { position: relative; <br> white-space: nowrap; <br> } <br> what do you think, good enough? <br> I added the white-space: nowrap chibaguy: The rule is in BS4's reboot.scss and there's an explanation: "Correct the inability to style clickable types in iOS and Safari." luciash: <u>chibaguy</u>: eh, that is weird <br> <u>chibaguy</u>: why it resets our colors then? <br> in Chrome chibaguy: (for button, <br> html [type="button"], [type="reset"], <br> [type="submit"] { <br> -webkit-appearance: button;} luciash: (I see iOS and Safari is webkit based too) chibaguy: yeah, I don't know why the color gets reset - I think that's a Chrome browser thing maybe. <br> I need to do some research on that. luciash: could we override it by -webkit-appearance: none ? chibaguy: Maybe. <br> Or inherit? <br> Testing needed. luciash: <u>chibaguy</u>: actually I think these input[type="submit"] buttons are OK, they actually get the background-color defined as #e5d7dc (which is kind of greyish and that confused me it is doing the same weirdness as with the Project sites dropdown one) <br> but there might be other cases for sure chibaguy: Right. luciash: what do you thin about the .dropup, .dropright, .dropdown, .dropleft rule? <br> s/thin/think/ chibaguy: What is that to fix? luciash: the dropdown arrows on dev.tiki.org <br> are wrapped below the menu items in the topbar chibaguy: Oh, right. Well, it shouldn't be necessary to add those classes. The arrows wrap because there isn't enough space for them. If you change the menu's gird div size from col-md-9 to col-md-10, then the arrows don't wrap. <br> Is that the problem you're talking about? luciash: ah, ok, yep <br> bbl, see you in 5 in the meeting ;) jonnyb: joined #tikiwiki fabricius: joined #tikiwiki ricks99: joined #tikiwiki xavi: joined #tikiwiki <br> left #tikiwiki fabricius: joined #tikiwiki xavi: joined #tikiwiki fabricius: joined #tikiwiki xavi: left #tikiwiki fabricius: joined #tikiwiki robertokir: joined #tikiwiki Tiki|bot: joined #tikiwiki <br> Recent Bug: - http://dev.tiki.org/item6900-Can-t-upload-pictures-on-the-tracker5-at-dev-t-o-error-potential-forgery <br> Recent Bug: - http://dev.tiki.org/item6901-Popup-window-over-tracker-item-title-is-really-tight-at-dev-t-o <br> Recent Bug: - http://dev.tiki.org/item6902-19-x-dev-t-o-Top-module-zone-is-no-more-hidable-nor-topbar-module-zone-sticky