#foswiki 2013-06-26,Wed

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

WhoWhatWhen
***ChanServ sets mode: +o pharvey [05:03]
........... (idle for 51mn)
ChanServ sets mode: +o CDot [05:54]
................................................ (idle for 3h56mn)
foswiki_irc4Hi there, Martin writing! I would like to upgrade an ole twiki 4.3.2 Georgetown to foswiki. Officially upgrade is only supported till 4.2.3. Will there be any Problems? We do not use any addons. [09:50]
.... (idle for 15mn)
CDotfoswiki_irc4: probably not. The rate of code change in twiki is glacial, and I believe foswiki supports pretty much everything. There's even a compatibility plugin. [10:05]
...... (idle for 28mn)
foswiki_irc6@cdot: Thank you. Regards Martin [10:33]
......... (idle for 40mn)
***ChanServ sets mode: +o MartinCleaver [11:13]
.............. (idle for 1h6mn)
fulekiaAnybody know what this means? Version string 'HEAD' contains invalid data; ignoring: 'HEAD' at /var/www/foswiki/lib/Foswiki/Configure/UIs/EXTENSIONS.pm line 283, <DATA> line 522.
Just disabled a plugin, and now configure is borked.
[12:19]
***ChanServ sets mode: +o gac410 [12:20]
gac410fulekia: What version of Foswiki are you running?
There is a patch for that issue.
Foswiki:Extensions.PatchFoswikiContrib has the fix. But with configure messed up you'll have to manually patch a couple of files.
[12:22]
FoswikiBothttp://foswiki.org/Extensions.PatchFoswikiContrib [ PatchFoswikiContrib ] [12:24]
.... (idle for 18mn)
fulekiagac410: thanks.
I'm still on 1.1.4, so I guess I need that patch.
[12:42]
gac410yes, It's pretty simple. Basically change 'HEAD' to '9999.99_999' in lib/Foswiki/Configure/UIs/EXTENSIONS.pm and lib/Foswiki/Configure/Dependency.pm [12:44]
fulekiagac410: thanks. I'll vim that up and see if configure comes back to life. [12:44]
gac410we used to use the string 'HEAD' to mean the user was running from SVN checkout. But perl version checks choke on that. So we use an impossibly high version number now. [12:45]
fulekiaAh, makes sense. [12:46]
gac410What extension did you install that triggered the issue? [12:46]
fulekiaI'm installing new plugins on a FW1.1.4 install, so I must have introduced the breakage somewhere.
I disabled MetaCommentPlugin
[12:46]
gac410Did you use configure to install the extensions or manually. If the plugin was built correctly, it should have automatically installed PatchFoswikiContrib and avoided the issue. [12:47]
fulekiaThen configure died,
Installed through the interface.
I may have to big Micha to see if PatchContrib needs to be added as a dep
s/big/bug/g
[12:47]
gac410hm. yeah, it should be a dep if the extension is using the new version strings. [12:48]
fulekiagac410: yay - configure is alive! [12:50]
gac410There are some other urgent patches for 1.1.4 [12:51]
fulekiaI'll install PatchContrib on my production system before I go any farther.
I suppose I should upgrade, then.
:-)
I've been hoping 1.2.0 would drop soon...
gac410: Should I install those patch extensions in the meantime?
[12:51]
gac410PatchItem12285Contrib patches a critical security bug [12:53]
FoswikiBothttp://foswiki.org/Tasks/Item12285 [ Item12285: Resolve MAKETEXT vulnerabilities CVE-2012-6329 and CVE-2012-6330. ] [12:53]
fulekiaDo I need PatchItem12391Contrib as well? Does that supersede PatchItem12285Contrib? [12:56]
FoswikiBothttp://foswiki.org/Tasks/Item12391 [ Item12391: Fix for [[Support.SecurityAlert-CVE-2013-1666]] ] [12:56]
.... (idle for 18mn)
jast1.2.0 will *not* drop soon
(I'm not the release manager, so that's not an official statement, but it's fairly obvious given that there are some majorly broken things in trunk)
[13:14]
....... (idle for 34mn)
MichaelDaumjast, what's broken on trunk?
besides configure
[13:48]
***ChanServ sets mode: +o MartinCleaver [13:49]
MichaelDaummaybe we need a good old release meeting
gac410, what do you think?
[13:51]
.... (idle for 18mn)
jastMichaelDaum: just configure :) [14:11]
............ (idle for 59mn)
gac410MichaelDaum: yeah probably. I don't know how to resolve configure. There is an awful lot of baby, but quite a bit of bathwater too :)
I have one stashed patch from Timothe from back in Jan, that implements the log viewer using the Logger nextEvent API.
[15:10]
MichaelDaumgac410, how about we pull together some people using an email invitation and discuss this all together, including a review of other release blockers. [15:11]
gac410But it is waiting on my fixing up the Logger API, which I've been sitting on. I think Sven's idea of basing off of 1.1.x and pulling select work from trunk might be better.
I'll do my best but I'm still very tied up with real life stuff. Hopefully schedule will open up in August.
[15:11]
MichaelDaumif we have an official release meeting here on irc, we can make these decisions stick. [15:12]
gac410yeah. We are somewhat paralyzed right now. [15:13]
MichaelDaumotherwise it is just lalaland. [15:13]
PsychoTraheis it possible to have META:TOPICPARENT set to a URLPARAM? [15:14]
MichaelDaumI am in the middle of renovating my flat from ground up as well (moved out temporarily). still I try to get stuff done.
gac410, would you like to create an invitation on the mailing list, maybe a doodle with proposed dates?
PsychoTrahe, what exactly are you trying to achieve?
(1) reparent a topic or (2) display a different value in the breadcrumbs while viewing a wiki page?
[15:14]
PsychoTrahe2)
:-)
[15:16]
MichaelDaumokay, so you don't necessarily need to _store_ the value. it is just to display the urlparam sometimes [15:17]
CDotMichaelDaum: AFAIK the validation tests are broken, and one additional test that I added
jast: what do you base that statement on?
(14:57:18) jast: (I'm not the release manager, so that's not an official statement, but it's fairly obvious given that there are some majorly broken things in trunk)
such as?
[15:18]
.... (idle for 15mn)
PsychoTraheMichaelDaum, you mean by having a different view template
?
[15:34]
MichaelDaumyes [15:34]
gac410MichaelDaum: yes indeed I try to get some stuff done, but I'm avoiding the "big commitments". ie building another release. I really need to get 1.1.9 going too, which I think is more urgent. [15:36]
MichaelDaumagreed. at least this fruit hangs a tad lower [15:37]
CDotCDot is still struggling to understand why people have such a downer on 1.2.0 AFAICT most of the "urgent" reports outstanding are Sven's aides memoire [15:40]
MichaelDaumthere are bits on trunk that didn't went well: SlideShow, Configure, PatternSkin, WikiGroups, the WikiApps feature Sven was trying to build ...
some cases might need a revert. some might be okay in the state they are atm
[15:45]
fulekiaMaybe pick an older branch point for 1.2.x, then merge back in any good stuff?
fulekia just tossing in $.02
[15:47]
gac410I think the choice is either 1.1.x or trunk. The trunk changes are all interwoven and have been very extensive. We waited too long to branch IMHO [15:48]
MichaelDaumthe TablePlugin fixes alone are worth a quick 1.1.x [15:48]
gac410All $.xx welcomed :)
I think 1.1.9 is in very good shape.
[15:48]
MichaelDaumbasically, I am fine with a 1.1.9 as long as branch 1.2.0 soon from trunk. [15:50]
fulekiagac410: like maybe this summer stilll?
for 1.1.9, i mean.
[15:50]
pharveyboo [15:50]
MichaelDaum1.2.0 will be an important step wrt performance [15:51]
gac410fulekia: I hope, yes. I'll probably start the process in August, assuming nothing else changes in RL [15:52]
pharveyto nobody in particular, I'm still overloaded with this bothersome madness called life, but I am telling myself I will contribute to trunk/1.2/WYSIWYG stuff at some point after July
there was a HN article saying javascript is the assembly language of the web
and given the mess I currently find myself, perhaps that is an apt comparison
[15:54]
gac410Item12448 is annoying, I've been unable to find a combination of stickybits to get tables with unsupported attrributes (via styles) to survive TML roundtrip [15:59]
FoswikiBothttp://foswiki.org/Tasks/Item12448 [ Item12448: WYSIWYG-Editor: Table Cell Background Color lost on save ] [15:59]
gac410We probably need some stickybit code to disect the style settings instead of just looking for html attributes. [16:00]
MichaelDaum... or disable coloring table cells in the ui
... or make it an html table
TML tables simply arent able to store cell colors
[16:00]
gac410y, although that would probably annoy some folks. I don't know TMCE well enough to do that.
Right. But if someone wants colors, Wysiwyg *used* to skip the conversion to TML. Now it doesn't
[16:02]
MichaelDaumit is the same folks that add lots of %BR% all over the place and love comic sans [16:03]
gac410Well, I've used table cell backgrounds on occasion, to highlight critical information, missed dates, etc. [16:04]
MichaelDaumwysiwyg adds lots of spans with font settings all over the place, I don't know why. [16:04]
gac410Hopefully we nuke all them still [16:04]
MichaelDaumso the editor switched to html tables once people added cell colors? [16:05]
gac410Yes [16:05]
MichaelDaumah ok
then we need to find a way to restore this behavior
[16:05]
gac410Well, the save just didn't convert to TML. Stickybits setting matches html attributes that should cause the conversion to be skipped. [16:06]
MichaelDaumgotcha [16:06]
gac410But color moved from HTML to Style, and that ended that.
There are probably a bunch of deprecated html attributes that need to be picked up when in styles. It needs a general review.
[16:06]
MichaelDaumdoesnt tinymce generate proper html5?
btw I've seen tinymce as customized in jive...awesom
[16:07]
gac410I think so. And the old html atriibutes bgcolor= for ex, is deprecated for style="background-color:" [16:08]
MichaelDaumaline="..." -> style="text-align:..." [16:09]
gac410exactly
http://foswiki.org/Extensions/WysiwygPlugin#WYSIWYGPLUGIN_STICKYBITS_45_Protect_tags_based_upon_their_arguments has not kept up with html changes
[16:09]
pharveyCDot: UnitTestContrib is still awesome :(
Test:::More, Test::Class, Test::Class::Moose seem over-hyped.
[16:20]
foswiki_irc2Howdy - I can not for the life of me figure out how to do LDAP groups in foswiki. My understanding of ldap groups being a limiting factor. I have however gotten apache to work using LDAP groups. Couod somebody help me translate that into foswiki config - or does it not work that way ?
AuthBasicProvider ldap AuthzLDAPAuthoritative On AuthLDAPURL ldap://161.195.161.93:389/ou=users,ou=usa,ou=noram,dc=fss,dc=pylkie,dc=com?userPrincipalName?sub?(objectClass=person) AuthLDAPGroupAttributeIsDN on Require ldap-group CN=UNIX_G,OU=Users,OU=USA,OU=NORAM,DC=fss,DC=pylkie,DC=com AuthLDAPBindDN "cn=svc_apacheldap,cn=Users,dc=fss,dc=pylkie,dc=COM" AuthLDAPBindPassword
AuthType Basic AuthName "Authorization required" AuthzLDAPLogLevel debug
[16:31]
gac410foswiki_irc2: have patience, I think there are some LDAP folks around today. Not me though :) [16:46]
foswiki_irc2I have some good info there - I life in hope ! And if the broweser/connection breaks I will have to find the logs . [16:54]
..... (idle for 20mn)
fulekiafoswiki_irc2: I'm off to another meeting. If I'm not around to help, please use the mailing list. [17:14]
....... (idle for 32mn)
***ChanServ sets mode: +o MartinCleaver [17:46]
........................................... (idle for 3h30mn)
ChanServ sets mode: +o MartinCleaver [21:16]

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