| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
| |
Call the set_notification_manager from the load_object function instead.
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
| |
To delete all notifications before a certain time
PHPBB3-11103
|
| |\ |
|
| | |
| |
| |
| | |
PHPBB3-11103
|
| |/
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
| |
This lets us clean up the mess that was in load_object(), but requires
scope: prototype to be added to the service definitions for all types
or methods!
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Create a very basic user loader class to handle querying/storing
user data in a centralized location.
Use DIC collection service for notification types/methods.
Cleanup unused dependencies.
Fix some other issues.
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
disable_notifications
This should be called when an extension which has notification types
is disabled so that all those notifications are hidden and do not
cause errors
enable_notifications
This should be called when an extension which has notification types
that was disabled is re-enabled so that all those notifications that
were hidden are shown again
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
| |
Now, if there is no row for the user in the user_notifications table,
the user will receive basic notifications. If the user wishes to not
receive notifications, a row must be added with notify = 0.
For other methods besides the basic (e.g. email, jabber) a row must
still be added with notify = 1 for them to receive notifications
PHPBB3-11103
|
| |
|
|
|
|
| |
Fix a bug that broke it and make sure to set the needed config/auth settings
PHPBB3-11103
|
| |
|
|
|
|
| |
This is going to require you recreate the db tables.
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If you're following along and would like to update your DB, you can run
the following queries to do so:
ALTER TABLE phpbb_notifications CHANGE `is_disabled` `is_enabled`
TINYINT( 1 ) NOT NULL DEFAULT '1';
UPDATE `phpbb_notifications` SET is_enabled = 1;
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
How do we do this? If an item is unread, the URL to view that item will
be the URL to mark it as read (index.php?mark_notification=$id). When the
URL is visited it marks the item as read and redirects them to the correct
URL for the item.
If the item is read, the URL is directly to the item.
Prettify the html output
PHPBB-11103
|
| |
|
|
|
|
| |
Also add the ability to specify an _EXPLAIN text for the notification option
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
EXTENSION AUTHORS TAKE NOTE! This is to prevent errors with notifications
from extensions!
Set is_disabled to 1 for all your notifications when your extension is
disabled so they are ignored and do not cause errors.
When your extension is enabled again, set is_disabled to 0 and your
notifications will be working again.
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Mark post/topic in queue notifications read when visiting mcp
Change post/topic in queue notification url to use MCP.
Fix the bug:
Approving a topic marks the topic as read, but before the notification
is created for the user approving the topic (if they would get a
notification that the topic has been made). This causes it to be
stuck "unread".
PHPBB3-11103
|
| |
|
|
|
|
| |
Just for posts currently and not yet outputted.
PHPBB3-11103
|
| |
|
|
|
|
|
|
| |
Fixing extension type/method naming scheme so they can be autoloaded.
Other bugs
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
| |
|
|
|
|
| |
It's no longer needed
PHPBB3-11103
|
| |
|
|
| |
PHPBB3-11103
|
|
|
PHPBB3-11103
|