| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
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).
|
|\ |
|
| |\
| | |
| | | |
Added info about SSL certificates
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
used when SSL is used at all.
It is now in the check failure message in the installation routine, the
installation readme and in the documentation pages.
|
|/ /
| |
| |
| | |
do this for the auto-save events (every ten seconds) which could generate superfluous network traffic.
|
| |
| |
| |
| | |
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.
|
|
|
|
| |
it really needs to be re-worked for bootstrap but in any event the words "show" and "don't show" make a mess of it. We should probably just use icons (with a bit of padding) that people can select with a touchscreen and reformat the box accordingly.
|
|\ |
|
| |\
| | |
| | | |
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
|
| | | |
|
|\ \ \ |
|
| |\ \ \
| | |_|/
| |/| | |
Extended theme redbasic: Allow to center the content (aside + converse)
|
| | | |
| | | |
| | | |
| | | | |
Use max-width instead of width to allow mobile devices to reflow the content.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added an option to settings of redbasic theme. You are now able to
activate centering the left aside and the conversion regions in the
middle of the screen. This respects configuration of conversion region
width and works without special actions for mobile devices.
TODO: Find a way to handle conversion width given in percent.
|
|/ /
| |
| |
| | |
non-connected channels.
|
|/
|
|
| |
together
|
| |
|
| |
|
|
|
|
| |
don't lose it in the ajaxuploader.
|
| |
|
|
|
|
| |
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.
|
|/ |
|
|
|
|
| |
since the ACL will belong to the wrong channel. Leaving disabled for now. I don't know that we can solve all the issues without a different design so this may end up in a plugin for those who are willing to put up with the shortcomings.
|
|
|
|
| |
not yet work, so the functionality has not been enabled.
|