Hi! I recently set up tikiwiki on my server; I am wondering how I can set up a module for articule submissions for members/admins
Guest94182: hi, have u searched for the module article submission keywords on doc.t.o ?
polom everybody btw
doc.t.o? I read the tiki for smarties and some document
http://doc.tiki.org
Yeah, I did
tikiwiki: 03chealer * r31005 10/trunk/tiki-login_openid.php: [FIX] OpenID: consumer->begin() can return NULL simply because the OpenID provider doesn't have a trusted certificate, so make the error message vaguer
tikiwiki: 03chibaguy * r31006 10/branches/6.x/templates/tiki-directory_footer.tpl: [ENH] Pointless use of class removed (for simpler CSS rule).
tikiwiki: 03chealer * r31007 10/branches/6.x/tiki-login_openid.php: [bp/r31005][FIX] OpenID: consumer->begin() can return NULL simply because the OpenID provider doesn't have a trusted certificate, so make the error message vaguer
tikiwiki: 03chibaguy * r31008 10/branches/6.x/styles/ (10 files): [CSS] Unnecessary instances of "div.", "span." and "table." removed.
is there a way in tiki 6 to make a blog the start page?
I tried to go via admin/General on the navigation tab
JoernOtt: to do that the only trick is that you have to set first the blog home page on Admin -> Blogs and after that set the feature blog as the home page on Admin -> General
ok
thx
well, after setting it in Admin->General, it always reverts to "Wiki"
I just set tikiIndex in the tiki_preferences table manually to "blog1" and got the desired results
JoernOtt: I have the same problem, so looks like a new bug
JoernOtt: was working a few weeks ago, so probably a regression bug
 Info: Tiki Training Day in Quebec City on December 8th - http://info.tiki.org/article126-Tiki-Training-Day-in-Quebec-City-on-December-8th
hi all :-)
 Recent Bug: Tracker item: #3691 - - Category Transition not working  - http://dev.tiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=3691
rodrigo_sampaio: I just set the value manually in tiki_preferences
There you could also use "blog35" even if another blog is set to your home blog ;-)
Polom!
I am fighting with UserTracker and the registration of users. The user tracker works fine when I edit items and view them when users are logged. But  the registration form allows me to input the data but doesn't save. Ideas?
I mean, during the registration process.
polom PhilBack_ - which tiki version?
6.x
I am looking inside the code of wiki_plugin and registrationlib and tiki-register.php|tpl for a while now... Trackers are not that easy code-wise, given all the features :-)
i've got user-registration tracker workin on my tiki 6 sites. i haven't seen any issues
the tracker works inside the site, no issue.
The point is registering users at the start.
i mean, the tracker works during registration process just fine
http://tiki.socius.be/tiki-register.php isn't working for me. Fields do appear and I can fill them in. The user gets registered but not the values in the user tracker.
i assume that you have the "user information tracker" selected correctly and the primary field identifed with the userid, right?
The fields shown are a subset of all possible fields in the user tracker. May it be linked to it.
yes, the field is properly set. With 1 autoassign and all.
It's weird.
I use wikipage templates for the look.
Yes, it works. Hence my disappointment when it doesn't saves right... :-(
so no record created at all in the db?
or is there a record, just not attached to the new user?
Let me see. I guess, there isn't any. But want to be 100% sure.
No record. No trackeritem, No trackerfield values
do u have tiki error reporting turned on? any errors?
Well,lemme check that.
most odd - PhilBack_ (and hi ricks99) - i have a 6.x one running fine, so no bugs there i am aware of
just found a big horror in 6.x - feature_wiki_protect_email seems very broken :(
I've got a bunch of notices.
but it tells me: You will receive an email with information to login for the first time into this site 
and I get the mail.
so the rest of the registration process works? user can actually verify and login?
yes, sure
as with jonnyb (hi) i too have 6.x with user registration tracker and no issues....
mmmh, well, ...
can you check the db tables and verify that none are marked as crashed (especialy the tiki_tracker_xx tables)
already did at least twice.
nothing.
hm.
indeed
can anyone else please check if feature_wiki_protect_email is failing? I'm getting the javascript tag sanitised and it wrecks all the JS on a page :(
i'm fixing now... (not trivial)
as an experiement, can you create a new tracker, just simple, and use it as the registration tracker, but  *without* the wikitpl
will do.
here, I've got username as field in my usertracker with userselector as type and 1 as parm (autoassign)
tiki-view_tracker_item.php?view=+user works perfectly once logged in...
@jonnyb: protect email seems to b fine for me
view/edit
ricks99: hmm, seems to depend on the user pref - i have "Is email public? (uses scrambling to prevent spam)" = "no")
r u talking about a specific user's email protection? or the generic js that will protect any foo@bar.com on a wiki page?
seems to be the generic one...
seems fine on my 6.0
hmm, ok - it's an allow_html thing - seems to get more sanitised then a page is html
(i.e. using wysiwyg)
ahh....
works fine in tiki edtor
ok, there was something else that broke like that - i'll redirect my debugging
hi lphuberdeau 
good morning
hi lphuberdeau
lo
hi lph
I think this is more welcoming than average
what do you all want?
:D
:-p
I want usertracker fixed
 New Forum Posts: Tracker Email Field Validation REGEX - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=39730
sorry phil, I can't fix what I can't wrap my head around
hehe
Debugging with Ajax is really an issue... How do you deal with that people?
firebug
sometime even that gets lost
Well, I mean at the PHP level. My debugger keeps at opening files that are in Ajax requests. I am debugging the PHP code.
yeah, just avoid bugs in the first place
last resort i hack - alert("here!") - commands in the scripts
I am looking for someone else's...
console.log() works for me
PhilBack_: are you using eclipse/aptana? There's an option to "break on first line" that's really annoying - switch it off
it's in the debugger options config thing
I am using NuSphere's PhpED. Yes, that's maybe the thing. It stops at every file.
Thanks jonnyb
Ha!
is money? (and Windows only?)
Windows.
Money.
But worth every cent.
there isn't enough money to make me use Windows (well, not in the Tiki world! :) )
Bah, I am pretty agnostic. Windows, Linux, Mac, all over me in this office. Even Blackberry OS.
but i've been planning to spend some money on an IDE if i can find one that's better than Aptana (for Mac OS)
PhpEd works under Parallels and VMWare Fusion on my Mac
fair enough for me.
But I prefer to code under Windows, go figure.
Me too - but in my own home, with my own money i don't tend to want to use it on microsoft products...
have parallels, but need a native thing (12 hours a day in an emulator is no fun)
Well, I have my own business and Microsoft Action Pack is a bargain. (Parallels no emulator, it runs native code in x86)
each to their own ;) i was just checking...
tracker found properly in the code.
Mac is perfect for video and audio. Linux perfect for heavy lifting. 
I still don't understand what feature is missing in vi that pushes people towards those huge IDEs
Well, can use vim and even the PHP plugins but easier with PhpEd. Will do a vid to show.
ricks99, you know you can help make it better by providing feedback early, right ? :)
been posting to the page on dev.t.o
about the popularity stuff, it does not seem impossible, but that kind of falls lower in priority - fuzzy stuff is hard to flag as completed
but most of the rating stuff can already be achieved with advanced ratings
tikiwiki: 03jonnybradley * r31009 10/branches/6.x/lib/tikilib.php: [FIX] parse_data: Don't parse inline syntax for ck_editor. Email protect JS gets sanitised and breaks the page.
tikiwiki: 03pkdille * r31010 10/branches/6.x/lang/fr/language.php: Typo
about range filtering, that's in. I don't keep track of expiry at this time... outside of articles, what else can expire?
calendar items
tracker items with date range
calendar items right now are "left as an exercise to the reader"
?
not implemented
doing a site search should NOT find expired events (at least not as default)
tikiwiki: 03jonnybradley * r31011 10/branches/6.x/lib/smarty_tiki/block.textarea.php: [FIX] wysiwyg: Oops, committed debug setup, apologies (thanks Geoff)
or past events should b ranked lower
the other big thing ive been thinking about, is a way to show/filter search results to show items to which i have contributed
i = the searcher
contributors are indexed when possible
all of em for wiki pages, only first/last for most of the rest
perfect.
because the db does not keep em all
coud this be extended  to "participants" in calendar events?
I know nothing about calendars
when calendar is implemented?
but essentially, about anything can be added to the index, it just becomes a matter of making a UI that makes sense to search in it
ricks99, something is failing in wikiplugin_tracker.php when the system tries to find if values have to be saved or something. That's where the issue lies with the UserRegistration tracker.
Will compare with latest code.
from 6.x
@PhilBack_: not sure. as i said, the registration trackers are working on my 6 sites :(
there is something in there. I've debugged step by step. The registrationlib->register_new_user succeeds and then tiki-register.php proceeds with the usertracker and.. well, fails. This is something with a test. 
($_SERVER['SCRIPT_NAME'], 'tiki-register.php') === false fails or something like that. the $_SERVER[...] value is "/tiki-register.php' at debug time. not tiki-register.php Maybe this has to do but not sure.
tikiwiki: 03jonnybradley * r31012 10/branches/6.x/lib/prefs/feature.php: Add conditional warning to feature_wiki_protect_email pref to warn about it not working in wysiwyg mode.
PhilBack_: sounds feasible - what file/line?
only one i can find is in wikiplugin_tracker.php - and that uses strpos, so should match /tiki-register.php
lib/wiki-plugins/wikiplugin_tracker.php:314
yes but execution flow doesn't go in. Maybe strpos should test agains 0
That's when it should save.
but strpos($_SERVER['SCRIPT_NAME'], 'tiki-register.php') === false should me it's testing that we're NOT on tiki-register.php (no?)
strpos returns false if the string's not found
returns 0 if it's found at char 0
Test wrong then. I"ll test.
try tiki-register.php
(expect that's where you started :P)
yes
line 70ish
sorry, no - that's where it makes the form
thing is: the user gets registered using the registration lib, confirmation is given, but the tracker item values aren't written out during registration. The only place would be in wikiplugin_tracker. But it doesn't happens.
tikiwiki: 03cdrwhite * r31013 10/trunk/ (3 files in 3 dirs): [NEW] Accounting: Allow cancellation of entries in the journal
JoernOtt: by the way, I gave a quick look at the code, everything seems standard
PhilBack_: can't see where or how it creates the usertracker item - mysterious...
ah ah, I guess it doesn't
the mystery deepens
lphuberdeau, thanks, I am trying hard to
well, it does on one site i have - but i never stepped through it - it just seems to work for me
I don't know much about accounting (just enough to be dangerous actually), so I can't really comment on the specifics
There are still many open points but the ones documented should work now
I see that you manually set object permissions when creating some type of object
seeming to work as well here, but doesn't. I have to login, and then, fill in my user tracker data. But upfront, it doesn't goes well. But: I am not using ALL fields from the user tracker in the user tracker form. Could it be the issue? In fact, I do not want to ask everyting upfront, just the essentials.
this is the very special part, when creating a book
I create a group for this books "admin accountants" as well
I think it's a nice usability touch, but I can't help to wonder if the management burden wouldn't be lower by using category permissions
and give the necessary objet permissions for that book to the newly created group
Theroretically you could set up an accounting company with tiki
for each customer you have one book (per year), none should see the others and different people are allowed to do different things
and that really has to change from book to book?
or you could just have a category per client and manage permissions there?
of course, I would not want the computer-club people look into my companys finances
or worse one of the current "accountants" to book in there
I see the need for permissions, trying to see if forcing the granularity and group creating is really mandatory
In the beginning I was planning on one book only,  but the different books were a request on the accounting page
PhilBack_: ok, i eventually get through to wikiplugin_tracker.php line 631 which seems to create the tracker item for me - you don't i guess?
called from tiki-register.php line 79
I guess I would like to see more categories used in there, because that's the binding point with other features... categorize books and items in there
@jonnyb: you mean the trklib->replace_item?
yup
Take my company as an example: I am the owner, so I should be able to view, but I am not getting my hands dirty (in theory). My employee does not know much about accounting, but she has to type in all the paperwork, so she'll get book_stack permissions but no view permissions
about there, stepping...
and then we have an accountant who may book 
so, for one book we already have 3 groups
never got there.
oh, so the stack is some sort of buffer space
a sandbox
you can book transactions there and alter them
for the IRS, it does nor exist
@jonnyb: This is never triggered and I get the "You'll receive an email..." 
oh yeah, transactions, you seem to have dangling code about that in there
and the accountant reviews stuff in there and moves it to the journal
(database transactions)
@jonny and $values are empty
"transactions" are booking transactions here
PhilBack_: do you get into wikiplugin_tracker.php - and past line 355?
I do get into wiki_plugintracker.php but will check line 355. Breakpoint set. I've to encode the fields
Actually, if you could make items categorizable, it would be really nice... you could attach expenses to projects or clients and then list those at different places
otherwise, the code seems ok to me
l 289: $values is NULL
well, a transaction is always at least two accounts and usually a client is an account
$_REQUEST contains all track_ fields
$itemId empty
so if I book EUR1000 from your account into profits, that means I charged you 1000 EUR
tikiwiki: 03jonnybradley * r31014 10/branches/6.x/lib/setup/twversion.class.php: [REL] Preparing 6.1 alpha 1
Skipping: if (isset($_REQUEST['removeImage']) && !empty($_REQUEST['trackerId']) && !empty($_REQUEST['itemId']) && !empty($_REQUEST['fieldId']) && !empty($_REQUEST['fieldName']))
and later when you pay, I'll book EUR 1000 from BANK to your account
got to 362
wouldn't it be nice to be able to list all transactions related to project XYZ, which is just one among many others with a given client?
PhilBack_: hmm, the $tracker['start'] bit - not sure what that is but mine skipped straight over that bit
which I can easily do by assigning it an account number (this is what accountants usually do)
just wondered why large companies run with 12 or more digit account numbers?
inside if ($thisIsThePlugin) {
on your tracker edit form do you have the checkbox "Items can be created only during a certain time" checked?
no
sure, there is the classic way of doing it, but tiki has categories that can also do that, and if there are other documents in Tiki related to those projects, they could all be linked together
what's the value of $tracker['start'] there? (and end)
if you are clever when planning your accounts schema, you can also group similar projects from different clients, because they al have 9** at the end
... or not have to be clever and use the existing hierarchy
PhilBack_: looks like it must be line 361 that's failing for oyu
null
and $tikilib->now ?
something in that line must be true
: long = 1291389765
sounds like "now"
I do not know what implications it would cause on my workload, implementing categrories and where to implement them
PhilBack_: bizarre - i call these "1 equals 2 problems"...
At the moment, I am just trying to get the core functionality of an accounting software to work here
$ins_fields["data"][] look like okay
PhilBack_: but it does the return on line 362?
joernott, I get that, just discussing here and trying to understand where it's all going
can't see now, I've been back to the web okay page.
Well, brb10 my wife calls me...
and maybe pushing a bit for it to be an accounting system within tiki rather than an accounting system on top of tiki
this is why I try to create things as modular as possible and with a lot of documented functions in the accountinglib
so that we'll have easy interfaces
@jonnyb I get past that
but not as far as where the replace_item happens?
tikiwiki: 03lphuberdeau * r31015 10/trunk/ (3 files in 3 dirs): [MOD] Adding category picker to build category filter query
indeed
$fields_plugin contains ALL plugin fields, not only the ones I have in the tracker.
I'm having problems with the CSS menus on IE6/7. The theme is coelese.
tikiwiki: 03jonnybradley * r31017 10/branches/6.x/ (4 files in 4 dirs): [MOD] fgals: Change the default for gallery "archives" to 0 meaning unlimited, instead of -1 meaning none (it's the wiki way!)
The text and icons underneath the menu show through or are on top of the menu.
jonnyb: found why: fields are not correctly compared. I do have a alphanumeric fields encoded under "Functie" which ends up tested against a "PostCode". Obviously not a numeric and that's the error I get on the field...
PhilBack_: strange, is it a bug then? or a config issue?
bug
 New Forum Posts: WYSIWYG editor window Background issues? - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=39732
The code works if you use ALL fields of the user tracker at registration time. If you use only a subset and want others to be filled later, it fails.
not sure what "Functie" is?
$field_errors = $trklib->check_field_values($ins_fields, $categorized_fields, $trackerId, empty($itemId)?'':$itemId);
'Functie" is the label of one of my tracker fields meant for things like "Job or Position"
hmm, if they're mandatory? or just not filled in?
no it checks the wrong fields.
seems odd, i thought i have a similar thing but was ok
$ins_fields is 6 entries, whereas the tracker has more. I'll track it down now.
(you just reminded me of a little usertracker bug - it shows "user: *" on the registration form but no field)
I'll be more knowledgeable about trackers for sure...
brave man! :D
jonnyb: I saw that (user: * with no field yesterday). The visibility was set to creator and admin.
Setting it to all and controlling access by groups allowed the field to show.
yes, i just removed that field id from the user tracker fields list on the reg group properties - makes it disappear but it still works
jonnyb: the issue is not in check_filed_values but before because $ins_fields contains crap.
tikiwiki: 03jonnybradley * r31018 10/branches/6.x/lib/tikilib.php: [FIX] listpages: Do an exact match when exact_match is true
@jonnyb: I happen to love trackers :-)
hurrah! someone who can code and loves tracker! :)
I guess the love/hate relation you have with trackers depend on which side of the user/developer fence you are on
there's a plan to do a very severe refactoring job on them for Tiki 7 or 8 - it's well overdue
Is there a way to allow only the creating user (or admin) to edit the information they added? For example, let the user edit their UserTracker information without everyone else seeing it?
Well, there isn't much like that in other CMS/Groupware. 
@thraxisp yes
PhilBack_: pointer please
thraxisp: i think as long as there's a user selector field with option "1" it just does it - oh, and check "Item creator can modify his items?" in the tracker properties
tikiwiki: 03lphuberdeau * r31019 10/trunk/ (3 files in 3 dirs): [MOD] Adding language filter to the UI
tikiwiki: 03jonnybradley * r31020 10/branches/6.x/lib/ckeditor_tiki/tikilink_dialog.js: [FIX] wysiwyg: tikilink jslint, change "Link Text" label and remove utf8 BOM
jonnyb: found issue: config mess by the user behind my back. Thanks for the help. Works all right now. He messed a {$f_xx} in the wiki template... Rhaaa
jonnyb: I have that, but I also don't want others in the group to be able to see the information in the tracker. 
PhilBack_: nice one, that's what users are for :P
thraxisp: have you tried removing the relevant view permission for that group from the tracker?
@jonnyb: anyway, keep in touch for trackers ... :-)
jonnyb: I did, but then I can't list the tracker to edit the item (message "You don't have permission to use this feature")
tikiwiki: 03lphuberdeau * r31021 10/trunk/lib/jquery_tiki/tiki-jquery.js: [MOD] Adding an empty character to help default selection
thraxisp: odd - you're admin?
yes. Admin can see and edit everything. I want the user to be able to edit their own record but not see other user's records.
The user (group Registered) sees the error
hmm, i thought that was possible - not done it myself though
tikiwiki: 03jonnybradley * r31023 10/branches/6.x/lib/ckeditor_tiki/tikilink_dialog.js: [FIX] wysiwyg: Fill tikilink "Link Text" with selection when creating a new link.
I cannot disable "User Messages" in Admin/Community. How comeS?
PhilBack_: you're right - looks like a bug
worked 2nd time when i clicked the little green arrow
jonnyb: I'll play with it some more. (I need to create a sandbox on a local machine).
my more pressing problem is the CSS Menus. tw.o has the same problem.
PhilBack_: looks like feature_messages appears twice in admin/community
tikiwiki: 03jonnybradley * r31024 10/branches/6.x/ (2 files in 2 dirs): 
tikiwiki: [FIX] admin community: feature_messages appeared twice in the same admin page, so you had to click both to make a change. Removed the 2nd one (and added some missing dependencies for the other prefs)
tikiwiki: Thanks PhilBack
tikiwiki: 03sampaioprimo * r31025 10/branches/6.x/lang/de/language.php: German translations done on i18n.tiki.org (1140 new translations and 100 translations updated!)
 Recent Bug: Tracker item: #3692 - - Text shows through CSS Menu in IE7  - http://dev.tiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=3692
@jonnyb: ok, will look
I'd like to bridge calendars and trackers for registering people to events. How to do this ? Insert a TRACKER in the event description? I'd like to have this in the right margin as a  module.
PhilBack_: it's a common thing - been a holy grail for a long time (non-trivial to do properly)
PhilBack_: The only thing existing now is http://doc.tiki.org/PluginTrackerList#Tracker_as_calendar
Another tracker question. Is there a way to update a tracker based on a wiki page without user input? I want to add an "i've paid" flag to a tracker and have it set when the user comes back from the payments page (e.g. PayPal).
I don't think you can actually rely on that page hit alone
if you use tiki payments, you can attach a behavior to update the tracker when the payment is received
not that the behavior is written for trackers, but there is a better hook for that
polom
hi chealer 
I see that there can be a button to prefill a tracker, so I'm looking for a way to do that without the button.
@sylvieg: Ok, I'll do some code then/
the problem is that you rely on something that may not be true - unless you change the value from the actual payment confirmation, which comes from paypal IPN, there is no way you can be sure you're not marking a payment as paid that is not
lphuberdeau: that was the plan. Right now it needs to be correlated by hand.
not sure it's much harder to add a behavior than to fiddle around tracker prefilter
lphuberdeau: thanks. I'll look into it some more this weekend.
polom
hi changi, jonnyb
chealer: hi
tikiwiki: 03changi67 * r31027 10/branches/6.x/README: [REL] Update README file for 6.1alpha1
changi: tu te fais à l'idée de ne pas avoir de 6.1 pour ta fête? :-)
chealer: oui tant pis 
tikiwiki: 03changi67 * r31028 10/branches/6.x/lang/ (47 files in 47 dirs): [REL] Update language.php files for 6.1alpha1
tikiwiki: 03changi67 * r31029 10/branches/6.x/changelog.txt: [REL] Update changelog.txt for 6.1alpha1
tikiwiki: 03changi67 * r31030 10/branches/6.x/copyright.txt: [REL] Update copyright.txt for 6.1alpha1
for ricks : Changelog updated with 167 new commits (revision 31025 to 30768), excluding duplicates, merges and release-related commits.
hi changi 
i'm (as usual) just about to do a little commit :)
(and don't care about the changelog - it's alpha anyway)
you have exactly 2 minutes :)
just let me know when it's done.
ok, let's alpha! :)
i'm going to eat something
tikiwiki: 03jonnybradley * r31031 10/branches/6.x/ (4 files in 4 dirs): 
tikiwiki: [ENH] newsletters: Quick fix for the newsletter CSS problem (where it would include all the css in the emails).
tikiwiki: Adding the possibility to have styles/yourtheme/newsletter.css (and one for option too) which will be minified and written into the mail if found (otherwise follows previous behaviour of including everything).
tikiwiki: Added fivealive/newsletter.css and fivealive/options/grape/newsletter.css for testing purposes (need more work pls).
tikiwiki: Made minify_css() in headerlib public.
2 minutes you said :P
eating good, i'm off for that too - bbl
ok
tikiwiki: 03changi67 * r31032 10/branches/6.x/db/tiki-secdb_6.1_mysql.sql: [REL] SecDB for 6.1alpha1
thanks changi 
tikiwiki: 03lphuberdeau * r31033 10/trunk/lib/tikilib.php: [MOD] When running the parser with stripplugins, preserve the body which may contain valid data
tikiwiki: 03jonnybradley * r31034 10/trunk/ (81 files in 63 dirs): [MRG] Automatic merge, branches/6.x 30996 to 31032
tikiwiki: 03changi67 * r31035 10/tags/6.1alpha1/: [REL] Tagging release
tikiwiki: 03sylvieg * r31036 10/branches/6.x/tiki-view_blog_post.php: [FIX]blog: permission denied if post not yet published
tikiwiki: 03lphuberdeau * r31037 10/trunk/lib/ (7 files in 6 dirs): [MOD] Wiki-parse content to strip out syntax
tikiwiki: 03sylvieg * r31038 10/branches/6.x/tiki-view_blog_post.php: [FIX]blog: use admin blog perm
tikiwiki: 03chealer * r31039 10/trunk/lib/core/TikiDb/Pdo.php: 
tikiwiki: PDO: avoid prepared queries when there are no binded parameters
tikiwiki: thanks lphuberdeau
tikiwiki: 03sylvieg * r31040 10/branches/6.x/ (lib/blogs/bloglib.php tiki-view_blog_post.php): [FIX]blog: do not show prev next of non published blog post if no perm
oops sorry did not see some release was on
hi sylvieg. are you available to discuss the password options again? there was still unclear parts after your commit.
sylvieg: no prob, it was an alpha :)
chealer:  ??? probably not finished...
with you I should always say work in progress ;-)
sylvieg: I'm talking about http://tikiwiki.svn.sourceforge.net/tikiwiki/?rev=30718&view=rev
in particular that really old option I think
I sent a mail now .. did I forget to commit it
the same mail to the user and the admin .. work on progress
sylvieg: what does it mean to re-validate a user?
an admin must checj the button in tiki-adminusers.php
sylvieg: what does that button do?
the user can log-in again
sylvieg: what else does it mean? unsucessful_logins has 'description' => tra('After a certain number of consecutive unsuccessfull login attempts, the user will receive a mail with instruction to validate his account. However the user can still log-in with his old password.'),
sylvieg: BTW, unsuccessful has a single "l"
chealer: no more idea how to improve the explanation
sylvieg: do you know what the option does?
this one? it doesn not invalidate the login
sylvieg: yes. so what does it do? do you know what re-validating a user means, if it's not about making it temporarily impossible for the user to login?
the first option - a user can still log-in with the olf password
the second it is impossible
sylvieg: OK, but what does the first option do?
I suppose it is for not high security site
where spam is tolerated
s/spam/login attack
sylvieg: do you know what re-validating a user means, if it's not about making it temporarily impossible for the user to login?
will not answer on this one - because it is ambigous
it does not mean the same if it is an admin or a user
sylvieg: then what does it mean in this case?
which case
sylvieg: the old option we're talking about - unsuccessful_logins (Re-validate user by email after: x unsuccessful login attempts)
it means the description .. see above
 tra('After a certain number of consecutive unsuccessfull login attempts, the user will receive a mail with instruction to validate his account. However the user can still log-in with his old password.'),
sylvieg: what does validating an account mean?
hi jonnyb. it seems we have an alpha1
super - something to test?
found them (on sf.net)
interesting (?) only about 1000 downloads for 6.0
jonnyb: I'm seeing about 4000 for the tar.gz, the tar.bz2 and the .zip
just tested the gz - unpacked and installed fine
ah, it was just this month
6000 in all of 6.x ever
66% on windows ;)
20% in Germany
China #3 downloader
jonnyb: interesting, but it could be people uploading via FTP
117 countries in total - good stats on sf these days
it would be nice to have longer term stats showing the increase with yeats
indeed - only goes back to feb this year afaisc - http://sourceforge.net/projects/tikiwiki/files/stats/timeline?dates=1995-12-03+to+2010-12-03
great!
83,000 downloads in total (that's quite a lot)
see you l8r.
let's hope 6.1 can break 1000 on one day (965 july 1st)
jonnyb: ah, hadn't found these. interesting
I didn't think about looking in Develop
sylvieg: about the new option, I already asked, but is there a mechanism so that admin accounts cannot be disabled? IOW, is a DOS forcing a recovery from the database possible if that feature is enabled? 
http://sourceforge.net/project/stats/?group_id=64258&ugn=tikiwiki is good too (wow, we're using 5GB a day - that's not cheap - thanks sourceforge)
odd, it seems we had nothing particular on July 1st
bbl
A plugin should always have {foo()} as its start, right?  With the ()?  Or did that change recently?
{foo() /} did not work last week in trunk
Ah, apparently there's a short syntax now, that broke many many of my pages.  -_-
We were relying on {foo} not doing anything, you see.
Now it's errors aaaaallll over the place.
in trunk or 6?
In trunk.
*Should* {foo bar} be treated as a plugin?
yeh.. I am afraid lph change a lot of things
Because if not, that's a bug, cus it is.
lph?
lphuberdeau: 
Oh, that's a person.  I thought maybe it was a dev initiative.
Do you think that should be treated as a plugin?
You personally, I mean.
sylvieg: ^^
I do not know .. I do not know the plugin grammar now in trunk
can you switch back to tiki6
Sure.  How?  :)
I'm not good with svn tags and such.
svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/6.x
Thanks.
syntaxes are:
{PLUGIN(...)/}
{PLUGIN(...)}...{PLUGIN}
{plugin ...}
lphuberdeau: That last one means that any use of {...} anywhere on any page will suddenly break.
Since it's been possible to freely use {...} before, that's really bad; it's going to break a lot of pages, and not just on my site.
And it breaks very loudly.
been like that for a bit now
few versions
Apparently not, since the 6.x branch doesn't have this problem.
trunk does not change much to the syntax, only the parsing
Apparently it does.
Beacuse I switch to 6.x and the problem went away.
I guess you can write unit tests to isolate your case
What's to isolate?  {foo bar} doesn't cause an explosion in 6.x, and it does in trunk.
that's a feature to me
well, not the exposion
explosion
but the parsing
Except for the part where many thousands of previously extant pages break.  It's not just me; any discussion of coding or mathematics will have the same problem.
Breaking tons of things to save you a few characters is not a feature.
that syntax was introduced many versions ago
Then why does it cause no trouble in 6.x ?
difference in the way it's parsed, might be a bit looser
{foo bar} does not explode for me
merely mentions the plugin does not exist
*sigh*  Whatever.  I'm out of trunk.  There's a problem.  Y'all should probably fix it, or people will just come back and yell later.
wow, nice attitude
Yes, and when you've got *dozens* of "plugin does not exist" on one page, when instead the text used to be "{foo bar}", there's a problem.
lphuberdeau: You're telling me that dozens of my webpages suddenly becoming unsuable is a *feature*, and *I* have the attitude problem?  I'm inclined to disagree.
Sorry, but I've been running tiki for ... what, 6 years now?, and every time I update something explodes.  It makes me cranky.  My apologies if I went too far.
I don't like your tone. It's not like I intentionally break stuff.
You told me that my problem was a feature; that sounded to me like "I don't care if it's broken for you, fuck off.".   If that's not how you meant it, again, my apologies.
03-14:33 < Broca> ro do bo canda'a ro ko bo cande .e ca ta'a ro do bo cande -- example page, for what it's worth.  In trunk, about half the text is replaced with "plugin not found", and the actual text is eaten.
Erm.
http://www.lojban.org/tiki/tiki-index.php?page=BPFK+Section:+Miscellaneous+Notes+And+To-Dos -- *that*'s the example page.  Sorry.
tikiwiki: 03sylvieg * r31041 10/branches/6.x/ (2 files in 2 dirs): [FIX]tracker: translate also the description
In general, I don't think a single character should ever indicate any thing in any wiki syntax; it makes it too hard to just write normal text without thinking about markup.  But that's a seperate discussion, I suppose.
(that is, it is fairly common for people to want to put things in (...) or [...] or {...}, so none of them should cause surprising things to happen)
well, it improves readability a lot
Only if you know it's going to happen in advance.
When you have a lot of users that aren't wiki experts, who just want to enter some text, it causes problems.
but initially, the goal of the short syntax was to remove all the special handling in the parser
which used that precise syntax
difference now is that it reports the plugin missing of just writing back the syntax
svn up
tikiwiki: 03lphuberdeau * r31042 10/trunk/lib/tikilib.php: [FIX] Reverting back to previous behavior or indicating missing plugin by writing back the syntax
lphuberdeau: Well, it certainly would be easy to change that last part.  I had thought that it was a syntax change, not just an alerting change.
and it is
What?
changed
Which?
the reporting
Ah, OK.  Thanks.  I'm sorry again for my comments earlier; I thought you were saying something different than you actually were.
I just hate reports saying "it's broken"
Fair enough.
especially when I spent dozens of hours fixing issues and it took 4 weeks for this detail to come up, hearing I broke everything is not really fun