| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
boot.php
include/api.php
include/enotify.php
|
| |
| |
| |
| | |
and RED_PLATFORM is equally problematic for other reasons.
|
| | |
|
| | |
|
|/
|
|
| |
us to search and cache private posts
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
specified
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixed wrong Doxygen syntax and add some of the available FIXME to
Doxygen documentation.
Updated Doxygen configuration to add also all capital letter tags.
Adding some more Doxygen documentation.
|
| |
|
| |
|
|
|
|
| |
the site default.
|
| |
|
|
|
|
| |
reduce the impact of expiration queries.
|
| |
|
| |
|
| |
|
|
|
|
| |
body text. It could be any one of hundreds of functions that touch the message body. We really want to trim the body text, so I'm putting back all the trim statements - in mod/item and item_store and item_store_update. The last fix for random bad sigs noted that one of the trims wasn't there, so the others were removed. The correct fix is for all the trims to be there. We will probably have a few (quite a few) bad sigs during the transition back to trimmed text but this should nail it for anybody on recent code and with new content.
|
| |
|
|
|
|
| |
hackish but I don't see any other way out.
|
|
|
|
| |
The issue remains what to do about comments which are already in the DB and have ITEM_ORIGIN incorrectly set. We can't exactly reset them because the "original" context has been lost. (Sorry but couldn't resist an insider pun that none of you will be able to follow anyway). Read the comments.
|
|
|
|
| |
There are some fields in the actual stored item that may change when we start the second delivery chain so a few plugins may not deal with these items correctly. Since we only source public items these effects will be slight.
|
|
|
|
|
| |
Previous regex would cause matches to span several tags
when present, thus never recognizing the mention.
|
|
|
|
| |
searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief.
|
| |
|
| |
|
|
|
|
| |
fix for the problem of receiving a delete notification before we actually get the item which we're supposed to delete.
|
| |
|
|
|
|
| |
few weeks back. This solution is not optimal as it also leaves you in the privacy ACL in some cases and not in others but it restores the previous functionality
|
| |
|
| |
|
|
|
|
| |
2. The reason is simple - count how many posts would be in transit simultaneously if this was unlimited and somebody tagged 40-50 forums. In practice when used legitimately - we've rarely seen more than two, in fact I don't recall seeing more than two ever. Typically it is one and occasionally two. Changing the default is tricky - a client system cannot do it, but the site hosting a forum can choose to. Since not all sites that host forums will choose to do so, the ordering of the mentions would then be important.
|
|
|
|
| |
route matching and only look at the last hop before it got to us - which is ultimately all we should care about (since that sender controls the thread permissions). Route mismatches seem to occur somewhat frequently from yamkote (for unknown reasons), and the logging has been improved a bit so it should provide some slightly more useful debugging info in case it still happens going forward. Oh, also we'll set the parent on comments when we store the initial post (item_store()) and only go back and set the parent for top-level posts. This should reduce the number of comments with missing parents on shared hosts, but may increase the number of missing threads. Probably worthwhile to do a query occasionally for parent = 0 and see how we're doing and how many have shared host related delivery issues.
|
|
|
|
| |
warning resulting from recent tag work
|
| |
|
|
|
|
| |
/channel/ string
|
|
|
|
| |
delete and not forced
|
|
|
|
| |
visible item in the conversation deleted the photo as well. Now photos must be deleted in the photos module. Deleting the linked item removes any attached conversation elements (likes, etc.) and sets the conversation item to hidden. This may create an issue in the future if we move the photo tags, title, or other photo elements to the linked item rather than the photo. Noting here so this can potentially be discovered and remembered at that time.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
is really going on
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
boot.php
include/dba/dba_driver.php
include/diaspora.php
include/follow.php
include/session.php
include/zot.php
mod/photos.php
mod/ping.php
|