| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
[ticket/16108] Add topiclist_row_topic_by_author_before|after
|
| | |
| |
| |
| | |
PHPBB3-16108
|
| | |
| |
| |
| | |
PHPBB3-16108
|
| |\ \
| | |
| | |
| | | |
[ticket/16107] Add mcp_move_destination_forum_before|after
|
| | | |
| | |
| | |
| | | |
PHPBB3-16107
|
| | |/
| |
| |
| | |
PHPBB3-16107
|
| |\ \
| | |
| | |
| | | |
[ticket/16066] Fix FORM_INVALID always returned for banned user.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After the introduction of add_form_key() and check_form_key() calls to
login_box() in phpBB 3.2.6 and later, if a banned user attempts to login,
they receive a "The submitted form was invalid. Try submitting again."
Instead of the message indicating that they are banned, and why.
This is happening because check_ban() actually calls into login_box()
recursively, but after the $user->session_id has been switched to a new
session ID for the logging-on user. Therefore, now that check_form_key()
has been introduced to login_box(), it is impossible for check_form_key()
to succeed during this recursive call.
Fix is to make login_box()'s use of check_form_key() conditional on whether
IN_CHECK_BAN is defined, so that the recursive call does not attempt to
re-validate the form_key again. Note the form_key has already been
successfully verified by the original call into login_box(), prior to calling
into check_ban() and attempting to recursively call login_box(). So the
protection of why check_form_key() was added is still intact with this change.
PHPBB3-16066
|
| |\ \ \
| | | |
| | | |
| | | | |
[ticket/16112] Update composer dependencies for 3.2.x
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-16112
|
| |\ \ \ \
| |/ / /
|/| | |
| | | | |
[ticket/16097] Add core.viewtopic_gen_sort_selects_before
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-16097
|
| | | |/
| |/|
| | |
| | | |
PHPBB3-16097
|
| |\ \ \
| | | |
| | | |
| | | | |
[ticket/15885] Display group rank on memberlist_body
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15885
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
[ticket/15886] Group helper functions
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| | | | |
| | | |
| | | |
| | | | |
PHPBB3-15886
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
[ticket/14459] Check language input for group and fix template logic
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-14459
|
| | | |_|/
| |/| |
| | | |
| | | | |
PHPBB3-14459
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
[ticket/16013] Allow admins to use disallowed username
|
| | | | | |
| | | | |
| | | | |
| | | | | |
PHPBB3-16013
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
[ticket/16096] Use InnoDB fulltext limits for InnoDB tables
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The max and min search length for the MySQL database vary based on the
engine for the underlying table. For MyISAM tables, the variables are
ft_max_word_len and ft_min_word_len, but for InnoDB tables the
variables are innodb_ft_max_token_size and innodb_ft_min_token_size.
Take the posts table type into account when setting the max and min
search length.
PHPBB3-16096
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
[ticket/16106] Add core.mcp_main_before
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
PHPBB3-16106
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
[ticket/16103] Add core.pm_modify_message_subject
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
PHPBB3-16103
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
[ticket/16102] Add core.posting_modify_post_subject
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
PHPBB3-16102
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
[ticket/16070] Remove support for WebSTAR and Xitami
|