next default template to build 261

[rejetto]

ok, we are at Release Candidate stage
all important features have been made.
if you download the attachment at first post you'll find something new:
- upload progress
- more search options
- password changer

feedback is welcome

[maverick]

Just a thought as you are working on it anyway... how about introducing pages into the default (select number of files/folders to display per page)?  I'm sure some users would welcome it.

[rejetto]

i meant to do it and i forgot.
i will

[rejetto]

updated version
much more customizable by putting javascript in section [more onload]
supporting and /regular expressions/ for the selection mask.

[timteka]

i have two scrollbars now (both in FF and IE), just like on this screenshot:

[rejetto]

yeah, i knew it.
i eventually addressed the problem, and hope the solution will fit.

please re-download to get the new version.

[maverick]

1.  I think 'word wrapping' is a better choice than a horizontal scroll bar.  I'm thinking of those folders with longer comments (properties -> comments) which force you to scroll one or two screens to the right to see the size/date/hit columns when the horizontal scroll bar is active.
2.  Pages?

[rejetto]

1. i don't know what you are referring to. The only place where i forced no-wrap is a place that cannot cause any scrollbar to appear. A screen shot is welcome, or a detailed description.

2. will come. It takes time, and i'm very busy with job
I gave problems priority over features.

[maverick]

1. i don't know what you are referring to. The only place where i forced no-wrap is a place that cannot cause any scrollbar to appear. A screen shot is welcome, or a detailed description.

2. will come. It takes time, and i'm very busy with job
I gave problems priority over features.

1.  See screen shots below.  Ignore what looks as white space as my chosen colors don't show up well on a white background.

2.  No problem.  Whenever you can.

[maverick]

Re: template password changer

First of all I would like to say this feature works as expected.  However, I have come across a problem with it.

Like many other sites, to access my file server all users "including guests" have to login.  Name and password for guests at this time are simply "guest" and that takes them to their folders until they register which would give them increased access to the site.

The problem I have encountered is that when a guest logs in he now has the capability to change the one password set up for "all guests" but once he does that, he is the only one that knows what it is and no other guests can access the site.  This is not a good situation.  You will see an example of a 'Guest' user in my screen shots above.

What is needed here is an option in "User Accounts" allowing the admin to approve or disapprove of the use of the password changer by user.  If a user is allowed to change his password, the password changer button will appear in the template.  If not, it is not a user option.

[SilentPliz]

About maverick's screenshots

It is this that is problematic: white-space:pre;

.comment { white-space:pre; }

If I remove the whole line, or if I put something in place of white-space: pre; (e.g: .comment { font-size:9pt; }) ... comments are displayed correctly.

@ maverick
You can also think about putting some <br /> in your HTML comments  

[maverick]

@ maverick
You can also think about putting some <br /> in your HTML comments  

Thanks but in my custom template the folder comments are centered (via properties -> comments).  Looks much better and you don't get any unwanted blank lines.  

[Mars]

What is needed here is an option in "User Accounts" allowing the admin to approve or disapprove of the use of the password changer by user.  If a user is allowed to change his password, the password changer button will appear in the template.  If not, it is not a user option.

It is so simple to make, I wonder of such a request

On the base, it is necessary to use the groups.

Create a group: 'canchangepass'

To authorize the use of the change of password:

{.switch|canchangepass|;|{.get account||member of.}|{: <a onclick="url">change password</a> :}|.}

Or more simply (for the useless)

{.if |{.member of|canchangepass.}|{: <a onclick="url">change password</a> :}.}

change the blue text by the correct request  and set the user as memeber of 'canchangepass'


Note from the wiki:
This is different from {.get account||member of.} because this latter form will consider only direct first-level membership, while {.member of.} will actually consider membership at any level.

{.if|{.and|%user%
            |{.not|{.match|guest;anonymous|%user%.}/not.}
            |{.member of|canchangepass.}
      /and.}
    |{: <a onclick="url">change password</a> :}
/if.}

[maverick]

mars,

I didn't think of doing it that way.  I'll give it a try.  Thanks.

[SilentPliz]

@ Maverick

Change the lines 306 at 311 with this "code"; that's all:

   <fieldset>
      <legend><img src="/~img27"> {.!User.}</legend>
     <center>
      {.if| %user% | %user% |<a href="~login">{.!Login.}</a></li> .}
     </center>
      {.if |{.and|%user%|{.!=|%user%|guest.}.}|
     <br />
      <button onclick='changePwd.call(this)' style='font-size:x-small;'>{.!Change password.}</button>
      /if.}
   </fieldset>