define('VALIDATE_EMAIL_TO_POST', '1');
in your project.inc, users have to validate their email addrs
to post in the forums, send PMs, or create profiles.
(e.g. because it has too many links) show the user an explanation.
Aside: the forum code (which was written by students a long time ago)
uses a hodge-podge of return conventions.
At some point we should standardize on 0 = success, nonzero = error code
principles:
- primary action buttons are green (btn-success)
- secondary action buttons are blue (btn-primary)
- potentially risky action buttons are yellow (btn-warning)
- if there are a lot of buttons (e.g. forum posts) use btn-xs
Our current translation system (Transifex) introduced a new editor feature which autodetects C-style placeholders in PO files. This wrongly detects our placeholders in the web code where a word immediately follows the digit. This leads to wrong translations if the placeholder is copied using this new transifex feature. The feature can not be globally disabled for our project. Instead every translator would need to use "raw" mode to disable it which is hard to communicate. Instead I added a space around problematic placeholders which is possing a smaller problem than wrong translations.
- change dark-background link color
- change dark-background colors for <pre>
- fix heading color for striped tables
It turns out that, for striped tables, Bootstrap ignores classes for <tr>.
You have to put them in the <th>.
row_heading() and row_heading_array() do this for you.
- put Preview content into a table w/ heading
- fix display of BBcode links and menus
- change textareas to class form-control
- add color to select so they work with dark and light backgrounds
Note: I'm becoming somewhat less enamored of Bootstrap.
Do this by putting
define("DISABLE_FORUMS", true);
in your html/project/project.inc.
If this is set, admin users can still see enough forum functionality
to post and edit news items
(this is linked to from the Admin web interface).
Other users, or non-logged-in access, sees news but no forums
or forum-related info.
- web: remove file_get_contents() workaround for PHP4
- web: If Akismet or ReCaptcha failure,
display the form again with a warning message at the top.
That way the user doesn't lose the text they just typed.
svn path=/trunk/boinc/; revision=16175
1) it's not correct to apply stripslashes() to all form input.
That should be done only if magic quotes is on.
I fixed this by adding a function undo_magic_quotes()
that does the right thing.
2) There's no reason to strip backslashes from user-supplied text
(forum titles and bodies, private messages, passwords etc.)
I'm not sure why this was being done.
It prevented messages from containing backslashes.
svn path=/trunk/boinc/; revision=15364
strip HTML tags from text (e.g. to remove photos)
- user web: show_image(): separate title (tooltip text)
from "alt" (replaces image if images disabled).
The latter must be terse.
- user web: show_button(): make it work even if Javascript disabled
svn path=/trunk/boinc/; revision=14294
Team founder and admins have moderator power.
Anyone can view a team message board,
but only team members can write to it.
Users cannot be banished from team message boards
(due to database limitations).
svn path=/trunk/boinc/; revision=14218
into a separate function.
Don't show subtitle bar for categories with no name.
Rename search_post_titles() to search_post_content()
svn path=/trunk/boinc/; revision=14209
- DB: added parent_type to forum
- user web: BoincUser uses caching by default
- client: fixed small memory leak in statistics parsing
svn path=/trunk/boinc/; revision=14130
David Anderson