| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
already received. Incidentally I discovered why we had the meltdown replying to discover channel items the other day - but can't fix it easily.
|
| | |
|
| | |
|
| |
|
|
| |
show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
|
| |
|
|
| |
killing the matrix, just turn it off.
|
| |
|
|
| |
out but their profile photo will remain rainbow man (or the site default). However the photo_date has been updated so we won't try again. This checkin looks for such a failure and leaves the photo_date alone if the photo import failed.
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
@! tags private - period.
|
| | |
|
| | |
|
| |\
| |
| | |
A few little fixes
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
bootstrapify aclselector
|
| | |/ |
|
| |/ |
|
| |
|
|
| |
developer to collect the delivery reports for a given post and store them in a DB table so that the sender could track and verify where a message had been sent on a web page and verify the success or failure of those attempts without requiring admin access. (To be fair this would also need an extra flag which hasn't yet been implemented to indicate that a channel created a second delivery chain of the message).
|
| |
|
|
| |
the characteristics of one that was sourced by the sys channel instead of just being stored under the sys channel uid. This should allow comments and likes to flow upstream if permissions allow and may fix issue #398. Permission may still be denied by the original poster, but without this the comment/like is treated as a forgery and is blocked from transmission.
|
| |
|
|
| |
that we aren't giving deleted posts special treatment.
|
| |
|
|
| |
as it contains important routing and scope information. Previously we were only sending a couple of critical fields like the message-id, flags, and creation date. The thinking was that it is deleted, let's not resend the deleted contents anywhere. But in order to route this through the same path the original post took we really need the entire original post with all of its baggage attached.
|
| |\ |
|
| | |\
| | |
| | | |
change the way jot tools are displayed/hidden
|
| | | |
| | |
| | |
| | | |
editblock and editlayout which still depended on it.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
'new/search' item view)
also reformat the new/search template to pick up recent changes to conv_item.tpl
|
| |/
|
|
| |
non-connected channels.
|
| | |
|
| | |
|
| |
|
|
| |
the xchan_flags and not the channel_pageflags; XCHAN_FLAGS_DELETED should only be set if the channel is to be removed from the entire network. As mentioned in a previous commit, channel_pageflags could be set to PAGE_REMOVED but still leave living clones on other sites.
|
| |
|
|
| |
the hubloc deleted - but not the xchan. The channel might be alive at another hubloc. We should only mark the xchan deleted when removing a channel from the entire network - e.g. there are no hubs left to service it.
|
| | |
|
| | |
|
| |
|
|
| |
to the url directly and which weren't going through chanview. Also worth noting - mentions in posts do not go through chanview. Perhaps it is time to kill chanview (except we then cannot implemented a "connected" or "connect" button since we don't have any control over the landing page). For the time being I'm just trying to trap as many of the "visit URL" links as possible and sending them to a common place. Then we can figure out how that common place should behave.
|
| | |
|
| |\
| |
| | |
Try to repair of channel administration
|
| | |\ |
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Channel blocking and deleting was copied from user actions. This was not
done to an end. Hope what I do is enough to enable channel blocking and
deleting the correct way.
On deletion all entities that belong to the channel are deleted. But the
channel itself is just marked as deleted. Do not really understand why
it is done this way.
|
| | |_|/
|/| | |
|
| | |/
|/|
| |
| | |
This should fix the issue with encrypted content in the notification messages (for locally posted replies). The fix was a bit harder than anticipated because we store the parent id as an int in the notify table so this had to be modified to char storage as well.
|
| |/ |
|
| |
|
|
| |
not yet work, so the functionality has not been enabled.
|
| | |
|
| |
|
|
| |
so that we can still have an unconditional 'pending' link. Needs testing before integrating with the nav menu
|
