MichawlHabib_dot: joined #tikiwiki
Tiki-KGB: 03amnabilal r60736 10branches/16.x/ 10(7 files in 5 dirs)
[bp/r60717]Fontawesome integration with mpdf
[bp/r60725]Plugin trackerfilter fix with mpdf,Passed all page variables with pdf link for TrackerFilter results to be printed in pdf. Made tracker filter form hidden in pdf.
[bp/r60735]Fixed visibility of all plugins with tablesorter option on in mpdf
03amnabilal r60737 10trunk/lib/pdflib.php * [Fix]Fontawesome support in mpdf fixed, removed extra css files from mpdf
Telesight: joined #tikiwiki
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6211
Recent Bug: - http://dev.tiki.org/item6212
RadoS: Uhm... I just created a report, and a show-instance for it, but I had to change admin password... for the devs to access it, should I set it to some default like "admin"?
Can I create more than 1 instance for 1 case? Like testing with different versions or setups?
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6213
Tiki-KGB: 03yonixxx r60738 10branches/16.x/ 10templates/mail/password_reminder.tpl 10lang/he/language.php * [TRA] improving translation and code.
Leu: joined #tikiwiki
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6214
Recent Bug: - http://dev.tiki.org/item6215
Recent Bug: - http://dev.tiki.org/item6217
Recent Bug: - http://dev.tiki.org/item6218
Recent Bug: - http://dev.tiki.org/item6219
Jyhem: polom
RadoS: common admin password on show instances: 12345 (or admin)
Only 1 instance per bug report
RadoS: Jyhem, devs can reset the pw as they need, or shall I reset it for all instances?
Where should I put accompanying remarks for the showcase? (there is no extra text field for that)
Any idea what's the cause of "No route found - full..." in error_log of apache2?
Comes with quite a few .js files.
Jyhem: they can reset, no problem
well, you can use existing fields, or put extra comments in the showcase, which is a wiki, after all
-: Jyhem is not sitting at his computer, just passing by occasionally
Jyhem: RadoS: ^
-: RadoS nods.
olinuxx: joined #tikiwiki
Leu: joined #tikiwiki
RadoS: If anyone can/shall commit, isn't there some code-review missing? How do you ensure stuff doesn't break?
Or leaves security holes?
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6221
Recent Bug: - http://dev.tiki.org/item6222
Recent Bug: - http://dev.tiki.org/item6223
Tiki-KGB: 03xavidp r60739 10branches/16.x/templates/wizard/profiles_demo_highly_specialized_confs.tpl
[FIX]Update cartograf url for the latest version of the profile (thanks luci for the info in the devel list and all those who worked to update the profile)
03xavidp r60740 10branches/ 1015.x/templates/wizard/profiles_demo_highly_specialized_confs.tpl 1015.x 1015.x/templates
[bp/r60739][FIX]Update cartograf url for the latest version of the profile (thanks luci for the info in the devel list and all those who worked to update the profile)
03xavidp r60741 10branches/16.x/templates/wizard/profiles_demo_interesting_use_cases.tpl
[FIX]Update Bug_Tracker profile in the Wizard to use the latest profile for this version of Tiki
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6224
Jyhem: RadoS: All commits create an email which is sent to this mailing-list: CVS/SVN commits information <tikiwiki-cvs@lists.sourceforge.net>
that's where anuone can subscribe and review the commits (and some do)
stuff breaks all the time, that is why we have: https://dev.tiki.org/Where+to+commit
so it breaks trunk and we can fix it before we publish a releasable version. There is a feature freeze before releases (bugfixes only)
same for security
emil__: joined #tikiwiki
emilVFR: joined #tikiwiki