<!-- 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>
Bsfez: joined #tikiwiki
luciash: <u>leagris</u>: thx. is it still valid when you send non-utf8 mail ? (latin1)
<br> grmbl, there is no lib/webmail/htmlMimeMail.php in trunk anymore :(
<br> <u>leagris</u>: now i read this in lib/ziplib.php line 792:
<br> * Only "7bit", "quoted-printable", and "base64" are universally safe * for transport via e-mail. (Though many MTAs can/will be configured to * automatically convert encodings to a safe type if they receive * mail encoded in '8bit' and/or 'binary' encodings.
<br> <u>leagris</u>: it seems to say exactly the opposite what you have said :)
arildb_: joined #tikiwiki
-: luciash wonders if base64 would be a safer choice
goj: joined #tikiwiki
arildb_: joined #tikiwiki
refizul: <u>luciash</u>: email separates between header encoding and body encoding
<br> header must me universal, so there are only three options
luciash: <u>refizul</u>: which ones
refizul: the body is almost a binary for transport, and it's meaning is written into the header by the encoding
<br> <u>luciash</u>: the three ones above, you mentioned them
luciash: so the suggestion by leagris to use 8bit instead of 7bit is wrong ?
refizul: does it refer to header?
luciash: yes
refizul: you cannot use German Umlauts and other special stuff directly encoded inside the header by a byte or two bytes UTF-8
<br> inside name and subject is has to be recoded qp or b64
<br> inside name and subject and any header is has to be recoded qp or b64
luciash: that's what i thought, base64
refizul: if you mess this up, you're in an undefined situation
<br> some MTAs can exchange mails despite, some not
Tiki|Log: joined #tikiwiki
Topic: for #tikiwikiis now Tiki Wiki CMS Groupware - the only Free Web App with the most built-in features & the most open Open Source software community! Tiki 11.0 (Vega), 10.4, 9.6 & 6.12 LTS is out! Question? Just ask! We log the channel @ http://irc.tiki.org (start line with [off] to exclude message from log)
Tiki-KGB: joined #tikiwiki
Tiki|bot: New Forum Posts: Renaming categories (problem and workaround) - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48105
Tiki-KGB: joined #tikiwiki
refizul: Which permission does a user need to see "Tracker" in the left menu?
dcedilotte: joined #tikiwiki
fabricius: tiki_p_view_trackersomething_inmodule?
goj_killedByISP: joined #tikiwiki
refizul: tiki_p_list_trackers
chibaguy: joined #tikiwiki
leagris: ssorry to fix your wrongness refizul
<br> Mail header encoding is a very different topic
<br> Mail header encoding of utf-8 requires what is named Q or B coding
<br> What I patched/proposed is concerning the content transported bits defined by mime header Content-Transfer-Encoding
<br> This defines how the content payload of a MIME part has to be handled in reguard to transport (IE MTAs and MDA)
<br> That is, I was talsking about MIME Payload and not MIME headers whic is a totally distinct topic with its own issues
<br> So, within actual versions of TIkiwiki webmail mime object constructor. The default of 7bit encoding is improper and unsuitable for anything other than either
<br> Quoted printable encoded charset
<br> Or plain 7bit ASCII
<br> The default mime object setup for HTML part is already Quoted Printable, so, a 7bit Content-Transfer-Encoding is ok
<br> The default mime object setup for text/plain part is currently bugged to 7bit and plain iso-8859-1 or utf-8 charsets which are 8bits charsets
<br> You can not use a 7bit Content-Transfer-Encoding for iso-8859-1 or utf-8, you need to Quote Print and declaire use Content-Transfer-Encoding: quoted-printable, (for purposedly QP encoded content) or Declare Content-Transfer-Encoding: 8bit if content is not encoded.
<br> Actually no [01:03] <@luciash> that's what i thought, base64
<br> or not precisely
<br> Mail headers use Q coding (equivallent of Quoted Printable) and B coding (equivallent of BASE64)
<br> Well, if you need to grasp this. There a the MIME RFCs and some good articles on wikipedia :)
<br> I whiches you all a good night.
chibaguy: joined #tikiwiki
arildb_: joined #tikiwiki
fabricius: joined #tikiwiki
nkoth|nelson: joined #tikiwiki
Tiki|bot: Recent Bug: - lpad password will not be accepted when using > or - http://dev.tiki.org/item4597
<br> Recent Bug: - lpad password will not be accepted when using > or - http://dev.tiki.org/item4598
<br> Recent Bug: - lpad password will not be accepted when using > or - http://dev.tiki.org/item4599
arildb__: joined #tikiwiki
arildb: joined #tikiwiki
arildb_: joined #tikiwiki
redflo: joined #tikiwiki
SkiNut: joined #tikiwiki
Bsfez: joined #tikiwiki
<br> polom
SkiNut: joined #tikiwiki
luciash: hi Bsfez
<br> <u>leagris</u>: thx for the information. so you say your fix is 100% correct ? ;) i can commit it then but will need fix for branches/11.x or trunk as the lib has changed there
rodrigoprimo: joined #tikiwiki
jonnyb: joined #tikiwiki
<br> polom
refizul: I've got a tracker with url field, and I try to get an url with comma into it. But this works like a separator and url breaks, and HTMML entity &#44; doesn't work either. What do I have to do?
<br> Is there a special escape mechanism?
Tiki-KGB: tikiwiki 03jonnybradley r46721 10branches/11.x/lib/wiki-plugins/wikiplugin_tracker.php
<br> tikiwiki [FIX] tracker plugin: Setting an empty value for fields now prevents the defaults being used, so don't do this for dropdowns with duplicated options which are used as defaults.
<br> tikiwiki Leave other field types alone in case this is still needed for "prefilling" values.
Tiki|bot: joined #tikiwiki
luciash: <u>refizul</u>: use URL escape
<br> %XX
<br> hi jonnyb !
jonnyb: hi luciash - how goes?
luciash: goes well
<br> :)
jonnyb: :)
luciash: just grabbed brances/11.x
<br> *branches
<br> need to dig the composer commands now somewhere, right ?
-: luciash missing the old good helpful bots here ;)
ricks99: joined #tikiwiki
-: luciash wonders the composer info is not at SVNTips
luciash: nor on DevTips
<br> nor on TikiDevNewbie
<br> ah, Composer
-: luciash srughs
luciash: ok, sh ./setup.sh
MagicFab_: joined #tikiwiki
refizul: <u>luciash</u>: thx, that worked (after converting dec2hex several times wrong in my head, haha)
luciash: fu*k the symfony
<br> "Your requirements could not be resolved to an installable set of packages."
-: luciash remembers the old times when setting up Tiki was easy
refizul: the easiest way is to give an order to someone else: "Install Tiki! Do it now!"
luciash: "symfony/console v2.2.0 requires php >=5.3.3 -> no matching package found."
refizul: is there a way to get rid of "Reply-To" email header inside forum outgoing email?
luciash: <u>refizul</u>: sure there is always a way ;)
refizul: ;-) Is there an easy way within Tiki webinterface to get rid of "Reply-To" email header inside forum outgoing email?
<br> IMO this lacks to be a) optional and b) configurable in value
leagris: @luciash My fix is a temp fix
<br> It fix default initialization values for the mime object reguarding a text/plain content part
<br> Well a proper enhancment would be a preference entry alongside charset to choose between 8bit or quoted-printable
<br> and it would need to be initialized within webmailmime extend class fetching some content-encoding preference entry
<br> Still my patch is good for the main class defaults
luciash: <u>refizul</u>: there is no such easy way then
<br> <u>leagris</u>: i wonder if it is worth of patching temporarily in 10.x when that version is going to end and in 11.x+ the file is not present
<br> <u>leagris</u>: it probably uses the Zend framework mimeMail lib or something
leagris: this is it
refizul: <u>luciash</u>: one more for the todo list then
leagris: This means it is a Zend Framework oddity
luciash: no, i mean the htmlMimeMail lib was replaced by the one from Zend
leagris: And it should be tikiwiki extended class initialization job to configure a proper 8bit or quoted-pritable
<br> Oh I see
luciash: <u>leagris</u>: or you mean the same problem is present in 11/trunk ?
leagris: Would it be safe if I upgrade now from 10.x to 11.x?
<br> and see what happens there?
luciash: do you have PHP >=5.3.3 ?
<br> seems it is a requirement for Tiki 11 because of the symfony/console package (dunno what it is needed for though)
<br> maybe not that a big issue
leagris: php 5.4.9
luciash: you should be fine then
leagris: Il look at the 10. zendmail class already present to see what are the defaults there
luciash: ok, not sure it is that one (used) though
leagris: Mail.php: public function setBodyText($txt, $charset = null, $encoding = Zend_Mime::ENCODING_QUOTEDPRINTABLE)
<br> should be fine as the main Mail class initialize to quoted-printable if not specified
Tiki|bot: New Forum Posts: Tiki 11, Tiki 12, Webinar today… all good news ! - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48107
luciash: <u>leagris</u>: sounds good
leagris: asside for a sane default text mime part as quoted-printable, a preference choice should be available to choose between 8bit and quoted-printable
<br> quoted-printable = work everywhere even with outdated MUA. But has a 30% payload due to encoding
<br> 8bit = woork everywhere except on some outdated legacy systems (some very outdated Outlook), and save 30% size
Tiki|bot: New Forum Posts: File and directory structure revamp brainstorming (Major changes coming to Tiki 13 as part of Bootstrap transition) - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48108
rodrigoprimo: joined #tikiwiki
leagris: As reference http://www.w3.org/Protocols/rfc1341/5_Content-Transfer-Encoding.html
goj_killedByISP: joined #tikiwiki
Tiki|bot: New Forum Posts: bootstrap transition - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=48111
Jyhem_laptop: joined #tikiwiki
chibaguy: joined #tikiwiki
leagris: @luciash Test mail from Tiki installer 11.0 fail
<br> Does not declare a Content-Transfer-Encoding mime header which default to 7bit according to rfc1341
chibaguy: joined #tikiwiki
luciash: <u>leagris</u>: thanks, fail means fail to send or fail to conform to the RFC ?
dhazel: joined #tikiwiki
marclaporte: joined #tikiwiki
chibaguy: joined #tikiwiki
dcedilotte: joined #tikiwiki
chibaguy: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
rodrigoprimo: joined #tikiwiki
marclaporte1: joined #tikiwiki
arildb: joined #tikiwiki
redflo: joined #tikiwiki
fabricius: joined #tikiwiki
leagris: @luciash it was only the setup email having no Content-Encoding while using utf-8 (minor bug)
<br> Other Mail messages gets the default quoted-printable as is
jonnyb: joined #tikiwiki
leagris: crap hitting an annoying bug
<br> A subscriber get a red error message "a valide email address is required" while entering a perfectly valid address
<br> besides this, the user account is created but no message is sent to confirm subscription
arildb: Some users get annoyed by the "web page has expired" message, when pressing the back button. What can be done?
nkoth|nelson_: joined #tikiwiki
jonnyb: hi all
arildb: hi jonnyb
Tiki-KGB: tikiwiki 03jonnybradley r46722 10branches/ 10(5 files in 5 dirs)
<br> tikiwiki [bp/r46159 & 46251]
<br> tikiwiki [ENH] trackers: Add pref to allow changing tracker field type after creation - advanced and off by default, but with a extra warning [from revision 46159]
<br> tikiwiki [FIX] trackers: Fix save field if tracker_change_field_type pref disabled [from revision 46251]
jonnyb: <u>arildb</u>: that message is when the data was a POST form submission, using GET instead doesn't have that problem
<br> obviously not clicking the back button but having a link somewhere on the page reduces that problem (but users will still do it)
arildb: right. It's a "tracker based" system. Is there a place I can change to GET?
jonnyb: <u>leagris</u>: is this on tiki-register.php? of something else? (email validation has always worked fine for me - is it an odd email address?)
<br> <u>arildb</u>: no, tracker plugin etc uses POST
arildb: It's a Tiki 9 system. Same there?
aalex: joined #tikiwiki
Telesight: joined #tikiwiki
dcedilotte: left #tikiwiki
marclaporte: joined #tikiwiki
Jyhem_laptop_: webinar is in 45 minutes : https://tiki.org/July+2013+Webinar
leagris: jonnyb it look like I had half baked subscription form enabled, so it failed to send aa welcome/confirmation message
refizul: almost too hot for webinar... ;-)
jonnyb: joined #tikiwiki
refizul: yeah - the heat makes their machines fail ;-)
<br> <u>fabricius</u>: webinar?
<br> five minutes left
marclaporte: joined #tikiwiki
nkoth|nelson: joined #tikiwiki
Jyhem_: grmbl, missing link again to BBB
refizul: https://tiki.org/live
<br> <u>fabricius</u>: ?
Tiki-KGB: tikiwiki 03jonnybradley r46723 10trunk/lib/core/Tracker/Field/ItemLink.php
<br> tikiwiki [FIX] trackers: Repair ItemLink displayFieldsList option which now returns array(0) instead of an empty value, causing JS errors and lack of list (probably needs a better fix upstream as other options will be affected by this)
refizul: just found a new bug...
SkiNut: joined #tikiwiki
dcedilotte: joined #tikiwiki
fabricius: refizul
<br> I am in a phone conference
<br> Germany - USA
<br> an international cooperation project, with a Tiki website