I tried this change of commands.php but no difference: the user name
in Cyrillic is unchanged both in the page name and in the display of
{id}, in contrast to the other pages created by action.create - the
same before the change and after that. I tried to create few users
with Cyrillic names.I tried to implement the join command to the action.register form, but unsuccessfully, maybe it works only for registered users I am sorry that Googlegroups do not support Cyrillic. Regards, Bogdan On 7 Ян, 18:18, The Editor <[email protected]> wrote: > Bogdan, try changing line 230 of commands.php from the first to the second: > > $members =$BOLTarray['members']; > $members = BOLTutf2url($BOLTarray['members']); > > Tell me if that doesn't solve the problem... Or if it does. :) > > Cheers, > Dan > > 2010/1/7 Bogdan <[email protected]>: > > > > > Thank you Dan for the comprehensive answer. > > > I'll try the option with the generated {id} and action.join. > > > Now, I can give you some text in Cyrillic to play a little: > > - 'Последен' means 'Last' as an one-word name of page with capital > > - 'Книга на Основите' - as sentence case example (means > > approximately 'Book of Fundamentals') > > > Regards, Bogdan > > > On 7 Ян, 00:54, The Editor <[email protected]> wrote: > >> On Wed, Jan 6, 2010 at 3:28 PM, Bogdan <[email protected]> wrote: > >> > I stumbled about at few problems which I cannot get they are my lack > >> > of understanding of BW or some kind of issues: > > >> > 1. I tried to put a user into Editor rank, so I make group.editor > >> > page and wright his name there on the first line. Then I entered the > >> > system with his details and the check showed a simple member priority. > > >> > Can the problem be that the name is in Cyrillic? > >> > Recently I spend 2 hours until catch that strtolower() and other strto* > >> > () functions do not work with Cyrillic. > > >> Very likely. Can you get it to work using the action.join page? What > >> happens when you put {id} on a page? Can you cut and paste that to the > >> group page? Case sensitivity may be a problem here. Give me any > >> information you can give me--like example cyrillic I can test with. > > >> > 2. The [option] markup doesn't generate a closing tag, instead it > >> > wrights <br/> or nothing: > >> > <option />some select<br/> or <option />some select <option / > >> >>another select... > >> > which is not XHTML compliant. It should be: <option>some select</ > >> > option> \n > > >> Are you sure about the XHTML compliance? Try changing line ~429 of > >> markups.php like this: > > >> Old return BOLTescape("<option $attr />$label"); > >> New return BOLTescape("<option $attr>$label</option>"); > > >> If it solves your validation, great. If the <br /> causes problems, > >> try putting all the options in one line without breaks. We will be > >> revisiting that line break issue another time--and I hope to solve > >> this as well as several other problems then. > > >> > 3. The docs.concepts.search.template reads: > >> > "First it will search for template.yourvalue, if not found, it will > >> > look for the exact same page as entered and use it as template. > >> > Finally, if no template is found it will use template.default." > > >> > I tried to use the option for page specific template ( 'the exact same > >> > page as entered') with no success: > >> > for the page action.chapter.create, > >> > I tried to make template.action.chapter.create.menu > >> > and use it as: template=menu > > >> The template selection is not hierarchical. If you enter > >> template=whatever, it looks for either template.whatever or whatever. > >> It doesn't do any hierarchical checking. If this is an absolute > >> necessity, I can look into it. Probably would not be that impossible, > >> but it's already looking several locations. Seems just as easy to use > >> whatever1, whatever2, whatever3, etc. > > >> > 4. Has I've got that in BW 3.3.4 we can use any html tags? Including > >> > nested tags? So full html compatibility? > > >> I'm sure there are some html things you can't do, but I think we have > >> support for most common, simple tags. We basically added support for > >> capital letters and tags like <br /> (with the closing slash). Do some > >> testing. If something doesn't work we can try to add it. > > >> > Finally, I support the idea of simple txt source files with no > >> > escaping and special encoding. > > >> Good that's another vote for this! > > >> > Happy and Merry New Year to All! > > >> Thanks! And same best wishes to you and the rest of the BoltWire > >> community. Good to be home again coding to my hearts content. > > >> Cheers, > >> Dan > > > -- > > You received this message because you are subscribed to the Google Groups > > "BoltWire" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/boltwire?hl=en.
-- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
